Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • PrimitivesData ModelsYour companies, contacts and deals, merged from every sourceContextWhat your team knows, as files every agent readsTerritoriesWho sells where, defined onceMailboxesMailboxes in your reps' names, warmed up and kept under limitsToolsThe actions your agents, plays and reps callAgentsAI that researches, decides and writes, reading your contextPlaysWorkflows that run on a trigger or a schedule, with retriesAppsInternal apps for your reps, hosted on Cargo
    Add-onsChrome ExtensionSell faster, right in your browserButtonTrigger AI agents inside your CRMFormTurn any tool into an embeddable formSlackTag Cargo in Slack. It does the GTM workGitHubPlan on every pull request, deploy on merge
    MoreProjectsDefine your entire GTM in codeCLIUse Cargo from your terminalMCPUse Cargo from Claude and ChatGPTDeveloper resourcesCargo API docs, OpenAPI spec, auth docs, webhooks, MCP serverAPI ReferenceExplore the Cargo APIDocumentationLearn how to use CargoIntegrationsConnected to your entire GTM stack
  • VeriffHow Veriff replaced MuleSoft with Cargo under NetSuite, Stripe and SalesforceAugmentHow Augment Code routes developer sign-ups to reps in under an hourWeights & BiasesHow Weights & Biases ships a new purchase signal in 2 days on CargoSee all
  • Pricing
  • Cookbooks
  • Blog
Sign in

CI/CD for yourgo-to-market

Connect your GitHub repository. Every pull request gets a plan of what it will change, send and spend. Every merge deploys.

Start building
A pull request on GitHub: Cargo comments the plan of what the merge creates, its check passes, and the pull request is ready to merge
cargo-hqBotcommented 7 minutes ago · edited

Cargo deployment preview

1 to create, 0 to update, 3 unchanged.

ChangeResourceKindID
CreateInboundplayplay:inbound
All checks have passed
3 successful checks
  • Cargo Successful in 6m, 1 resource(s) would change
  • lint / lint (pull_request) Successful in 18s
  • typecheck / typecheck (pull_request) Successful in 31s
No conflicts with base branch
Merging can be performed automatically.
Merge pull request

From pull request to production

Every change goes through the pull request your team already reviews.

  1. 1. Plan

    Cargo comments what a merge would change.

    + play inboundcreate
    sends, at most2,140
    credits, at most4,280
  2. 2. Approve

    Past a limit, a reviewer adds the approval label.

    limit100 messages
    labelapprove-impact
    check Cargopassed
  3. 3. Deploy

    Merging deploys it as a service user.

    merge #128main
    deploysuccess
    run #1 Northwindto Alice
  4. 4. Roll back

    Revert and merge to put the workspace back.

    revert #128main
    play inboundprevious
    sends already madekept

Ask @cargo to fix iton the pull request.

Mention @cargo in a review comment. A coding agent pushes the fix to the same branch and replies.

How to set up @cargo
An example: on the pull request's diff, a reviewer asks @cargo to fix a line, Cargo pushes the fix to the same branch and replies in the thread
infra/workflows/score.ts1 commit by Cargo on inbound-play
11 export const sizeScore = (company) => {
12- const size = company.employeeCount;
12+ const size = company.headcount;
S

Sam

@cargo scoring still reads the old employee-count field. Fix it here.

Cargo

Fixed in a new commit on this branch. The plan comment is updated.

13 return size > 200 ? 30 : 10;
14 };

Connect a repository in three steps

Start from a Cargo project: cargo-ai project init creates one.

1. Install the Cargo GitHub app

Connect GitHub and install the app on the repository.

Settings → Connectors → GitHub

2. Connect the repository

Pick the repository, the production branch and the project folder.

Settings → States

3. Open a pull request

Cargo comments the plan. Turn off Deploy on push for plans only.

On GitHub

Questions people ask

Approvals, deletes, rollbacks and what still runs from a laptop.

No. Once the repository is connected in Settings → States, Cargo plans pull requests and deploys merges itself. There is no workflow file to write and no Cargo API token to store in GitHub. If you prefer your own CI, it can run the same two commands: cargo-ai project plan and cargo-ai project deploy.
No. A plan compiles the branch in a sandbox and compares it with what is deployed. The sandbox gets a copy of the deploy state and a read-only token for that one repository, and no Cargo credential.
A merge whose plays and one-off runs could send more than 100 emails, 100 LinkedIn actions or 100 chat messages, add more than 5,000 records to an audience, or spend more than 2,500 credits. The check also waits when a play that sends or spends cannot be counted. Adding the cargo:approve-impact label plans the pull request again and the check passes. Make the Cargo check required in branch protection so it actually blocks the merge.
It stays live. The plan lists it as Prune, and a deploy never deletes. Removing it is a deliberate cargo-ai project deploy --prune.
Not while Deploy on push is on: Cargo refuses deploys from anyone but the connection's service user, and --force does not get past it. Plan, import, pull and rollback keep working locally. To deploy by hand during an incident, turn Deploy on push off.
No. Reverting a play stops future enrollments, but it does not recall emails, LinkedIn actions or messages that went out. That is why the plan counts sends on the pull request, before they exist.
Three things: the Cargo GitHub app installed on the repository, a Cargo coding agent bound to it (running Claude Code, Codex or OpenCode), and "All pull requests" turned on in that agent's GitHub trigger. Without the setting, the agent only answers on pull requests it opened itself.
No. Planning means running the branch's code, and a fork is somebody else's. @cargo does not answer on them either.

Read the details

Each step above has its own page, with the commands and the limits.

GitHub deploys in the docs

Permissions, multi-project repos and limits.

Deploy changes on merge

What a pull request and a merge each do.

Preview what a merge will send

How the plan counts sends and credits.

Ask @cargo on a pull request

Declare the agent and who answers which mention.

Trusted by GTM teams at

  • <1 h to a repAugment Code
  • New signal in 2 daysWeights & Biases
  • Dust
  • −40% enrichment costWorkOS
  • Braintrust
  • 2x pipelineDescript
backed by y combinator

Build the self-driving GTM engine

Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.

Start building
Cargo
Backed byY CombinatorSOC 2 Type IICertified
LinkedinX

Product

Data ModelsContextTerritoriesMailboxesToolsAI AgentsPlaysAppsIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude CodeCodexCursorAll coding agents

Resources

ReportsBlogCustomer storiesCookbooksEnrichmentRoutingSignalsScoringCRM hygieneAd audiencesGTM skillsGTM EngineeringGlossaryCompareCargo x ClayCargo x WorkatoCargo x n8nCargo x DeeplineCargo x DefaultCargo x LeanDataCargo x UnifyCargo x ValleyCargo x GojiberryCargo x PhantomBusterCargo x ZapierCargo x ApolloCargo x Chili PiperCargo x Common RoomCargo x MakeCargo x Tray.io

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

SecurityTerms of servicePrivacy PolicyRefundsDPASupport
© 2026 Cargo
 ////////    ///////    ////////     ////////    ///////
///         ///   ///   ///   ///   ///         ///   ///
///         ///   ///   ///   ///   ///         ///   ///
///         /////////   ////////    ///  ////   ///   ///
///         ///   ///   /// ///     ///   ///   ///   ///
///         ///   ///   ///  ///    ///   ///   ///   ///
 ////////   ///   ///   ///   ///    ///////     ///////

$ npm install -g @cargo-ai/cli