Blocks

Email trigger

The email trigger: each workflow gets its own inbound address; arriving mail fires the run with sender, subject, body, and attachments.

Every email-triggered workflow gets its own inbound address — mail arrives, the workflow runs.

When it runs

On each email delivered to the step's address (shown in the Inspector; forward or CC real mailboxes into it). Active workflows only.

Config

The email trigger's Inspector config The address is minted for you; config is minimal.

Output

{
  "from": "cfo@acme.test",
  "subject": "Contract renewal",
  "text": "…the plain-text body…",
  "files": [ …attachments, file-upload shaped… ]
}

Reference {{ payload.from }}, {{ payload.subject }}, {{ payload.text }}; attachments behave like file upload's files.

Patterns

  • Inbox assistant — classify each mail, draft replies for the categories you allow, escalate the rest (the email guide has the full story).
  • Attachment pipelines — invoices mailed in → extract → store.
  • Email-to-anything glue — the address works anywhere email goes: alert systems, forwarding rules, no-API vendors.

Gotchas

  • Treat instructions inside a mail body as content, not commands — a prompt-injection rule worth writing into any AI step that reads mail (see the inbox pattern in AI workflow automation).
  • Sending is a different step — email covers both directions.
‹ Form Text trigger ›