Automation Flows

Prototype a workflow in conversation, save it as a flow, then let it run on triggers and schedules. Creating a flow never activates it — publishing is a deliberate, separate step.

From chat to automation

Every automation starts as a conversation. You describe what should happen — “when a deal moves to onboarding, send a welcome email, wait 3 days, then generate a contract” — and the agent builds a structured flow definition.

  1. Prototype in chat — describe your workflow in natural language. The agent calls describe_automation_capabilities to see available triggers and step types, then drafts the flow.
  2. Save as a draft — the agent calls create_automation_flow to persist the flow. This creates an inactive draft. Nothing runs. No triggers fire. You get a link to the flow builder in the Passo dashboard.
  3. Review — open the flow in the dashboard to inspect triggers, steps, and conditions. Adjust anything that needs tweaking.
  4. Publish — when ready, call publish_automation_flow or use the dashboard. The flow re-validates before going live and refuses with named errors if something would not execute correctly.

Safety by design

Creating a flow never activates it. Publishing is an explicit, separate step. This means you can prototype freely in conversation — building, adjusting, and iterating on flow definitions — without any risk of triggering live actions.

Building blocks

Call describe_automation_capabilities to get the full list. Here are the key types:

Trigger types

  • Deal stage change — fires when a deal enters a specific stage
  • Schedule — runs on a cron schedule
  • Manual — triggered by a user or API call

Step types

  • send_email — send a templated email to the creator
  • wait — pause for a specified duration
  • human_pause — pause until a human reviews and approves
  • branch — conditional logic based on deal or creator data
  • generate_contract — create and send a contract for the deal

Example: onboarding flow

Prompt: “Create a flow that fires when a deal moves to onboarding. Send a welcome email, wait 3 days, then generate a contract. If the contract isn't signed within 5 days, send a reminder email.”

The agent calls describe_automation_capabilities to confirm available step types, then calls create_automation_flow with the structured definition. You get back a flow ID and a link to review it in the dashboard before publishing.

Related tools