# Build or change an automation flow or journey

> Build or change an automation flow or journey: 1 companies fully do it, 5 with a limit, 12 carry the tag. Every listing in Lifecycle marketing & customer engagement with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/
- Markdown: https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 5 | 12 | 13 | 4 |

## 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

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

- **Omnisend (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.

## Does the job, with a limit

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.

- **Customer.io (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.
- **Dreamlit (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.
- **Klaviyo API + MCP (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.
- **Nitrosend (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.
- **Sequenzy (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.

## Couldn't check

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

- **ActiveCampaign (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.

- not this job: Braze (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.
- not this job: CleverTap (WizRocket Inc.): The API index lists no journey or flow endpoint; Create Campaign makes single campaigns only.
- not this job: Iterable (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.
- not this job: Mailchimp Marketing API (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.
- not this job: MoEngage (MoEngage, Inc.): Flow tools search, read, analyse and change a flow's status; none creates a flow or edits its trigger, delays or branches.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/lifecycle-marketing.journey-build.json, or the MCP tool get_use_case with id lifecycle-marketing.journey-build. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
