Action categories
Cargo organizes actions into two groups: workflow actions for building logic in tools and plays, and connectors for integrating with external systems and AI.Workflow actions
These actions are available in the Tool and Play editors for building automation logic:Logic
Control workflow behavior with branching, looping, filtering, and custom
scripts.
AI
Use LLMs to generate content, extract information, and search documents
semantically.
Sales
Purpose-built actions for lead allocation, scoring, and revenue operations.
Storage
Read, write, and search data in your Cargo data models.
Universal actions
These actions are available everywhere in Cargo—in tools, plays, agents, and via API:Integrations
Connect to CRMs, enrichment providers, communication tools, and external
platforms.
Tools
Call other Cargo tools from within your workflows to compose complex
automations.
Agents
Invoke AI agents to handle complex, multi-step reasoning tasks autonomously.
Where actions are used
| Context | Description |
|---|---|
| Tools | Build reusable workflows by connecting actions visually in the tool editor |
| Plays | Automate data-driven workflows that trigger when data model records change |
| Agents | Give AI the ability to select and execute actions autonomously |
| MCP | Expose your Cargo tools to any MCP-compatible AI system (Claude, Cursor, etc.) |
| API | Call tools and actions programmatically from your own applications |
Logic
Logic actions control how your workflow executes—branching based on conditions, looping through arrays, or running custom code.Logic actions are available in Tools and Plays only.
| Action | Purpose | Use when… |
|---|---|---|
| Balance | Distribute records across multiple routes proportionally | You need even workload distribution |
| Branch | Route execution based on a Yes/No condition | You have a single condition to evaluate |
| Delay | Pause execution for a specified time | You need to wait for external processes or rate limits |
| Filter | Stop execution if a condition is false | You want to gate workflow continuation |
| Group | Execute a sub-workflow for each item in an array | You’re processing multiple records |
| Human Review | Pause for human approval via Slack | You need manual approval before proceeding |
| Script | Run custom JavaScript code | You need custom logic or transformations |
| Split | Randomly route to one of two branches | You’re A/B testing or sampling |
| Switch | Route based on multiple conditions | You have several possible paths |
| Variables | Create and store values for later use | You need to maintain state across nodes |
Human Review
The Human Review node pauses your workflow and sends a message to Slack, allowing a team member to approve, decline, or edit the content before the workflow continues. This is essential for workflows where you need human oversight before taking action—such as sending personalized outreach, updating CRM records, or executing high-stakes operations. How it works:- When the workflow reaches the Human Review node, it posts a message to your configured Slack channel
- The message displays your content along with three buttons: Approve, Decline, and Edit
- The workflow pauses and waits for someone to respond
- Based on the response, the workflow continues down one of two branches
| Property | Description |
|---|---|
| Connector | Select your Slack integration. Make sure the integration is already added to the target channel. |
| Channel | The Slack channel or user DM where the review request will be posted. |
| Title | The message title that appears as the username in Slack. Supports expressions like {{input.company_name}} - Review. |
| Content | The content to be reviewed. This is displayed in a formatted block within the Slack message. Supports expressions for dynamic data. |
| Timeout | Maximum time to wait for a response before timing out. Defaults to 24 hours if not specified. |
- Branch 1 (Approved): The reviewer clicked “Approve” or “Edit” (with modifications). The workflow continues with the approved or edited content.
- Branch 2 (Declined): The reviewer clicked “Decline”. Use this branch to handle rejections—skip the action, log the decision, or trigger an alternative flow.
The Edit button allows reviewers to modify the content before approving.
The edited content is passed to the Approved branch, so your downstream nodes
receive the human-modified version.
AI
AI actions leverage large language models to process, generate, and understand content.AI actions are available in Tools and Plays only.
| Action | Description |
|---|---|
| File search | Search through files and documents using semantic understanding. Find relevant content based on meaning, not just keywords. |
| Model ask | Query an LLM with a prompt. Generate text, analyze data, extract information, or make decisions. |
Sales
Sales actions are purpose-built for revenue operations, replicating complex routing and scoring logic.Sales actions are available in Tools and Plays only.
| Action | Description |
|---|---|
| Allocate | Distribute leads to team members based on rules. Supports round-robin, territory-based, and capacity-weighted distribution. |
| Scoring | Create scoring models to evaluate records. Determine lead priority and potential value based on business rules. |
Storage
Storage actions interact with data models in your Cargo workspace, enabling data persistence and retrieval.Storage actions are available in Tools and Plays only.
| Action | Description |
|---|---|
| Memory | Key/value store for temporary data during a workflow run |
| Model custom column | Set custom column values on existing records |
| Model record | Add new records to your data models |
| Model search | Query your data models with filters and conditions |
| Model vector search | Perform semantic searches using vector-based queries |
Integrations
Integration actions connect Cargo to external platforms. Each integration provides a set of actions specific to that platform.Common actions
| Action | Description |
|---|---|
| Insert | Create new records in the connected system |
| Find | Retrieve a specific record by ID |
| Match | Check if a record exists based on criteria |
| Search | Find multiple records based on filters |
| Update | Modify existing records |
| Upsert | Insert or update based on matching criteria |
| Delete | Remove records from the connected system |
| Associate | Link two records together (e.g., contact to company) |
Tools
Call other Cargo tools from within your workflows. This lets you compose complex automations from smaller, reusable building blocks. Use cases:- Modular design — Build small, focused tools and combine them into larger workflows
- Reuse logic — Share common operations (like enrichment or CRM writes) across multiple plays
- Abstraction — Hide complexity behind a simple tool interface
Agents
Invoke AI agents from within your workflows. Agents can handle complex, multi-step tasks that require reasoning and decision-making. Use cases:- Research tasks — Have an agent gather and synthesize information
- Dynamic decisions — Let the agent choose the best action based on context
- Complex workflows — Delegate multi-step processes to an autonomous agent
Learn more about agents
Understand how to build and configure AI agents.
Browsing actions
Cargo offers 120+ actions across all categories. To explore them:- Open the Tool or Play editor
- Click the + button to open the node picker
- Browse by category or search for specific capabilities
- Click any action to see its configuration options and documentation