Cargo CLI — Connections

Connector and integration management: listing connectors, discovering available integrations, and managing authenticated connector instances.

See
references/response-shapes.md
for full JSON response structures. See
references/troubleshooting.md
for common errors and how to fix them. See
references/examples/connectors.md
for connector CRUD and discovery examples. See
references/examples/integrations.md
for listing available integrations and OAuth flows. For third-party connector rate limit handling and retry config in workflows, see
cargo-orchestration/references/polling.md
and
cargo-orchestration/references/troubleshooting.md
. Native integrations do not have rate limits.

Prerequisites

bash

npm install -g @cargo-ai/cli
cargo-ai login --oauth                                  # browser sign-in (recommended)
# or: cargo-ai login --token <your-api-token>           # workspace-scoped API token (non-interactive)
# Pin a default workspace at login (with --oauth)
cargo-ai login --oauth --workspace-uuid <uuid>

Verify with

cargo-ai whoami

. All commands output JSON to stdout. Without a global install, prefix every command with

npx @cargo-ai/cli

instead of

cargo-ai

Failed commands exit non-zero and return

{"errorMessage": "..."}

Key concepts

Integration: The external service type (e.g. HubSpot, Clearbit, Salesforce). Integrations define what actions are available.

Connector: An authenticated instance of an integration. One integration can have multiple connectors (e.g. two different HubSpot accounts). Connectors are what you reference in workflow node graphs.

Discover resources first

bash

cargo-ai connection connector list                        # all authenticated connectors
cargo-ai connection integration list                      # all available integration types
cargo-ai connection integration list --search "hubspot"   # search by name
cargo-ai connection integration get <slug>                # third-party-specific actions (e.g. HubSpot)
cargo-ai connection native-integration get                # built-in Cargo actions only (NOT third-party)

integration get

native-integration get

These two commands return different sets of actions and are not interchangeable:

Command	What it returns	When to use
`integration get <slug>`	Actions specific to a third-party service (e.g. HubSpot contact CRUD, deal management, Salesforce queries)	When you need service-specific actions to use in a connector node — use this for HubSpot, Salesforce, Clearbit, etc.
`native-integration get`	Generic built-in Cargo actions (e.g. HTTP requests, data transforms, internal utilities)	When you need Cargo-native capabilities that don't belong to any specific third-party connector

Example: To find HubSpot-specific actions, use

integration get hubspot

— not

native-integration get

. The latter will only return generic actions unrelated to HubSpot.

Quick reference

bash

cargo-ai connection connector list --integration-slug <slug>
cargo-ai connection connector create --integration-slug <slug> --slug <slug> --name <name>
cargo-ai connection connector update --uuid <uuid> --name <name>
cargo-ai connection connector remove <connector-uuid>
cargo-ai connection connector get <connector-uuid>
cargo-ai connection connector autocomplete --connector-uuid <uuid> --slug <slug> --params '<json>'
cargo-ai connection integration list
cargo-ai connection integration get <slug>
cargo-ai connection integration get-documentation <slug>
cargo-ai connection native-integration get

Connectors

Connectors are authenticated connections to external services.

bash

# List all connectors
cargo-ai connection connector list

# Create a connector
cargo-ai connection connector create \
  --integration-slug clearbit \
  --slug clearbit_production \
  --name "Clearbit - Production"

# Update a connector
cargo-ai connection connector update --uuid <connector-uuid> --name "Clearbit - Staging"

# Remove a connector
cargo-ai connection connector remove <connector-uuid>

# Check if a connector slug is taken
cargo-ai connection connector exists-by-slug --slug clearbit_production

Note: Creating a connector requires

--slug

(unique identifier) in addition to

--name

(display name) and

--integration-slug

. For OAuth-based integrations, the authentication flow is completed separately via

connection integration complete-oauth

Integrations

Integrations define the available services and their connector actions.

bash

# List all available integrations
cargo-ai connection integration list

# Filter by category
cargo-ai connection integration list --category enrichment

# Search by name
cargo-ai connection integration list --search "hubspot"

# Find by exact slug
cargo-ai connection integration list --slug clearbit

# Only integrations that have actions (usable in workflow nodes)
cargo-ai connection integration list --has-actions true

# Only integrations that have extractors (can sync data into models)
cargo-ai connection integration list --has-extractors true

# Get built-in Cargo actions and extractors (NOT third-party connector actions)
cargo-ai connection native-integration get

Integration categories:

engagement

marketing

sales

finance

analytics

freeform

success

support

enrichment

storage

custom

Use

integration get <slug>

to discover all actions available for a specific third-party service (e.g. HubSpot, Salesforce). Use

native-integration get

only for built-in Cargo actions — it does not return HubSpot or other service-specific actions. Actions are referenced by

actionSlug

in workflow node graphs (see the

cargo-orchestration

skill's

references/nodes.md

Connector autocomplete — fetching available values for action fields

Some action fields don't accept freeform input — their allowed values must be fetched dynamically from the connector. When you inspect an action's config (via

integration get <slug>

native-integration get

), look at the

uiSchema

alongside the

jsonSchema

. If a field's

uiSchema

contains

"ui:widget": "IntegrationAutocompleteWidget"

, the valid values for that field must be retrieved using

connector autocomplete

How to detect autocomplete fields

When an action's config looks like this:

json

{
  "jsonSchema": {
    "type": "object",
    "properties": {
      "objectType": { "type": "string", "description": "The object type" }
    }
  },
  "uiSchema": {
    "objectType": {
      "ui:widget": "IntegrationAutocompleteWidget",
      "ui:options": {
        "slug": "listObjects",
        "allowRefresh": true
      }
    }
  }
}

The

objectType

field requires autocomplete. The

ui:options.slug

(

"listObjects"

) is the autocomplete slug you pass to

connector autocomplete

How to call connector autocomplete

bash

cargo-ai connection connector autocomplete \
  --connector-uuid <connector-uuid> \
  --slug <autocomplete-slug> \
  --params '{}'

Flag	Required	Description
`--connector-uuid`	yes	The UUID of the connector to autocomplete against
`--slug`	yes	The autocomplete slug from `uiSchema[field]["ui:options"].slug`
`--params`	yes	JSON object of parameters (use `{}` when none are needed)
`--value`	no	Search string to filter results
`--refresh`	no	Bypass cache and fetch fresh results

Autocomplete with parameters

Some autocomplete fields depend on the value of another field. This is indicated by a

params

object in

ui:options

json

{
  "uiSchema": {
    "objectType": {
      "ui:widget": "IntegrationAutocompleteWidget",
      "ui:options": { "slug": "listObjects" }
    },
    "propertyName": {
      "ui:widget": "IntegrationAutocompleteWidget",
      "ui:options": {
        "slug": "listObjectProperties",
        "params": { "objectType": "$this.$parent.objectType" }
      }
    }
  }
}

Here,

propertyName

depends on the selected

objectType

. Replace the

$this.$parent...

expression with the actual value you chose:

bash

# 1. First, get the list of object types
cargo-ai connection connector autocomplete \
  --connector-uuid <uuid> --slug listObjects --params '{}'

# 2. Then, get properties for the chosen object type
cargo-ai connection connector autocomplete \
  --connector-uuid <uuid> --slug listObjectProperties \
  --params '{"objectType": "contacts"}'

Response format

json

{
  "results": [
    { "label": "Contacts", "value": "contacts" },
    { "label": "Companies", "value": "companies" },
    { "label": "Deals", "value": "deals" }
  ]
}

Use the

value

field in your node config. The

label

is the human-readable display name. Results may also include optional

description

and

parent

fields.

End-to-end example: configuring a HubSpot action

bash

# 1. Find your HubSpot connector UUID
cargo-ai connection connector list --integration-slug hubspot

# 2. Get HubSpot actions and inspect their config + uiSchema
cargo-ai connection integration get hubspot
# → The "findRecords" action has objectType with autocomplete slug "listObjects"

# 3. Fetch available object types
cargo-ai connection connector autocomplete \
  --connector-uuid <hubspot-connector-uuid> \
  --slug listObjects --params '{}'
# → Returns: contacts, companies, deals, tickets, etc.

# 4. Fetch properties for the chosen object type
cargo-ai connection connector autocomplete \
  --connector-uuid <hubspot-connector-uuid> \
  --slug listObjectProperties \
  --params '{"objectType": "contacts"}'
# → Returns: email, firstname, lastname, phone, etc.

# 5. Use these values in your workflow node config

Using connector actions in workflows

Connector actions are used as nodes in workflow graphs. To use an action:

bash

# 1. Find your connector UUID
cargo-ai connection connector list
# → Filter the output by integrationSlug to find the right connector

# 2. Discover available actions for the integration
cargo-ai connection integration get <integration-slug>
# → actions are keyed by actionSlug, with config.jsonSchema for each
# → Or use get-documentation for a plain text overview
# → Or use native-integration get for built-in Cargo actions (not third-party)

# 3. Reference the connector and action in a node graph
# See cargo-orchestration references/nodes.md for the full node syntax

Example connector node (Clearbit company enrichment):

json

{
  "uuid": "node-uuid",
  "slug": "enrich",
  "kind": "connector",
  "integrationSlug": "clearbit",
  "actionSlug": "company_enrich",
  "connectorUuid": "<clearbit-connector-uuid>",
  "config": {
    "domain": {
      "kind": "templateExpression",
      "expression": "{{nodes.start.domain}}",
      "instructTo": "none",
      "fromRecipe": false
    }
  },
  "childrenUuids": ["end-node-uuid"],
  "fallbackOnFailure": false,
  "position": { "x": 0, "y": 166 }
}

Help

Every command supports

--help

bash

cargo-ai connection connector list --help
cargo-ai connection connector create --help
cargo-ai connection integration list --help

cargo-connection

NPX Install

Tags

SKILL.md Content

Cargo CLI — Connections

Prerequisites

Key concepts

Discover resources first

`integration get`
vs
`native-integration get`

Quick reference

Connectors

Integrations

Connector autocomplete — fetching available values for action fields

How to detect autocomplete fields

How to call connector autocomplete

Autocomplete with parameters

Response format

End-to-end example: configuring a HubSpot action

Using connector actions in workflows

Help

cargo-connection

NPX Install

Tags

SKILL.md Content

Cargo CLI — Connections

Prerequisites

Key concepts

Discover resources first

integration get vs native-integration get

Quick reference

Connectors

Integrations

Connector autocomplete — fetching available values for action fields

How to detect autocomplete fields

How to call connector autocomplete

Autocomplete with parameters

Response format

End-to-end example: configuring a HubSpot action

Using connector actions in workflows

Help

`integration get`
vs
`native-integration get`