A revenue engine on your stack

Name: Cargo
SKU: cargo
Availability: InStock

Workato is an enterprise iPaaS built on recipes. Cargo is GTM infrastructure: accounts, enrichment, routing and plays as primitives.

Start building

Trusted by GTM teams at

Augment Code
Weights & Biases
Dust
WorkOS
Braintrust
Descript
Alaan
Engine
Scaleway
Preply
DataDome
Oneflow

A recipe moves a payload. A play acts on the account.

Same company, different jobs. Workato moves data between systems; Cargo decides what that data means for ownership and pipeline.

Workato and Cargo compared
	Workato	Cargo
Built for	Enterprise integration across the company	GTM infrastructure for revenue-critical workflows
Artifact	A recipe: connectors, steps, and actions	An engine: models, plays, and agents
Starting point	Triggers, payloads, and API steps	Accounts, contacts, territories, and CRM state
GTM logic	Custom-built on top of every recipe	Native: enrichment, routing, scoring, sync
GTM as code	Recipes built in the Workato recipe editor	The workspace in TypeScript, in your git repo
Best when	The job is connecting systems	The job is running the revenue engine

In short. Use Workato to move data between systems. Use Cargo when that data has to decide ownership, enrichment, routing, or pipeline.

What recipes make you rebuild

Workato's primitives are connectors and steps. Cargo's are the objects a revenue team already thinks in.

One GTM data model
Accounts, contacts, deals and custom objects every play reads.
Companies
2 hours ago
All records
FilterSort12,480 records6/24 columns
Name+23
Domain
Employees
Country
Industry
ICP fit
Add column
Northwind
northwind.com
420
United States
Logistics
82
Contoso
contoso.com
1,200
France
Software
74
Globex
globex.com
3,400
Germany
Manufacturing
91
Initech
initech.com
260
United States
Software
68
Fabrikam
fabrikam.com
880
France
Retail
55
Umbrella
umbrella.com
2,100
United Kingdom
Healthcare
79
Stark Logistics
starklogistics.com
640
United States
Logistics
88
Wayne Freight
waynefreight.com
1,450
Spain
Logistics
71
Plays that fire on change
A row updates, a play runs: research, qualify, engage. Traced.
Route inbound leads
TriggerEditorRecordsMetrics
Schedule
Type*
ManualEnroll records manually
Real-timeTrigger your play when new records are added
IntervalSchedule your play to run on a set interval (e.g., once per hour)
CronSchedule your play using a cron expression
DependencySchedule after a play finished running
Interval*
Every hour
Syncs are scheduled in UTC
Conditions
Filter
Lifecycle stage is LeadANDEmail is not empty
Add group
Changes
Mode*
New records onlyOnly new records that match the conditions will be enrolled in the play
New and updated recordsNew and updated records that match the conditions will be enrolled in the play
FullProcess all matching records
CustomAdvanced mode
Changes included*
AddedUpdatedUnchanged
Enrollment
Rule*
Always enrollEnroll the record into a new play run every time the trigger fires for that record
Enroll onceOnly enroll each record once, even if the trigger fires multiple times for the same record
If is not currently enrolledOnly enroll a record if it's not already in an active run, preventing concurrent runs
Save
Model
Contacts
The model associated with this play. Each record within this model is eligible for enrollment in the play.
Enroll manuallySync now
CRM-safe writes
Dedupe, protected fields and attribution, built in.
Enabled
Route inbound leads
TriggerEditorRecordsMetrics
Search...
2/2 nodesFilter5/5 statusesAll versionsAll batchesAll dates
1,284 records
Startstart
Update ownerupdate_owner
Ada Lovelace
Owner updated
Grace Hopper
Owner updated
Alan Turing
Owner updated
Katherine Johnson
No Salesforce lead matches this email
Edsger Dijkstra
Mary Jackson
Owner updated
Claude Shannon
Owner updated
Barbara Liskov
Owner updated
Default
Routing that knows the org
Territory, capacity, ownership and fallback, not a branch in a recipe.
Back to appWorkspaceGeneralBillingUsageUsersRolesIntegrationsDomainsRevenue organizationAPIEnvironmentSystem of record
Revenue organization
New territoryNew capacity
MembersTerritoriesCapacities
A group of members that shares incoming records. Weights and a fallback decide who is next.
Territories3 territories
United StatesInbound from North America
2 membersAdded 3 days ago
FranceInbound from France
1 memberAdded 3 days ago
EMEAEverything else in Europe
1 memberAdded a week ago
United States
EditAllocations
Label*
United States
Choose a label to your territory
Color*
Choose a color to represent your territory
Description
Inbound from North America
Choose a description
Members*
AMAlice Martin
50
SOSam Okoro
50
Add member
Pick members you want to be part of your territory
Fallback Member
DCDana Cole
The member that will be used when other territory members are not available (e.g. Capacity reached).
Save
Enrichment without the contracts
Credit-based providers and waterfalls. Test before you sign a vendor.
Enabled
Enrich inbound leads
TriggerEditorRecordsMetrics
Search...
4/4 nodesFilter5/5 statusesAll versionsAll batchesAll dates
1,284 records
Startstart
Find emailfind_email
Enrich companyenrich_company
ICP fitscore_icp
Ada Lovelace
ada@northwind.com
Northwind, 420 employees
82/100
Grace Hopper
grace@contoso.com
Contoso, 1,200 employees
74/100
Alan Turing
No email found, 0 credits
Globex, 3,400 employees
91/100
Katherine Johnson
katherine@initech.com
Running...
Default
Agents on the same runtime
Agents see account state, ICP and history, and follow your rules.
Account researcher
TriggerEditorActivities
Deploy
Instructions
Research the account, score it against our ICP and write a two-line brief for the owner. Use our ICP definition from context, not your own.
Actions
Enrich companyenrich_company
Search the webweb_search
Get companyhubspot_get_company
The building blocks of the agent. They are the actions the agent can take. The agent will use the actions to achieve the goal.
Advanced settingsClaude Sonnet 5
Research Northwind and tell me if it fits our ICP.
Reasoned for a few seconds
Get company0
Enrich company1
Search the web2
Northwind fits: 82/100. 420 employees, logistics, and two open SDR roles, which is the growth trigger in your ICP.
It sits in the United States territory, so the owner is Alice Martin. Lead with routing: their HubSpot assigns inbound by hand today.
Ask agent...

GTM as code, in your repo.

Your whole Cargo workspace is TypeScript in git: every change reviewed, planned and reversible.

In your repoThe whole workspace, declared in TypeScript.
Planned on every pull requestcargo-ai project plan shows the diff. Merging deploys it.
Undone with git revertRevert the commit and the previous version deploys.
Written by your coding agent: Claude Code, Cursor or Codex.

import { defineMember, defineTerritory } from "@cargo-ai/cdk";
 
const alice = defineMember("alice@acme.com");
const dana = defineMember("dana@acme.com");
 
// United States accounts go to Alice, Dana covers
export const unitedStates = defineTerritory("united-states", {
  label: "United States",
  members: [{ ref: alice, weight: 1 }],
  fallback: dana,
});

When to choose which

Both products have a real job. The decision is which job you are hiring for.

Choose Workato when…

The mandate is “connect these thirty systems”
Go-to-market is one consumer among many
Procurement needs an enterprise iPaaS
Recipes already run the company's integration estate

Choose Cargo when…

The job is the revenue engine, not the integration estate
Accounts, enrichment, routing, and CRM writes are the work
You want plays and agents, not recipes for GTM concepts
Cost should follow GTM volume, not iPaaS task counts

Both true. Workato is the better iPaaS. Cargo is the better GTM runtime. Teams often keep Workato for the integration estate and run the revenue engine on Cargo.

Frequently asked questions

How Cargo and Workato differ, when to use each, and whether teams run both.

Workato is an enterprise integration platform: it connects many systems to each other with governance, audit and support around it, and the artifact is a recipe. Cargo orchestrates a revenue engine, where the artifact is the engine itself declared in code, and where accounts, contacts, territories, enrichment and routing are primitives rather than connectors and steps.

When the problem statement is genuinely "connect these thirty systems" and go-to-market is one consumer among many. Workato is built for an IT or ops function with an integration mandate across a whole company, and it brings the governance and support an enterprise procurement process asks for.

Its primitives are connectors and steps, not models, plays and agents, so every GTM concept has to be rebuilt on top. The pricing also assumes integration workloads rather than always-on, high-volume revenue ones, which is where the cost of running an engine on it starts to look wrong.

Often, and it is a reasonable architecture. Workato keeps the enterprise integration estate it was bought for, and Cargo owns the revenue engine that sits on top of the data those integrations move.

“Essential. Innovative. Indispensable. Cargo let you build your unique growth engine, a much-needed solution in the market today.”

Guillaume Cabane · Co-Founder @Hypergrowth

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

//////// /////// //////// //////// /////// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// ///////// //////// /// //// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// //////// /// /// /// /// /////// ///////

Workato and Cargo compared
	Workato	Cargo
Built for	Enterprise integration across the company	GTM infrastructure for revenue-critical workflows
Artifact	A recipe: connectors, steps, and actions	An engine: models, plays, and agents
Starting point	Triggers, payloads, and API steps	Accounts, contacts, territories, and CRM state
GTM logic	Custom-built on top of every recipe	Native: enrichment, routing, scoring, sync
GTM as code	Recipes built in the Workato recipe editor	The workspace in TypeScript, in your git repo
Best when	The job is connecting systems	The job is running the revenue engine

Workato

Cargo

Built for

Enterprise integration across the company

GTM infrastructure for revenue-critical workflows

Artifact

A recipe: connectors, steps, and actions

An engine: models, plays, and agents

Starting point

Triggers, payloads, and API steps

Accounts, contacts, territories, and CRM state

GTM logic

Custom-built on top of every recipe

Native: enrichment, routing, scoring, sync

GTM as code

Recipes built in the Workato recipe editor

The workspace in TypeScript, in your git repo

Best when

The job is connecting systems

The job is running the revenue engine

import { defineMember, defineTerritory } from "@cargo-ai/cdk";

const alice = defineMember("alice@acme.com");

const dana = defineMember("dana@acme.com");

// United States accounts go to Alice, Dana covers

export const unitedStates = defineTerritory("united-states", {

label: "United States",

members: [{ ref: alice, weight: 1 }],

fallback: dana,

});

A revenue engine on your stack

A recipe moves a payload. A play acts on the account.

What recipes make you rebuild

One GTM data model

Plays that fire on change

Schedule

Conditions

Changes

Enrollment

CRM-safe writes

Routing that knows the org

Enrichment without the contracts

Agents on the same runtime

GTM as code, in your repo.

When to choose which

Frequently asked questions

Build the self-driving GTM engine

A revenue engine on your stack

A recipe moves a payload. A play acts on the account.

What recipes make you rebuild

One GTM data model

Plays that fire on change

Schedule

Conditions

Changes

Enrollment

CRM-safe writes

Routing that knows the org

Enrichment without the contracts

Agents on the same runtime

GTM as code, in your repo.

When to choose which

Frequently asked questions

Build the self-driving GTM engine