Members - Cargo Documentation

A member is a person on your revenue team who can receive leads. Members are the atoms of the whole system: territories are pools of members, capacities cap how much each member can hold, and an Allocate node ultimately hands each lead to a single member.

Where members come from

Members are imported from a connected CRM rather than created by hand, so your Cargo team hierarchy stays in step with the source of truth in Salesforce, HubSpot, or another connector. Syncing pulls in each rep and keeps their details current; reps removed in the CRM stop receiving leads on the next sync.

Connect and configure your CRM first — Revenue Organization has no members to route to until a connector has synced your team in.

Anatomy of a member

Field	Description
`uuid`	Cargo’s stable identifier — the value you reference in a territory’s `members` array.
`name` / `email`	Identity, synced from the CRM.
`crmUserId`	The originating record in the connected CRM, used to write assignments back.
`metadata`	Custom attributes like languages, specializations, or region that you can branch on upstream of an Allocate node.

Manage members from the CLI

# Pull the latest team from a connector
cargo-ai revenue-organization member sync --connector-uuid <uuid>

# List members (and grab the UUIDs you reference in territories)
cargo-ai revenue-organization member list

member list is how you get the member UUIDs used in territory create --members and in fallback-member fields — sync first, then list.

Next steps

Territories

Group members into pools and distribute leads across them.

Capacities

Cap how many records each member receives within a time window.

Salesforce integration

Connect your CRM to import team members automatically.

Build a play

Create workflows that trigger lead allocation.

Overview Territories

​Where members come from

​Anatomy of a member

​Manage members from the CLI

​Next steps

Territories

Capacities

Salesforce integration

Build a play

Where members come from

Anatomy of a member

Manage members from the CLI

Next steps