Workflow templates

A template is a ready-made diagram with a sample trigger payload. Start a workflow from one under Start from when you press New workflow on a project page. That list opens on AI debate, which needs a change before it runs. See AI debate. In the builder, the node library also lists the templates: picking one there replaces the whole canvas, renames the workflow after the template and puts its sample payload in the Test tab. The live version is unaffected until you publish.

Templates leave every Agent node without an agent, because an agent is your organization’s own record with its model and apps. Pick one in each Agent node before the first run.

Order router

Rules only, no AI and no apps. A good first workflow to run.

1. New order: a Manual trigger.
2. Valid order?: a Conditional that continues when {{trigger.amount}} is greater than 0.
3. Route by size: a Decision with two branches, Large (≥ 500) and Standard (< 500).
4. Hold for review: a 3-second Delay on the Large branch.
5. Record order: a webhook Notification both branches lead into. It sends the customer, the amount and {{nodes.route.selectedBranch}}.

Sample payload: {"customer": "ACME", "amount": 750}.

Caution

The webhook URL is https://postman-echo.com/post, a public test service that echoes requests back. Change it to your own URL before real data goes through.

Support triage

An agent classifies a customer message, then a specialist agent handles it.

1. Customer email: a Manual trigger.
2. Classify: an Agent asked to reply with one lowercase word, bug, feature or question.
3. Route: a Decision with Bug, Feature and Question branches, each matching when the reply contains its word.
4. Bug ticket, Feature request and Answer: an Agent on each branch, writing from the original message in {{trigger}}.

Sample payload: Customer email: the app crashes every time I upload a photo.

Set first: an agent in each of the four Agent nodes. A reply with none of the three words takes no branch, so the run ends after Route.

Calendar briefing

Reads your calendar and turns it into a briefing.

1. Plan my week: a Manual trigger.
2. Upcoming events: an Action that lists your next 10 Google Calendar events.
3. Briefing: an Agent that summarizes what is next, the conflicts and the free blocks.

Set first: a Google Calendar connection, made by an admin on the Apps page, and an agent in Briefing. See Google Calendar.

Then select Upcoming events. If its panel shows Choose an app and action, the action the template names is no longer offered. Pick Google Calendar in that picker, then its action that lists upcoming events. The picker always holds the current list of actions.

Slack assistant

Answers when someone mentions your Slack bot.

1. App mentioned: an App event trigger on Slack’s app mention event.
2. Reply: an Agent told to answer briefly and post the answer once, as a thread reply in the channel it was mentioned in.

Set first:

1. A Slack connection, made by an admin. See Slack.
2. On the trigger, Slack as the App, then the Connection. Picking the app clears the event, so pick the app mention event again under Event.
3. An agent in Reply with a grant on that Slack connection that includes posting a message. See Grants and approvals. The Task names the Slack action to post with. If the grant lists that action under another name, change the Task to match.
4. The bot invited to each channel it should answer in.
5. Publish, so the trigger starts listening. It uses one of your plan’s active app subscriptions.

AI debate

Three agents weigh an idea: Pros and Cons each argue one side from the Idea trigger’s text, and Verdict weighs them.

Sample payload: Idea: replace our REST API with GraphQL.

Caution

As shipped, both Pros and Cons lead into Verdict. A step may be reached by only one edge per run, so a run fails at Verdict with “Pros and Cons both fired into Verdict; only one step may”.

To use it, chain the agents:

1. Delete the edges from Idea to Cons, from Pros to Verdict and from Cons to Verdict.
2. Connect Pros to Cons, and Cons to Verdict.
3. In Cons, replace {{ input }} with {{ trigger }}, so it argues against the idea, not against the pros.
4. In Verdict, replace {{ input }} with {{ nodes.pros.response }} and {{ nodes.cons.response }}.