Send email from your flows

Before you can email someone, you need their address — with their permission. Ask for it right in the conversation using the Ask for Input node set to Email, or a hosted form with an email question. Either way, the address lands on the contact and every following email step can use it.

The email question carries a built-in consent gate: a flow that asks for an email won’t publish until you’ve acknowledged the consent terms, and every captured address is recorded together with the question asked, the answer given, and the consent context. If a dispute ever comes, your records already answer it.

Add the Send Email node after an email is on file and point it at one of your templates. The default choice, “Use sender for triggering Instagram account,” uses that account’s explicit From-identity assignment. Choose a specific identity only when this node intentionally needs an override. Options let you track opens and clicks (both on by default) and override the subject line for this one send.

The node splits on the outcome, so follow-ups always match reality. The Queued branch continues when the email is accepted for delivery; the Skipped branch continues when it can’t send — because there’s no address on file, the contact unsubscribed or is suppressed, the account has no ready identity, the reply inbox is unverified, the mailing address is missing, sending is paused, the monthly allowance is used up, or the template is unavailable. A stop routes visibly instead of failing silently.

There’s no separate campaign builder to learn: an email sequence is just a flow. Chain Send Email nodes with Wait nodes — welcome now, value in two days, an offer in five — and branch on what happens like any other flow. Because it’s a flow, the sequence can react: send a different next email to people who clicked than to people who didn’t.

Every marketing email carries unsubscribe links automatically — you never add them, and they mean what they say. A recipient can leave just that flow’s emails, or unsubscribe from your workspace entirely. The workspace-wide kind — including the one-click unsubscribe some inboxes show in their header — writes a suppression that no future send bypasses.

The Suppressions page is the master list of everyone who won’t receive your email — unsubscribes, spam complaints, and bounced addresses, added automatically as they happen. You can add an address by hand, export the list, or lift someone who asked to come back.

The Analytics tab keeps you honest: sent and delivered counts, open and click rates, bounces, complaints, unsubscribes, and skips — with a daily timeline, a per-flow breakdown, and a plain-language list of why any sends didn’t land. Test sends never show up here, so your numbers stay real.

Deliverability is guarded automatically. Ravela watches your complaint and bounce rates over a rolling window, and if they cross safety thresholds it pauses your sending before your reputation pays for it — and tells your owners and admins why. Clean up the audience, then resume from your email settings.