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
~/cargo-x-slack/

Tag Cargo in Slack.It does the GTM work.

Anyone in the channel can mention Cargo. The same agents and integrations you run in Cargo answer in the thread.

Start building
SlackThread#gtm
Guillaume Cabane9:41 AM

Ramp just raised a Series D. Worth a look before the quarter ends?

Reply…
~/in-practice/

Ask the way you would ask a colleague.

No syntax and no tool names. Tag Cargo, keep working, and the answer comes back in the thread.

@Cargo who should we talk to at Ramp?

It finds the buying committee, skips anyone already in the CRM, and drops the rest in the thread.

@Cargo this account just hired a VP Sales. What do we know?

It reads the record, the playbooks, and recent activity, then writes a brief the whole channel can see.

@Cargo enrich this list and put the file here.

The batch runs on Cargo. The file comes back in the thread you asked from.

@Cargo does this fit our ICP?

It checks the account against the definition your team wrote, and quotes the line it used.

@Cargo update HubSpot with what you just found.

It writes back through the connector you already set up, with your field mapping and your dedup rules.

@Cargo catch me up on this thread.

It reads the thread it was tagged in and writes back what was decided and who owns what.

~/why-slack/

The channel is the runtime.

Cargo in Slack is the same GTM you already declared, reachable from the place the team already talks.

One agent the channel shares

Anyone in the channel can tag Cargo and pick up the thread. It is closer to a teammate than to a private chat.

Multiplayer by default

Your workspace, not a demo

The same integrations, records, and playbooks your team already runs in Cargo. Nothing to re-import or re-authorize.

Bound to one Cargo workspace

Tag it and keep working

The reply lands in the thread when the work is done: thinking state, stop button, streamed text. You do not have to watch it.

Asynchronous by design

Plays post here too

Agents you mention, and plays you already run, send messages, files, and Block Kit layouts into the same channels.

One Slack app, every agent

Questions people ask

Privacy, accuracy, and how to get help.

Mention Cargo in a watched channel, or DM it. The agent replies in thread with Slack's native thinking state, stop button, and streamed text. Anyone in the channel can pick up the conversation. Slack Marketplace lists one Cargo app; each agent still shows its own name and icon in the thread.
Yes. Connecting Slack binds the Slack team to one Cargo workspace. The agent sees the integrations, records, and playbooks that workspace already has. Plays and tools can also post into the same channels.
No. Cargo agents use large language models. AI-generated responses, summaries, and other outputs may not always be accurate. Review important results before acting on them.
No. Slack's native agent experience — the thinking state, the stop button, and streamed text — needs a Slack plan that includes it. Everywhere else Cargo still answers in the thread: the reply posts as a placeholder and fills in when the agent is done. Posting messages from plays and tools works on every plan.
No. Cargo does not use Slack data or any Customer Content to train foundation models. Messages an agent is invoked on are stored as run history so you can inspect what ran, then deleted with the rest of the workspace after the contract ends.
Email hello@getcargo.io. You do not need a Cargo account or any other login. We respond within two business days. The support page is https://www.getcargo.ai/support. The privacy policy is https://www.getcargo.ai/privacy.
~/get-started/

Pair Slack, then tag Cargo.

Install from the Slack Marketplace, or connect Slack from an existing workspace. Invite the app to a channel and mention it, or open a DM.

Connect Slack

Authorize the workspace from Cargo. That binds the Slack team to one Cargo workspace.

Slack integration docs

Mentions, DMs, watched channels, and posting from plays.

Support

Email hello@getcargo.io. No account or login required. We respond within two business days.

Trusted by GTM teams at

  • Augment Code
  • Weights & Biases
  • Dust
  • WorkOS
  • Braintrust
  • Descript
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 Gojiberry

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

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

$ npm install -g @cargo-ai/cli