Send the right email the moment a step is done

Attach an email to any step in your workflow. When a teammate completes that step in a run, Manifestly sends the message for you — personalized with tokens and delivered to the addresses collected during the run. No more manual “just letting you know” notes after every hand-off.

Start your free trial. No credit card required.

Email on step completion Onboarding kickoff
To {{Customer email}}
Reply‑To success@acme.co
From Acme (your org)
Subject Your onboarding for {{run.title}} is underway
Body Hi {{Contact name}}, your kickoff step is complete and your account is being set up. Questions? Just reply to this email.
Fires when the step is completed Save message

Stop chasing hand-offs with manual emails

Every finished step used to mean someone remembering to email the customer, the next team, or the requester — with the right details, spelled correctly, to the right address. Attach the email to the step once and Manifestly sends it every single run, exactly when the work is done.

Doing it by hand
  • Someone has to remember to send it after each step
  • Copy-pasting names, dates, and details every time
  • Missed and mistyped notifications slip through
With step-completion emails
  • Configured once on the step, sent every run
  • Tokens fill in the run's real details automatically
  • Delivery is logged in the run's activity

Set it up once, and every run sends it for you

1

Attach an email to a step

On any step in your workflow, add an email message. You can attach more than one message to the same step when several people need to hear about it.

2

Write it with tokens

Set the recipients, reply-to, subject, and body. Drop in tokens for run details and for values captured earlier in the run, so each message reads like you wrote it by hand.

3

Complete the step

The next time someone checks that step off in a run, Manifestly fills in the tokens and sends the email — then records the delivery in the run's activity.

One message, personalized for every run

Write the email once and let tokens do the rest. Reference run details like {{run.title}}, the current date, your organization, or the person completing the step — plus any value someone captured earlier in the run, referenced by its field label. When the step is completed, each token resolves to that run's real data.

  • Use tokens in the recipients, subject, and body alike.
  • An “insert variable” helper lists every token available on that step.
  • Anything a token can't fill is flagged in the run's activity, so nothing goes out half-blank unnoticed.
Template → what sends
You write
Subject: {{run.title}} — step complete

Hi {{Contact name}},
{{step.name}}” is done as of {{current_date.full}}.
What actually sends
Subject: Acme Corp onboarding — step complete

Hi Priya Shah,
“Provision the account” is done as of August 9, 2026.

Email the people who matter to this run

The recipient doesn't have to be decided in advance. Point the To field at an email address collected during the run — the customer, the vendor, the requester — and the message goes to whoever this particular run is about. You can also list fixed addresses, mix several together, and set a Reply-To so responses land with the right person.

  • Send to email fields captured earlier in the run.
  • Add one or more fixed addresses, separated by commas.
  • Recipients are validated as real addresses before anything is sent.
To {{Customer email}}, ops@acme.co
resolves at completion
Delivered to priya@acme-corp.com, ops@acme.co
Reply‑To success@acme.co
From (display name) Your organization

Tokens you can drop into any message

The exact list adapts to your workflow — the “insert variable” helper shows what's available on each step.

Run & system
{{run.title}} {{run.due_date.full}} {{step.name}} {{current_date.full}}
People & org
{{current_user.name}} {{current_user.email}} {{organization.name}} {{department.name}}
Data collected in the run
{{Contact name}} {{Customer email}} {{Order number}}
Run links (body)
{{run.url}} {{run.percent_completed}} {{run.summary}}

Sent reliably, and recorded

These aren't fire-and-forget. Each message is tied to the step and the run it came from, so you can always see what went out and to whom.

  • Every send is written to the run's activity, with the recipients and time.
  • If a token couldn't be filled or an address was invalid, the activity says so instead of sending something broken.
  • Messages send from your organization's name, so recipients recognize who it's from.
  • The same step-completion messaging can also send an SMS when you need to reach someone fast.
Run activity
Provision the account completed by Dana Ruiz
Email sent on step completion
To: priya@acme-corp.com, ops@acme.co
Subject: Acme Corp onboarding — step complete
Aug 9, 2026 · 10:42 AM

Where teams put step-completion emails to work

Customer onboarding

Keep the customer in the loop as each phase wraps.

Finish “Provision the account” → the customer gets a heads-up email at the address captured on the intake step.

Team hand-offs

Notify the next team the instant the work reaches them.

Complete the review step → the fulfillment inbox is emailed with the run title and a link to the run.

Approvals & requests

Close the loop with whoever asked.

Approve the request step → the requester is emailed automatically that it's been approved.

Step-completion emails, answered

The moment that step is completed in a run. Manifestly fills in the tokens with that run's data and sends the message — you configure it once on the workflow's step and it happens automatically on every run.

Recipients, reply-to, subject, and body. Tokens cover run details (title, due date, step name), the current date, your organization and department, the person completing the step, links back to the run, and any value captured by a data-collection field earlier in the run — referenced by its field label.

Yes. Put a token for an email field in the To line and the message goes to whatever address was entered for that run — the customer, vendor, or requester. You can also list one or more fixed addresses, or mix both.

Yes. You can attach multiple messages to the same step, each with its own recipients and content, so different people can be notified when that step is done.

Recipients are validated as real email addresses first, and any token that couldn't be resolved is flagged in the run's activity. That way a broken or half-filled message doesn't quietly go out — you can see what happened.

Messages send with your organization's name as the display name, and you can set a Reply-To so responses reach the right person or inbox.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

Send a Customized Email on Step Completion

With Manifestly, your team will Never Miss a Thing.