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
Blog

Draw Your Go-to-Market Resource Graph

16 Oct4min read
AurelienAurelien

To draw your go-to-market resource graph, run cargo-ai project graph: it prints every resource in your Cargo workspace (connectors, models, segments, plays, tools, agents and the rest) and what each one points at, as a Mermaid flowchart. Add --project to draw your repository instead, offline, and --plan to colour what the next deploy would create, update or delete.

Mermaid renders in GitHub, in most docs tools and in coding agents, so the graph can go straight into a README or a pull request comment.

The commands #

shellscript
npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com

cargo-ai project graph                          # the live workspace, as Mermaid
cargo-ai project graph --project                # the local project, offline, no API calls
cargo-ai project graph --project --plan         # mark what the next deploy changes
cargo-ai project graph --json > graph.json      # the same graph as JSON

--plan only works with --project, because the diff is between your code and its deploy state.

What comes back #

A Mermaid flowchart, left to right. Each resource is a node labelled with its kind and name, folders become nested subgraphs, and the arrow says what the edge means:

text
flowchart LR
  subgraph n0["Outbound"]
    n4["play: Expansion"]
  end
  n1["connector: HubSpot"]
  n2["model: contacts"]
  n3["segment: Expansion targets"]
  n1 -.-> n2
  n2 -.-> n3
  n3 -.-> n4
  n4 -->|"updateContact"| n1

That is the shape, not output from a real workspace. The edge kinds, read from source to target:

EdgeMeaning
usescalls a connector: a workflow action, an agent’s model or MCP server
feedsrecords flow: a connector into its model, a model into a segment, play or agent
callsinvokes a tool, agent, worker, MCP server or app
triggersa play starts the play scheduled after it; a connector’s events start an agent
parenta model unified under a parent model
relatesa relationship between two models
watchesan alert over a play, tool, agent or model

With --plan, created resources are green, updated ones amber and deleted ones red and dashed.

--json prints a versioned CargoGraph object (version, source, workspace, nodes, edges, unresolved, integrations). unresolved lists references the graph does not contain, such as a resource deleted outside the project or a modelRef to something the project does not declare. A workspace graph also carries each integration’s logo and colour; a project graph read offline does not.

When to use which #

  • The workspace graph answers “what is actually running”: everything in the workspace, including resources nobody declared in code.
  • The project graph answers “what does this repository declare”, and needs no login. If a resource file fails to load, the command prints the errors and exits rather than drawing a graph that silently omits the broken resources.
  • The plan graph is a review aid: paste it into a pull request so a reviewer sees which part of the engine a change touches. On a connected repository, the plan comment already lists the changes and what the merge sends.

To draw a single play, tool or run step by step rather than the whole workspace, use cargo-ai orchestration node diagram.

More on the lifecycle: GTM as code: the complete guide. Every resource the graph can contain is declared in a Cargo project.

~/run-it-on-cargo/

Build this workflow instead of reading about it.

Cargo is the GTM infrastructure your coding agent builds on: enrichment, scoring, routing and outreach, defined in code and run in production.

Start building
AurelienAurelienOct 16, 2026
On this page
  • The commands
  • What comes back
  • When to use which

Stay Informed with our
weekly Newsletter

Related articlesSee all articles
GTM Engineering
CI/CD for Go-to-Market: What It Means and How to Set It Up

CI/CD for GTM means every change to enrichment, scoring, routing and sequences ships as a pull request that is planned, checked, approved, deployed on merge, logged and reversible. What each software CI/CD step becomes for go-to-market, and how to set it up on Cargo.

AurelienAurelien·Nov 3, 2026
GTM Engineering
Require Approval Before a High-Impact Go-to-Market Change Goes Live

How Cargo holds a go-to-market pull request that would send or spend more than set limits until a reviewer adds the cargo:approve-impact label: the thresholds, what counts as high impact, who should approve, and what the gate does not catch.

AurelienAurelien·Nov 3, 2026
GTM Engineering
Test a Go-to-Market Change Before It Reaches Production

How to test a change to enrichment, scoring, routing or outreach before it runs on every lead: check the project offline, dry run an action, read the plan on the pull request, ship the play switched off and pilot it on 50 records, evaluate agents, and use a second workspace as staging.

AurelienAurelien·Nov 3, 2026

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