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
Cookbooks
SLSignals

Social listening

Find the LinkedIn conversations worth joining every week: each Monday the week's public LinkedIn posts about the problem you solve are judged against your ICP, and one Slack digest lists the posts worth joining and the commenters who look like buyers, each with a link.

Installation
Set up the social-listening cookbook in this project. 1. If the Cargo CLI is not installed yet, follow every step in https://api.getcargo.io/INSTALL.md 2. From the Cargo project, run: cargo-ai project add cookbook/social-listening 3. Then follow .claude/skills/social-listening/SKILL.md. Stop for my approval before any paid call, and stop at "cargo-ai project plan" before deploying anything.
Paste it into Claude Code, Cursor, Codex, Gemini CLI, Devin or Replicas.
$cargo-ai project add cookbook/social-listening
Run it in your Cargo project. Copies the example in, and deploys nothing.

Say this to your agent

Every Monday, tell #gtm-signals which LinkedIn conversations about lead routing are worth joining.

Illustrative output #

Fictional records, to show the shape of what comes back.

text
:ear: *What the market said this week*
_Routing breakage after CRM migrations came up three times._

*Worth joining*
• Dana Ruiz, VP RevOps at Fabrikam: "Our Salesforce migration broke every
  routing rule we had" — ICP persona, pain "routing breaks on field changes"
  (linkedin.com/posts/dana-ruiz_fab…) · 41 comments
• Wingtip Toys Engineering: a teardown of hand-built lead routing — category
  term "speed to lead" (linkedin.com/posts/wingtip…) · 12 comments

*Warm engagers*
• Sam Okafor, Head of Revenue Operations at Contoso, on Dana's post:
  "We rebuilt ours three times this year." (linkedin.com/in/sam-okafor)

_Searched: 40 posts read, 3 already surfaced_

Forty posts were read; two were picked and recorded in surfaced_posts, one commenter matched an ICP persona, and nothing was sent to anyone.

What you will be asked #

InputWhy
searchKeywords (infra/models/linkedin-posts.ts)Looked upIt is what you buy each week. Positioning copy as keywords returns vendors talking to each other; buyer language returns buyers.
limit (infra/models/linkedin-posts.ts)AskedIt is the weekly spend ceiling on the search.
channelId (infra/agents/listener.ts)AskedThe digest names people. Locked so it never lands in a customer shared channel.

Done when #

  • node --import tsx evals/contract.mjs passes
  • cargo-ai project plan reports the agent, the two models, the three connectors and the two folders
  • the first sync landed rows in linkedin_posts, all from the past week, no more than limit
  • one digest landed in the locked channel in the references/digest.md shape, every pick citing a context line and linking its post
  • surfaced_posts has one row per pick plus one digest-<date> row, and no column holding a person
  • a second run the same day posted nothing and read no comments
  • the run transcript shows no LinkedIn action other than searchPostComments, and only on picks
  • every quoted comment exists on the linked post, and every employer shown is in the commenter’s own headline

What it costs #

Read the live price of each paid step immediately before the plan, and say each one out loud:

  • cargo-ai connection integration get linkedin: the fetchPosts extractor (per post returned, so the weekly ceiling is limit times that price) and searchPostComments (per comment returned).
  • cargo-ai orchestration action list postMessage --kind connector --integration-slug slack.

The weekly cost is one search capped by limit, comment reads on at most five posts each capped by the prompt’s comment limit, one Slack post, and the agent run billed as LLM tokens through the Anthropic connector. On the live run the agent run, not the search, was most of the bill: it reads the ICP, personas, objections and insights before it judges a post. A re-run that stops at the ledger costs a small fraction of a full run. Read the run’s usage after the first week (cargo-ai ai message get) before you widen limit.

To find the LinkedIn conversations about your problem worth joining, search the week’s public posts for your buyers’ own words and judge them against your ICP. Every Monday this cookbook syncs one capped post search, has an agent pick at most five posts and up to ten commenters who look like buyers, and posts one digest to a locked Slack channel. It never engages on anyone’s behalf.

shellscript
cargo-ai project add cookbook/social-listening

What it does #

  • Syncs the past week’s LinkedIn posts for your buyer-language keywords every Monday.
  • Drops posts already surfaced, then picks at most five worth joining, each tied to a context line.
  • Reads comments on those five only, and quotes up to ten commenters whose headline matches an ICP persona.
  • Posts one digest, then records the picked posts in a ledger so none headlines twice.

What’s inside #

Adds 9 resources.

FileResourceRole
infra/models/linkedin-posts.tsdefineModel (fetchPosts)the weekly, capped keyword search: what you buy
infra/models/surfaced-posts.tsdefineModel (native)the ledger: one row per post surfaced, no people
infra/agents/listener.tsdefineAgentthe cron, the reads, the comment pull, the locked post
infra/agents/listener.prompt.ts(not a resource)read context, pick, read comments, post, record
infra/connectors/linkedin.tsdefineConnector (linkedin)the search and the comment read; no engagement wired
infra/connectors/slack.tsdefineConnector (slack)the post path
infra/connectors/anthropic.tsdefineConnector (anthropic)the model the agent runs on
infra/folders/index.tsdefineFolder ×2where the agent and the models are filed
references/digest.md(not a resource)the digest shape and the rule for each section

Why the search is in the model #

The search is a paid source: it bills per post returned. That makes its query the purchase, so it sits in the model’s config with a limit, rather than pulling everything and narrowing in SQL. The sync replaces the rows each week, which is why “already surfaced” lives in a separate ledger.

Placeholders (edit before deploy) #

  1. searchKeywords in infra/models/linkedin-posts.ts: buyer-language phrases and competitor names from your workspace context.
  2. channelId in infra/agents/listener.ts.
  3. languageModel: any Anthropic model the workspace’s connector can reach.

What it does not do #

It does not like, comment, connect, message, follow or visit a profile; store a list of people; look anyone up beyond the comment they wrote; or post anywhere but the locked channel.

Version0.1.2
LicenseMIT
Source
Deploys
  • agents
  • connectors
  • models
For
  • Marketing
  • Sales development
Integrations
  • Anthropic
  • LinkedIn
  • Slack
Content
  • Say this to your agent
  • Illustrative output
  • What you will be asked
  • Done when
  • What it costs
  • What it does
  • What's inside
  • Why the search is in the model
  • Placeholders (edit before deploy)
  • What it does not do
More in Signals
  • New hire detection
  • Visitor identification
  • Readiness scoring
Next: Engagement
  • Inbound qualification
  • Agentic engagement

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