Practical ways teams use AutoRelay

How to send transactional email without adding more platform sprawl

Transactional email should feel operationally simple: one place to send from, one place to review access, and one place to understand what happened. Teams often lose time when account notifications, billing mail, and product communications are spread across too many systems.

AutoRelay helps centralize that flow so teams can keep delivery and account access aligned with how the product actually behaves.

How event-driven journeys help product teams move faster

Product events carry the context teams already need. Instead of manually coordinating follow-up, event-driven messaging lets teams respond at the right time with less operational drag.

When those flows are easier to manage, teams can spend more effort refining customer experience and less effort stitching tools together.

How to build an event-driven flow in AutoRelay

Start inside a project, open Flow Studio, choose an entry signal, and add the actions you want AutoRelay to perform. The current release supports immediate email sends, timed waits, and follow-on signal emission.

The fastest starting point is an event signal like user_signed_up paired with a send-email step. Teams can then layer wait steps and follow-on signals to create onboarding or lifecycle sequences that stay close to the product event stream.

Practical use cases include welcome sequences, activation nudges, trial-to-paid conversion prompts, billing reminders, and operational alerts that need to react to the same application events your product already emits.

Teams that prefer infrastructure-as-code can also create and update flows programmatically through the Flow API, then execute them by posting matching events from their product backend.

How to create and execute flows through code

Use a project-scoped Events key to manage flows by API. Create the flow with POST /v1/flows, inspect current project flows with GET /v1/flows, then trigger matching runs with POST /v1/events.

This is useful when a product like Northstar CRM wants to provision opinionated automation for each customer workspace without requiring manual flow setup in the dashboard.

A good first test is a one-step flow triggered by a unique event name. Create it, send the event, and confirm the response reports both a matched flow and a sent message. Once that works, add waits and branches.

When a project has a verified sender domain and default sender email, flow sends inherit that sender automatically. The execution response does not echo the sender address back, so branded-sender testing still requires checking project configuration or the delivered message itself.

How to build a signup funnel

Use a dedicated first-party project for signup and lifecycle marketing. That keeps sender identity, templates, delivery safeguards, analytics, and unsubscribe handling in one place instead of splitting them across hidden internal paths.

A practical starter funnel uses two entry signals: signup_started and signup_completed. Start with a welcome note, follow with a short setup reminder, then send one proof-driven message that helps the new user get to value quickly.

Keep the sequence short and spaced out with waits. Every message in that project should include an unsubscribe link so recipients can opt out cleanly.

Why reusable templates make lifecycle messaging easier to operate

Teams rarely want to rewrite email bodies inside every individual flow step. Reusable templates reduce drift, keep lifecycle messaging consistent, and make it easier to evolve onboarding, billing, and retention communication without editing the same content in multiple places.

AutoRelay is planned to support categorized templates so teams can attach reusable message assets to flows instead of treating every step like a one-off email action.

How to verify a sender domain for branded delivery

Teams that want branded delivery should add a sender domain at the project level, then publish the CNAME records AutoRelay provides. Those records are the DKIM verification path used to confirm that the domain is authorized for sending.

A practical pattern is to verify a subdomain like mail.example.com instead of the root domain. That keeps outbound delivery cleaner and avoids unnecessary overlap with a company’s main inbox setup.

DNS providers often want the host entered relative to the zone they already manage. For example, if the zone is example.com and the sender domain is mail.example.com, the host field may need token._domainkey.mail instead of the full hostname.

How to run a branded sender test

Use a disposable flow and a fictional sender domain to confirm that project-level sender settings are being applied correctly. For example, imagine a product called Northstar CRM with a verified sender domain of mail.northstar.example and a default sender email of noreply@mail.northstar.example.

Create a one-step inline send flow, trigger it with a unique event, and confirm two things: the API response shows matchedFlows: 1 and sentMessages: 1, and the delivered email arrives from the branded sender address you configured for the project.

The event response confirms execution. The inbox confirms the sender identity. You need both when testing branded delivery.

Managed templates versus remote templates

Some teams want to manage templates directly inside the messaging platform. Others already keep templates in their own product stack and only need execution and orchestration. AutoRelay is being shaped to support both models so teams can choose between a built-in template library and remote template references.

That flexibility is part of the product direction that separates AutoRelay from tools that focus only on send APIs or only on campaign orchestration.

AutoRelay flow FAQ

What triggers a flow? A matching entry signal on an active flow inside the current project.

How do wait steps work? AutoRelay stores the pending flow state and resumes it on a timed loop.

Can one event trigger multiple flows? Yes, if multiple active flows match the same entry signal.

Do flows stay scoped to a project? Yes. Flows are attached to a specific project and use that project context.

Will flows support reusable templates? Yes. Planned work includes managed template libraries and remote template references for advanced customers.

Can I create flows by API instead of the dashboard? Yes. Use a project-scoped events key with the Flow API.

How do I know a flow really executed? The /v1/events response includes flow_result with matched flow and send counts.

Why did my flow store audience_filter as null? Empty-string filters are normalized to null when the flow definition is stored.

Where do I confirm the sender used? Check the project sender settings and the delivered email. The event execution response does not include the sender address.

How should signup funnels handle opt-out? Keep those messages in a dedicated marketing project and include an unsubscribe link in every send.

Flow troubleshooting

Event accepted but no flow matched? Check that the flow is active, the trigger value exactly matches the event name, and the event key belongs to the correct project.

Flow matched but no mail sent? Check that properties.email is present and the send-email step has valid content.

Mail sent from the wrong sender? Check the project sender domain status and default sender email in the selected project. Flow sends inherit the project sender configuration.

Want a known-good first test? Create a one-step inline send flow, trigger it with a unique event name, and confirm matchedFlows: 1 and sentMessages: 1 in the response.

Why event-based automation can improve lifecycle messaging

Teams that connect communication to real product behavior tend to reduce lag, reduce manual coordination, and improve the consistency of customer follow-up. A cleaner automation layer also makes it easier to operate onboarding, reminders, usage nudges, and critical account notifications from one control plane.

Why tighter customer communication systems improve retention

Customers notice when messaging is timely, clear, and consistent. They also notice when billing notices, account alerts, or onboarding sequences arrive late or feel disconnected from product activity.

Better communication systems support trust, reduce friction, and make products feel more complete.

How access control supports safer messaging operations

Messaging infrastructure is only as dependable as the way access is managed. Clear workspace boundaries, key rotation, and cleaner operational surfaces reduce the chance of accidental misuse and make product teams more confident in day-to-day delivery.