Niches · Lifecycle marketing & customer engagement

Build or change an automation flow or journey

One company's docs show a full fit.

1companies, full fit
5companies, fit with a limit
12companies carry the tag
13share of the category's work
4first-hand accounts

What counts as done

A flow or journey exists in draft with the named trigger, delays and branches readable back through the API, and does not go live without a separate step.

How agents ask for it: set up a welcome series, build the post-purchase flow, add a win-back branch

Does the job 1

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Omnisend B
Omnisend, UAB
POST /automations takes a trigger condition and blocks of delays, actions and splits, GET /automations/{id} returns the blocks, and going live is a separate enable operation. source

Does the job, with a limit 5

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Customer.io A
Peaberry Software, Inc. d/b/a Customer.io
The MCP write scope creates automation drafts and cannot edit live ones, and actions are readable and updatable through the App API, but the public spec has no create-automation endpoint, so the build rests on the MCP guide's claim. source
Dreamlit C
Notika AI (d/b/a Dreamlit AI)
Workflows with event or schedule triggers are built as drafts and go live only through confirm_publish, but they are written from natural language, not a graph, and get_workflow_and_preview_url's return shape for delays and branches isn't documented. source
Klaviyo API + MCP BB
Klaviyo, Inc.
POST /api/flows takes a full encoded definition and returns it, get_flow reads it back, and flow actions default to draft, but flow creation is capped at 100 a day and create_flow_action needs beta=true on MCP. source
Nitrosend BB
Nitrosend Pty Ltd
nitro_compose_flow creates and patches flow graphs and going live needs nitro_control_delivery, but saving a live or paused flow publishes the change straight away. source
Sequenzy B
Nic Tech Solutions, LLC
Create sequence makes a draft with an event trigger and delay steps, definitions read back by ID, and turning it on needs sequences:activate, but branches aren't shown in the create examples, and sequences:write edits emails in live sequences. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
ActiveCampaign E
ActiveCampaign, LLC
Not read: hosts paused under the terms question. Whether automations can be created or read in full through the API wasn't in the earlier sources.

Doesn't do this job 5

Listings in the category that do something else, with the reason.

ListingWhy
Braze B
Braze, Inc.
Canvas tools are list, details and data series only; no tool or documented endpoint creates or edits a Canvas's trigger, delays or branches. source
CleverTap D
WizRocket Inc.
The API index lists no journey or flow endpoint; Create Campaign makes single campaigns only. source
Iterable C
Iterable, Inc.
The spec has GET /api/journeys and triggerWorkflow only; no operation creates or edits a journey, and acc-03 could list journeys but not read their nodes or branches. source
Mailchimp Marketing API C
The Rocket Science Group LLC d/b/a Mailchimp
POST /automations creates only classic automations of four workflow types without branches, and the Customer Journeys API only triggers an existing step, so a journey with branches can't be built. source
MoEngage B
MoEngage, Inc.
Flow tools search, read, analyse and change a flow's status; none creates a flow or edits its trigger, delays or branches. source

What stops agents finishing

  • no API that creates or edits a journey (Iterable, Braze Canvas tools read-only)
  • flow creation capped per day
  • webhook triggers that refuse the automation host's URL

Around it

Before: lifecycle-marketing.profile-event-sync. After: lifecycle-marketing.send-with-approval.

Where this comes from

Weight 13 of 100 in Lifecycle marketing & customer engagement: 4 of 30 counted mentions (acc-03, 06, 20, 25), two of them planning issues

The same as data: /api/v1/use-cases/lifecycle-marketing.journey-build.json, or the MCP tool get_use_case with id lifecycle-marketing.journey-build. Other jobs in this category: /api/v1/niches?category=lifecycle-marketing.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.