> ## 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 every step in https://api.getcargo.io/agent-install.txt` 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://github.com/getcargohq/cargo-skills/blob/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.

# Phantombuster

> Connect Phantombuster to launch agents and sync their results in your workflows.

## How to set up Phantombuster

### Authentication

Phantombuster uses API key authentication:

1. Sign up at [phantombuster.com](https://phantombuster.com)
2. Open your Workspace settings
3. Copy your API key
4. Paste the API key in Cargo when connecting

<Note>
  **Code slugs** — integration slug: `phantombuster`. Action: `launchAgent`. In a [workflow](/workflows/overview), declare the connector in `uses` and call `uses.<key>.launchAgent(...)`.
</Note>

Cargo spreads requests at up to 100 calls per minute against the Phantombuster API.

## Phantombuster actions

### Launch Agent

Launch a Phantombuster agent, wait for the run to finish, and return its result items.

**Required fields:**

* **Agent**: Select the agent to launch

**Optional fields:**

* **Argument**: JSON argument to pass to the agent

**Use case:** Trigger a Phantombuster scraping or automation agent from a workflow and use its output downstream.

## Data models

Phantombuster also provides a **Fetch Agent Results** extractor, so you can sync agent output into Cargo as records without launching the agent yourself:

* Pick the agent to fetch results from
* Cargo fetches the result object of each finished agent run and turns items into records (columns are inferred from the items, deduplicated by a content hash)
* Creating the model backfills the agent's past runs — Cargo walks back through the agent's history, not just its most recent runs
* Syncs are then incremental — only runs that ended after the last sync are fetched, at most every 30 minutes

**Use case:** Keep a Cargo model up to date with the leads a scheduled Phantombuster agent produces.

## Best practices

* Validate the **Argument** field is valid JSON — the action fails otherwise
* Use the extractor (rather than the action) when the agent runs on its own schedule in Phantombuster
* Agent runs that error, crash, or time out fail the action with the agent's exit message