AgentWorks
GitHub Book a call

Product

Overview Goals Crews Flows Brain Vault LLM Gateway Code Auto-improve Connectors Bullpen

Use cases

All premade agents E-commerce operations Sales & GTM Shopify stores Customer support Finance & billing Marketing & growth Engineering ops

Enterprise

Overview Release quality Incident response Security testing Cloud cost Growth analytics Code Expert Crews Vault Pricing Docs GitHub Book a call

Flows Enterprise

The same steps, every time. Run them from anywhere.

Some jobs don't need an agent that plans. They need the same few steps, done well, every time: read the enquiry, decide what it is, look something up, write the reply. Flows let you chain agents, decisions and small scripts into one simple sequence, then call it from your website, your CRM or any other system. Share it, and your team runs it from its dashboard.

Read the Flow guide See how it works
Website enquiry → qualified replyExample

Trigger · Contact form on your website

  1. ClassifierSort the enquirysales → next · support or partner → their own agent
  2. ScriptLook up the companyCRM API call
  3. AgentDraft the replyyour tone, with pricing
  4. ScriptSend to your CRMreturns the result
Agent step: system prompt + messageClassifier or condition: picks the next stepScript step

How it works

Design it once. Call it from anything.

  1. Chain the steps

    Agent steps, classifiers, conditions and small scripts.

  2. Test with real input

    See every step's output, and the exact path each run took on the diagram.

  3. Deploy a trigger

    Get a versioned API endpoint or webhook.

  4. Run it anywhere

    Call it from your site, CRM or backend, or share its dashboard with your team. Every run is logged.

Use cases

Same steps, every time. Illustrative examples.

  • Website enquiry

    Contact form

    1. Classifier: sales, support or partner
    2. Look up the company in your CRM
    3. Draft the reply in your tone

    Reply sent, lead logged

  • Support triage

    New ticket

    1. Classifier: billing, bug, account or other
    2. That area's agent finds the answer in your help docs
    3. Found an answer?

    Answered, or routed to a person

  • Invoice intake

    Invoice by email

    1. Extract supplier, amount and due date
    2. Check the totals add up
    3. Anything off?

    Booked, or flagged for review

  • Content check

    New blog draft

    1. Check it against your style guide
    2. Check every claim has a source

    Approved, or edits suggested

  • Order exception

    Store webhook

    1. Decide what went wrong
    2. Update the order

    Customer update prepared

  • Call notes to CRM

    Call transcript

    1. Summarise and pull next steps
    2. Write them to the CRM

    Notes and follow-ups logged

FAQ

Questions, answered.

How do I publish a new version?

Edit the draft in the Flow Builder and publish. Each publish freezes a numbered version behind the same endpoint, so callers can pin a version or follow the latest.

How is a Flow different from a Goal?

A Goal works toward a number: it plans, measures and adjusts its own steps, and shows whether the metric moves. A Flow is fixed. It runs the same steps in the same order every time, which is what you want behind a website form or another system.

What can a step be?

An agent step with its own system prompt and message, a classifier that sorts the input into the categories you name, a condition that decides which step runs next, or a script step for exact work like formatting data or calling an API. Steps pass their output to the next one.

How does a Flow send a request the right way?

Add a classifier step. You list the categories, such as billing, support or sales, with a line on what belongs in each, and the Flow sends each request to that category's branch. The diagram shows which way every run went.

Who can run a Flow I share?

Anyone you share it with opens its dashboard and can ask it questions or run the published version. Only you change the steps.

How do other systems run a Flow?

Each deployed Flow gets a trigger: an authenticated API endpoint or webhook. Your website, CRM, backend or no-code tool sends the input and gets the result back, or a callback when it finishes.

Which models run the agent steps?

The same AI plans you connect to AgentWorks, such as Claude, ChatGPT, Gemini or Cursor. You can choose a different one per step.

Have a chain in mind? Build it with us first.

We are opening Flows to a small group of early users. Tell us the steps you repeat, and we will set up your first Flow with you.

Get early access How AgentWorks works