Introduction

Flows in Chamelio let you automate legal work end-to-end — from the moment a request comes in, through generation, negotiation, signing, and storage. Each flow is built by chaining together modular steps, each with its own configuration. This article walks through every step you can add to a flow, what it does, and how to configure it.

How flows are structured

Every flow begins with a single Intake step (the trigger) and then continues with one or more action steps connected in sequence. You add a new step by clicking the + button that appears between existing steps or at the bottom of the flow. The right-hand Add Steps panel shows all step types available for insertion. Clicking a step inserts it into the flow and opens its configuration panel.

Intake (Trigger)

The Intake step is the entry point of every flow. It defines how a request enters Chamelio and what data is collected at the start.

Under Start from, choose one or more sources that can initiate the flow: Slack, Salesforce, Email, Manual, or Teams.

Under Fields group, you can create groups of custom input fields that the requester must complete (for example, counterparty name, deal value, region). These fields become variables that downstream steps can reference via the @ mention picker.

In the flow canvas, the Intake step reads: "Start workflow when [Source] with [Field] field is completed."

Agent

The Agent step hands work off to Chamelio's AI Agent for reviews, redlines, or custom flow tasks. It's the most flexible step — use it whenever you need the AI to read, reason over, or produce structured output.

Configure it by setting:

Agent context — the resources the agent can access during this step (for example, specific playbooks, clauses, policies, or uploaded documents). Click Add to attach resources.

Instructions — free-text guidance for the agent. You can type instructions directly, pull instructions from a previous step with Add from Flow. Use @ to inject variables from earlier steps or intake fields.

Output settings — define the structured outputs the agent should produce. Click Add Output to declare one or more named result fields that later steps can consume.

Human Approval — toggle this on to require a specific person to approve the agent's output before the flow continues.

Generate

The Generate step automatically produces documents, drafts, or other outputs from a template.

For template-based generation, pick the template and version, then fill in the template fields that appear. You can also add conditional logic with Add condition so that different template branches are selected based on flow variables.

Under Result, set the Result Type (for example, Word) and provide a Document name for the generated file. The output becomes available as an input to subsequent steps.

Notify

Notify sends updates or alerts to people — internally or externally — once the flow reaches this step.

Pick a Destination: Slack, Teams, or Email. Depending on the channel, you'll see recipient pickers. For Email, fill in Recipients and optional CC, a Subject, and a Message body. Both Subject and Message support @ to pull variables from earlier steps. Click Add from Flow to insert attachments from previous steps. Toggle Send as PDF to convert attached files to PDF before sending.

Negotiate

Negotiate creates a collaborative review round where parties can revise a document through iterative versions.

Choose the Inputs to review (the document that should be reviewed). Assign the negotiation to a Review Assignee, which is the person responsible for handling the negotiation. Pick a Result Type (for example, Word) for the reviewed file. Toggle Store versions on to keep a history of every version created during negotiation — useful for audit trails and comparing drafts.

Sign

The Sign step manages the signature phase of a contract, including routing, envelope creation, and archival.

Select the documents to sign and choose a Signature Provider (DocuSign is available out of the box). The Signatures coordinator is the person that will create and send the envelope.

Add Counter party recipients (external signers) and User party recipients (internal signers). You can reorder the signing sequence with Switch order, and add more signers with Add more. Map from flow lets you pull signer details from earlier steps.

Under Message, set the Subject and optional Message sent to signers. Additional toggles:

• Save final signed copy to repository — automatically archives the fully signed PDF after completion.

• Auto send envelope — automatically sends the envelope (requires an organization-level DocuSign integration).

• Auto draft envelope — automatically drafts the envelope when a Coordinator is set and DocuSign is connected.

Collect

Collect gathers structured details from a person, either to fill gaps in the original intake or to capture approvals, answers, or data later in the flow.

Choose where to Collect from: Slack, Teams, or Email. Under Fields to Collect, click Add group to build groups of fields the respondent must fill in. Assign to sets the person responsible for filling the request. Provide a Subject and Message explaining what you need.

Customization

Customization updates task properties — priority, owner, title, due date, and other attributes — for the task associated with the flow.

Click Add Attribute to choose which task property you want to set or change, and then supply the new value (either a static value or one pulled from the flow context). Use this step whenever you need the flow itself to adjust metadata on the task it's running against.

Condition

Condition branches the flow based on input variables.

Choose between two modes at the top of the panel:

• True / False — a binary branch. Build one or more If... rules (left side, comparison, right value), then define what happens on the If true branch and the If False branch.

• Multi / Case — multiple exclusive branches, each with its own case and downstream path.

Approval

Approval pauses the flow until one or more designated approvers sign off on a piece of content.

Under Content to approve, click Add to attach the content (often a document generated upstream). Under Select Approvers, use Add Group to define who needs to approve. Toggle Approve by order on to require approvals in sequence rather than in parallel.

Pick the Select channel where the request will be delivered (Slack, Teams, or Email), then supply a Subject and Message Content explaining what's being approved and why. The flow only advances once approvals are recorded.

Store

Store persists files to a long-term destination at the end of a flow (or at any intermediate checkpoint).

Choose the Store destination: Vault for general document storage or Contracts for contract-specific archival.

Salesforce destination is also supported in environments where that integration is enabled.

Merge

Merge combines outputs from multiple previous steps — most commonly used to rejoin branches after a Condition step, or to consolidate parallel paths before a downstream action such as Notify or Store.

In addition to selecting the merging paths, you can set a merging rule, which can merge fields from the Merged Paths into a single input that subsequent steps can reference.

Tips for building flows

Start by sketching the trigger and the final outcome (for example: "Intake from Email → Generate NDA → Negotiate → Sign → Store"). Add branching with Condition only where there's a real decision, and use Merge to cleanly rejoin branches. Toggle Human Approval on Agent steps whenever the AI's output is consequential, and prefer Approval steps for formal sign-off on content that will leave your organization.

When a step supports @ mentions or Add from Flow, use them aggressively — it's the primary way to pass data from one step to the next without manual copy-paste.