Inbound Email Workflow Trigger in Sparkforge
The Inbound Email workflow trigger fires on every inbound email — cold senders, existing contacts, or replies — and supports filters for sender, mailbox, subject, body, and attachments. Cold-email capture requires a Sparkforge Email or Mailgun dedicated domain.
The Inbound Email workflow trigger automates actions whenever a new email lands in your mailbox. Whether the sender is an existing contact or brand new, the trigger gives you granular control over how inbound mail enters workflows — so you can capture leads, route conversations, and respond faster.
What the trigger fires on
Unlike the Customer Replied trigger (which only fires on replies to messages you sent), the Inbound Email trigger captures all inbound mail, including cold emails from senders not in your CRM. It handles:
- Cold emails: new emails from unknown senders.
- Warm emails: new emails from existing contacts.
- Customer replies: replies in an existing thread (optional, controlled by a setting).
Important: Only domains configured with Sparkforge Email or Mailgun dedicated domains can capture cold inbound emails. Two-way sync (Gmail/Outlook), shared domains, and other SMTP setups capture only emails from existing contacts.
Supported email configurations
| Email setup | Cold inbound captured | Inbound from existing contact captured |
|---|---|---|
| Sparkforge Email — Shared Domain | No | Yes (replies to mail sent from Sparkforge) |
| Dedicated Domain (Mailgun or Sparkforge Email) | Yes | Yes |
| Two-Way Sync (Gmail / Outlook) | No | Yes |
| Other SMTP (SendGrid, Custom) | No | Yes |
Dedicated domain behavior
- Any address at your dedicated domain is captured. With
acme.com, that includessales@acme.com,support@acme.com, andrandom@acme.com. - Each sub-account should have a unique dedicated subdomain. Sharing one domain across sub-accounts can route mail unpredictably.
- If a sub-account is configured with a non-dedicated setup, the trigger UI shows guidance that cold inbound capture will not work.
What you can do with it
- Capture cold inbound mail — first-time emails from unknown senders that the Customer Replied trigger never sees.
- Route by inbox using the To/Mailbox filter (sales@ vs. support@).
- Trigger workflows by subject line for refunds, resumes, or warmup mail.
- Filter by From, CC, body, and attachments to narrow exactly which messages enter automation.
- Control reply behavior so existing-thread replies do not retrigger workflows.
How to set up the trigger
- Log in to your sub-account.
- Open Automations > Workflows.
- Create a new workflow or open an existing one.
- Click + Add New Trigger and select Inbound Email.
- Enter a clear trigger name (for example, "New Lead from Sales Inbox").
- Click + Add Filters to narrow when the workflow should run.
- Set the trigger settings: Track replies in existing threads and Automatically create a contact.
- Click Save Trigger.
- Add workflow actions (Send Email, Create Contact, Add Tag, Assign to User, etc.) and publish.
Trigger filter ideas
- Email Sent To: route by inbox so support@ and sales@ run different flows.
- Subject contains: auto-tag refund requests or invoice replies.
- From domain: isolate vendor emails or partner threads.
- Has attachment: capture resumes, signed contracts, or invoices.
Common pitfalls
- Cold-email capture only works on a dedicated domain. Shared domains and Gmail/Outlook sync will not capture mail from new senders.
- Reusing one dedicated domain across sub-accounts can misroute incoming mail.
- Leaving "Track replies in existing threads" on can re-trigger automation on every reply — turn it off when you only want first-touch workflows.
Frequently Asked Questions
Can the Inbound Email trigger capture cold emails?
How is this different from the Customer Replied trigger?
What addresses get captured on a dedicated domain?
Can I route different inboxes to different workflows?
Will replies in an existing thread retrigger the workflow?
Was this article helpful?
Thanks for the feedback.