Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcargo.ai/llms.txt

Use this file to discover all available pages before exploring further.

Actions transform your Agent from a reasoning engine into an action-taker. Each action is an external API endpoint that the Agent can call to interact with the world.
For a complete reference of all available actions and how they’re used across Cargo, see the Actions overview.
Actions configuration interface

​
How actions work

When an Agent receives a task, it:
  1. Analyzes the goal and available actions
  2. Selects the appropriate action(s) based on their descriptions
  3. Executes the action with the right inputs
  4. Uses the output to continue reasoning or complete the task
The action’s description is critical. The Agent reads this description to decide when and how to use the action. Write descriptions that clearly explain what the action does and when to use it.

​
Configuring an action

​
Description (The AI Contract)

This plain-language description tells the Agent:
  • What the action does
  • When to use it
  • What inputs it expects
Good example: 
"Enriches a company using its domain. Returns firmographic data including
employee count, industry, funding, and tech stack. Use this when you need
company information for qualification or research."
Poor example: 
"Gets company data"

​
Input configuration

Each input field in an action has its own mode selector, giving you fine-grained control over how the Agent fills it in:
Field modeBadgeBehavior
DefaultGreyYou provide a fixed value for this field manually
AutoPurpleThe Agent decides the value for this specific field at runtime
DisableRedThe field is skipped entirely and not sent to the action
Fields default to Auto, meaning the Agent will determine the value based on conversation context, available data, and the action’s description. Switch a field to Default to lock it to a specific value, or Disable to exclude it entirely.
Mix Default and Auto fields when some inputs should always be the same (e.g., a specific CRM pipeline ID) while others depend on the conversation context (e.g., a lead’s email address).

​
Bulk execution

Enable this when the Agent should apply the action across multiple records in a single run. Useful for batch operations like:
  • Enriching a list of companies
  • Updating multiple CRM records
  • Sending notifications to several recipients

​
Common action types

CategoryExamplesTypical use
EnrichmentClearbit, Apollo, FullEnrichGather company or contact data
CRMSalesforce, HubSpot, AttioCreate/update records, log activities
CommunicationSlack, Email, OutreachSend messages, add to sequences
Data lookupInternal APIs, SQL queriesRetrieve custom data from your systems

​
MCP Servers

Cargo Agents support the Model Context Protocol (MCP)—an open standard for connecting AI models to external actions and data sources. You can connect your Agent to any MCP-compatible server, giving it instant access to a wide ecosystem of pre-built integrations. Simply provide the server URL, and Cargo will automatically discover and register the available actions. For example, you can connect your Agent to:
  • Notion — Search pages, create databases, and manage workspace content
  • HeyReach — Automate LinkedIn outreach and manage campaigns
  • HubSpot — Access CRM data, manage contacts, and trigger workflows

​
Best practices

Write clear descriptions

The Agent relies on descriptions to choose actions. Be specific about what the action does and what it returns.

Name actions descriptively

Use names like Enrich-Company or Slack-Notify-Rep instead of generic names like Action1.

Handle failures gracefully

In your Agent’s instructions, specify what to do if an action call fails (retry, skip, report error).

Limit scope

Only give Agents access to the actions they need. Fewer actions = faster, more accurate action selection.

​
Next steps

All actions reference

Complete reference for all action types available in Cargo.

Using actions everywhere

Learn how to leverage actions across tools, plays, agents, and APIs.