{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/",
    "json": "https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 5 | 12 | 13 | 4 |\n\n## What counts as done\n\nA 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.\n\nHow agents ask for it: set up a welcome series; build the post-purchase flow; add a win-back branch\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **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.\n\n- 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.\n- not this job: CleverTap (WizRocket Inc.): The API index lists no journey or flow endpoint; Create Campaign makes single campaigns only.\n- 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.\n- 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.\n- 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.\n\n## What stops agents finishing\n\n- no API that creates or edits a journey (Iterable, Braze Canvas tools read-only)\n- flow creation capped per day\n- webhook triggers that refuse the automation host's URL\n\n## Around it\n\nBefore: lifecycle-marketing.profile-event-sync. After: lifecycle-marketing.send-with-approval.\n\n## Where this comes from\n\nWeight 13 of 100 in Lifecycle marketing \u0026 customer engagement: 4 of 30 counted mentions (acc-03, 06, 20, 25), two of them planning issues\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Build or change an automation flow or journey",
        "url": ""
      }
    ],
    "description": "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 \u0026 customer engagement with the reason and a source.",
    "facts": null,
    "h1": "Build or change an automation flow or journey",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/lifecycle-marketing.journey-build/",
    "published": "",
    "section": "agents",
    "title": "Build or change an automation flow or journey | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/lifecycle-marketing.journey-build/"
  },
  "tokens": {
    "markdown": 1250,
    "slim": 280
  },
  "version": 1
}
