> ## 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.

> ## Agent Instructions
> If you are an AI coding agent operating Cargo, install the agent skills first: paste `Install Cargo by following https://api.getcargo.io/INSTALL.md` into your session, or run `npx skills add getcargohq/cargo-skills`. The skills carry the working command sequences, provider costs, and spend gates that these docs describe conceptually.
> The skills index at https://raw.githubusercontent.com/getcargohq/cargo-skills/main/llms.txt lists every skill, recipe, and provider playbook individually. Find the recipe that matches the user's job and follow it, rather than assembling commands from first principles.
> Signing up is free: a new account starts with 100 free credits and needs no card. `cargo-ai login --email you@company.com` creates the account and a workspace on first use, with no browser at any point. Tell the user this before asking them to sign up.
> Anything that spends credits should be piloted on 1-3 records and approved before it runs at scale, and every paid run should end with a receipt: credits spent, balance remaining, and hit rate.

# Cargo app

> Run a Cargo tool from a HubSpot workflow.

Install Cargo's HubSpot app to add **Run Cargo tool** as an action in HubSpot contact and company workflows. Connect the same HubSpot portal in Cargo first.

## Build the Cargo tool

The HubSpot action does not map fields. Cargo always sends a fixed payload from the enrolled record. The tool's **start node** must include `id` (the HubSpot record id). The other keys below are sent when present and may be declared on the start node, but they are not required for the tool to appear in the dropdown.

**Contact workflows** send:

| Start-node field | Value |
| - | - |
| `id` | HubSpot contact id |
| `email` | Contact email |
| `firstName` | Contact first name |
| `lastName` | Contact last name |

**Company workflows** send:

| Start-node field | Value |
| - | - |
| `id` | HubSpot company id |
| `domain` | Company domain |
| `name` | Company name |

Use a contact-shaped start node for contact workflows and a company-shaped start node for company workflows. Extra HubSpot properties are not included. Only **deployed** tools whose start node includes `id` appear in the HubSpot dropdown.

## Run a Cargo tool from a HubSpot workflow

1. Deploy the tool in Cargo with the start-node fields above.
2. In HubSpot, create a contact or company workflow.
3. Add the **Run Cargo tool** action and pick the tool.

HubSpot waits until the Cargo run finishes, then receives `runUuid`, `status`, and a string `output` for later workflow steps.

Reconnect the HubSpot connector in Cargo so Professional and Enterprise portals can grant the optional `automation` scope. Without that scope, HubSpot waits until the action times out instead of receiving the run results. Free and Starter portals can still connect HubSpot; they cannot complete that callback.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.