Skip to content

Branching on send results

Use the action's Send status output to follow up when an email doesn't go out.

When the email isn’t sent, the workflow history marks the Send transactional email step as failed, with the reason, but your workflow keeps going. That’s deliberate: it lets you decide what happens next instead of the workflow stopping with an error.

a workflow’s history for one record: the Send transactional email step shows Error with the reason, and its outputs status and error_code read recipient_invalid

Add an if/then branch on the action’s Send status output to catch the cases that need a person.

  1. Add an if/then branch directly after the Send transactional email action.

  2. Branch on the action’s output. In the branch filter, choose the Send transactional email action’s outputs and select Send status.

  3. Add a branch for success. Match Sent and Queued (warm-up) — both mean the email is on its way.

  4. Add branches for the failures you care about, such as Recipient missing or Suppressed, or let everything else fall into the None met branch.

  5. Add follow-up actions to each failure branch — create a task for the record owner, send an internal notification, or set a property.

  6. Save and turn on the workflow.

    a workflow that branches on Send status after the Send transactional email action: Sent and Queued (warm-up) end, Suppressed and Recipient missing create a task for the deal owner, and None met sends an internal email

Records that don’t get their email now land in a branch where someone can act on them.

Receipt that must reach the customer. In a deal workflow that sends a receipt to the deal’s contacts, route Recipient missing, Recipient invalid, and Suppressed to a task for the deal owner: “Receipt didn’t send — confirm the customer’s email address.”

Temporary problems. For Review pending, Quota exhausted, and Internal error, add a delay of an hour and re-enroll the record in a follow-up workflow, or notify an admin to check App Home. Don’t loop without a delay — repeated sends to the same address can hit the limit of 10 emails per recipient in 24 hours.

Keeping a record of what was sent. Use the Message ID output in a later action — for example, to store it on the deal — so you can look the email up in the Send log later.

  • Queued (warm-up) means the email is waiting for tomorrow’s warm-up limit. It sends automatically after midnight UTC; the workflow isn’t told again when it goes out, and Message ID stays empty. The contact’s timeline shows a Sent event when it does. If it can’t be sent then — the address was suppressed in the meantime, say — the reason shows only in the Send log.
  • Sent means the email was accepted for delivery, not that it reached the inbox. A later bounce or spam complaint shows in the send log and on the contact’s timeline, and suppresses the address for future sends.
  • The workflow history shows the explanation for each outcome, such as “Not sent: the recipient address is malformed or its domain cannot receive email.” See Send status and error codes.