Choosing who a step sends to
By default, a messaging block sends to the contact who triggered the flow, that’s what makes an automation feel personal. You can also point it at a fixed list of wallets (up to 250) for a targeted announcement.An automation handles one contact per entry, there’s no “send to the whole segment” step inside a flow. To reach an entire segment, send a campaign to that segment directly, or have your system send one “entered a segment” event per contact.
Send an email
Point the step at a saved template, and optionally override the subject. Email steps skip rather than fail when they can’t send, and the flow simply moves on:
Because a skipped step doesn’t stop the flow, an automation can finish without sending anything. If an email step produced nothing, check the entry’s history for a skip reason before assuming the trigger is broken.
Send an in-app push
Give the step a title and body, and optionally a button (it needs both a label and a link to appear). In-app pushes reach wallets that have signed in through the SDK; someone offline gets the push the next time they connect, within a 72-hour window. See In-App Notifications for the setup, and note that in-app has its own monthly allowance, separate from email. Wallets with no in-app session are quietly skipped. You can size the reachable audience ahead of time from your segment view.Launch a campaign
Hand the contact off to a campaign you’ve already prepared. Reach for this when the follow-up content is owned by the campaigns team and kept on their schedule, rather than written into the flow itself.Handoff patterns
Immediate in-app, delayed email
Immediate in-app, delayed email
Acknowledge on-chain instantly where the user already is, then follow with email once the moment has passed.
trigger → send in-app → wait 1h → send emailThis is the shape of the built-in Mint Welcome play.Channel fallback
Channel fallback
Prefer in-app, fall back to email when the wallet has no session.
trigger → branch (has wallet → send in-app | else → send email)A branch can see both the wallet and the email on the entry. See Triggers and Conditions.Nudge after intent
Nudge after intent
Someone approved a token but never swapped. Wait, then prompt.
trigger (approval intent) → wait 30m → send email → send in-appThe built-in Approval Abandoned Cart play.Tag now, campaign later
Tag now, campaign later
Don’t message immediately, mark the contact so a campaign can pick them up.
trigger → add tag → call a webhookUseful when send timing belongs to the campaigns team rather than the trigger.