Output

Email outbound

Send report link

The Email outbound node sends an email when the workflow reaches it, usually the finished report or a link to it. It is the step that puts the result in someone's inbox without anyone hitting send.

How it works

Write the message once with placeholders for the parts that change (the recipient, the result, a link). Every job fills them in and sends automatically.

It can email the original sender back, a fixed address like your team, or an address pulled from the data, so the right person always gets it.

Pair it with a Classify step and you can send different messages for different outcomes, an approval to one path and a decline to another.

Common use cases

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

Deliver the finished report

Send the applicant or your team a link to the report the moment a job finishes.

Send the outcome

Email a templated result, including the reason, when a decision is made.

Hand off to a reviewer

Email a colleague that a job needs their eyes, with the key details inline.

Email outbound in a workflow

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

What you set up

Write the subject and body, using placeholders for values that change per job.
Choose who it goes to: the original sender, a fixed address, or one from the data.
Attach or link the result the workflow produced.

Common questions

Can each outcome send a different email?

Yes. Put a Classify node before it and wire a separate Email outbound to each path, so approvals and declines read differently.

Can it reply to the person who submitted?

Yes. If the job started from an email, the sender travels with it and this node can reply straight back to them.

Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.

Field	Type	Default	What it controls
`recipient`	string (emails)	—	Fixed address(es) to send to; when blank it falls back to the job's original sender.
`subject`	string	—	Overrides the email subject; supports job/lookups/status tokens.
`body`	string	—	Overrides the email body; supports job/lookups/status tokens.
`cc`	string (emails)	—	Additional CC recipients.
`replyTo`	string	—	Overrides the Reply-To header; supports the same tokens as the body.
`bodyOnly`	boolean	`false`	Strip the branded email chrome and send just the body.
`attachment`	enum: auto \| report \| merged-pdf \| filled-pdfs \| bundle \| originals \| none	`auto`	What file, if any, to attach.

recipient
Fixed address(es) to send to; when blank it falls back to the job's original sender.
Type: string (emails)
subject
Overrides the email subject; supports job/lookups/status tokens.
Type: string
body
Overrides the email body; supports job/lookups/status tokens.
Type: string
cc
Additional CC recipients.
Type: string (emails)
replyTo
Overrides the Reply-To header; supports the same tokens as the body.
Type: string
bodyOnly
Strip the branded email chrome and send just the body.
Type: booleanDefault: false
attachment
What file, if any, to attach.
Type: enum: auto | report | merged-pdf | filled-pdfs | bundle | originals | noneDefault: auto

How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.

{
  "id": "email-out",
  "type": "card",
  "position": {
    "x": 160,
    "y": 120
  },
  "data": {
    "type": "email-out",
    "kind": "output",
    "title": "Email outbound",
    "subtitle": "Send report link",
    "config": {
      "recipient": "",
      "subject": "",
      "body": "",
      "cc": "",
      "replyTo": "",
      "bodyOnly": "false",
      "attachment": "auto"
    }
  }
}