For developers
Connect the event. Let the journey do the rest.
Your product knows when someone signs up, activates, or returns. Connect those signals to email workflows your team can edit, test, and understand.
Connect your AWS account. One flat SendOps fee.
Built for collaboration
Ship the integration. Share the controls.
Use the API to sync contacts and record activity. Build workflows in SendFlow or on the visual canvas, and let marketing make everyday campaign changes without another deployment.
Visual canvas, SendFlow source, API, or MCP. Your team works on the same workflow, whichever way they build.
- Triggers from product events, segments, and dates.
- Branching, waits, named exits, and stable random splits.
- Version history and restore for campaign definitions.
- Shadow mode and per-contact timelines for debugging.
- Scoped API access and MCP tools for your coding agent.
Templates fit your build
Keep the email code close to the product.
Author with React Email, preview using test data, and push definitions from CI. Your repository holds a copy; SendOps keeps the shared, versioned definitions your team works with.
{
"templates": {
"welcome": {
"path": "emails/welcome.tsx",
"testdata": "fixtures/emails/welcome/"
},
"order-confirmation": {
"path": "emails/order-confirmation.tsx",
"testdata": "fixtures/emails/order-confirmation.json"
},
"password-reset": {
"path": "emails/password-reset.tsx"
}
}
}Personalization you can inspect
Real context. Predictable messages.
Typed contact attributes and explicit test fixtures make it easier to spot a missing name or broken action link before a workflow sends.
{
"name": "Alice Chen",
"company": "Acme Corp",
"action_url": "https://app.acme.com/onboard"
}An integration you can reason about
Connect signup to the first useful action.
Define the event contract once. Keep application state trustworthy, workflow logic reviewable, and everyday campaign edits in the hands of the team.
Account creation starts onboarding. Project creation ends the beginner reminders. Your existing transactional email keeps sending directly through SES.
A small application integration, a workflow definition you can review, and a repeatable path from change to rehearsal.
01
Send a reliable signal
Associate signup and project-created activity with the correct contact. Register the attributes the workflow will use and handle absent values deliberately.
02
Review the SendFlow change
Keep a copy of the definition in Git. Review triggers, waits, and the activation exit together with the event contract before pushing from CI.
03
Test the paths that matter
Rehearse a fast activator, someone who never starts, and a contact missing an attribute. Inspect their timelines instead of relying on a test email alone.
04
Keep the handoff clear
Engineering maintains events and webhook receivers. Marketing edits messages and timing. SendOps records definition versions whichever editing surface your team uses.
Powered by your Amazon SES
Ambitious workflows. Proven delivery.
Send from your own AWS account, alongside the transactional emails your product already sends. Keep the infrastructure, reputation, and sending costs under your control.
Your delivery foundation
Connect SES with a keyless AWS role. Manage domains, authentication, channels, and delivery health in SendOps.
Your transactional sending stays independent
Your application keeps sending directly through SES, independently of SendOps availability. SendOps handles the workflow orchestration and brings delivery events into view.
Your team gets the full toolkit
Message search, templates, broadcasts, inbound email, DMARC monitoring, alerts, and integrations support every journey.
Start building
Go as deep as your product needs.
Your next workflow starts here
Build journeys with the care you give your code.
Connect your AWS account. Build your first journey. Make the next email count.
Free plan available. No credit card required.