Input

Email inbound

Forward to address

The Email inbound node gives your workflow its own email address. Anything sent there, usually a document attached to a message, starts a job automatically. No app to open, no upload button: people just email it in like they already do.

How it works

You get a dedicated forwarding address. Point your existing intake inbox at it, or hand it out directly, and every incoming message becomes a new job with its attachments ready for the next step.

The sender, subject, and body come through too, so later steps can reply to the right person or read details out of the message.

This is the most common way real work arrives, because customers and partners are already comfortable sending things by email.

Common use cases

Real situations where this node earns its place in a flow.

Applicants forward statements

Give applicants a single address to send their PDF bank statements to. Each message starts a job on its own, with no portal to log into.

Vendors email invoices

Point an accounts-payable inbox at a workflow so every vendor invoice that lands is picked up and processed the moment it arrives.

Catch forwarded submissions

Forward mail from any other inbox (a contact form, a partner referral) into a flow and let the workflow pull out what matters.

Email inbound in a workflow

A simple example of where this node sits in a flow.

Email inbound Forward to address Email outbound Send report link

What you set up

  • Copy the forwarding address the node gives you.
  • Send or auto-forward documents to it (an inbox rule works well).
  • Attachments and the message details flow into the steps after it.

Common questions

Do senders need an account?

No. Anyone who can send an email can start a job. That is the point: it meets people where they already are.

Can the workflow reply to whoever sent it in?

Yes. The sender's address travels with the job, so an Email outbound step later can reply straight back to them.