Create records from incoming emails
Give a workflow its own inbox address so every email sent to it runs the workflow, with the sender, subject, body and attachments ready to use.
- Verified Nov 17, 2026
- Classic builder
On this page
An email catcher turns incoming email into work in your app: a support request becomes a ticket, an invoice sent by a supplier becomes a record with the PDF attached. Each email delivered to the address runs a workflow.
Catch emails with a workflow #
- Create a workflow with the Email Catcher trigger In the trigger picker it is described as When an email is received. Save the workflow; until then the trigger says Save this workflow to choose its inbox address.
- Check the app's inbox subdomain Every Email Catcher workflow in an app receives mail on the app's own subdomain. If the trigger says the app has no inbox subdomain yet, click Open Email Settings and set Workflow Email Catcher Inbox Subdomain, then Save subdomain. Changing it later changes the address of every Email Catcher workflow in the app.
- Choose the inbox address Under Inbox Address, click Choose an address (or Change address), type a name such as
invoicesand click Save address. The name must be at least 3 characters and free in this app; if it is taken, pick one of the suggestions under Try instead. - Capture a sample email Click Send a test email, or Paste sample JSON. Until then the Sample Email section shows example data. The sample's fields become available to mappings, conditions and Loop steps.
- Add the steps For example a Create Record action that maps the sender to a customer email field, the subject to a title field and the body to a notes field.
The address looks like invoices@yourapp.emailtotada.com. Nothing else needs setting up: any email sent to it runs the workflow. Click How to use this address for a reminder.
What the workflow receives #
Each email arrives as data the workflow's steps can use, including the sender (From and Reply-To), the To, Cc and recipient addresses, the subject, the date, the body, the headers and the attachments. Attachments are stored privately; the Sample Email section lists their names and sizes.
Limit who can run the workflow #
Under Sender Rules:
| Setting | What it does |
|---|---|
| Allowed senders | Addresses or domains, one per line: anna@acme.com, @acme.com, or @.acme.com to include subdomains. |
| Only allow senders on the list | Rejects every email from anyone not listed under Allowed senders. With an empty list nothing gets through. |
| Blocked senders | Never runs for emails from these addresses or domains. |
Use your own domain #
When your account allows a custom domain, you can catch mail on a subdomain of your own, such as inbox.yourcompany.com. Use a subdomain you do not already receive mail on. Then, once per domain:
- Add the domain to your mail service Add it to your Postmark, SendGrid or Mailgun account.
- Point its MX records at that service Use the MX values the service gives you.
- Paste the listener URL as its inbound webhook Copy the URL shown under Point your mail service here in the trigger.
On your own domain, only addresses saved on a workflow run one.
Delivery #
Run immediately when the email arrives runs the workflow while the mail provider waits instead of queueing it. Use it only for short workflows; long ones should stay queued so the provider does not time out.
Email catchers under Automation #
Email catchers created before Workflows live under Automation › Email Catchers. What you see there depends on your app:
- Workflows available, no email catchers: the page says email catchers are no longer managed here and offers Go to Workflows.
- Workflows available, some email catchers: a notice says they are moving to Workflows. Your email catchers keep working and the manager opens below the notice.
- Workflows not available: the manager opens as before.
If the app has never used them, the page first shows Enable Email Catchers. After that the manager loads inside the page with your app's tables and fields, and you edit each email catcher, its address and its field mapping there.
Plans #
The Email Catcher trigger is available when your plan includes it; if it does not, you cannot set up an inbox address and emails sent to one do not run the workflow. The older email catchers under Automation need a plan that includes incoming webhooks.
Was this page helpful?
Something wrong or missing on this page? Tell us.