I/O Mesh

GTM pipeline — sales automation on the mesh

Leads and automations often sit outside governed agent context. Native GTM pipeline on dept.sales.* (Beta growth-suite) compounds pipeline judgment you own. Salesforce stays available as a live CRM connector where you already run it — a catalog name is not Connected. No public lift %. Create a workspace when ready.

Who it's for

Founder or RevOps engineer — pipeline hygiene and lead scoring without a dedicated data team.

The problem

Leads arrive via webhooks, product signals, and CRM with no durable loop. Outreach automations live in n8n silos disconnected from governed agent context.

Outcome

Native GTM pipeline on dept.sales.* (Beta growth-suite) compounds pipeline judgment you own. Salesforce stays available as a live CRM connector where you already run it — a catalog name is not Connected. No public lift %.

Workflow map (2026)

Outbound and PLG automation silos (n8n, marketing tools) break agent context. Growth-suite marketing connectors (Mautic, Matomo, Twenty, EspoCRM, n8n) are Beta multi-tenant installs. Webhook fabric + CRM sync on the mesh keeps pipeline judgment owned; Salesforce is a live CRM connector where you already run it — catalog listing is not Connected.

Founder / RevOpsGrowth engMarketing ops

Build

Custom webhooks + Beta marketing/CRM growth-suite ingress on dept.sales/marketing.

Steer

Scored leads and campaign context agents can cite without re-upload.

Compound

Conversion and reply-rate loops measured on governed events (private evals; no public lift %).

Learning loop

Pipeline narratives compound on dept.sales.* (Beta growth-suite). Salesforce is a live CRM connector where you already run it — catalog listing is not Connected.

Questions agents answer

  • Which leads scored highest this week and why?
  • Draft outreach using live product usage plus CRM stage.
  • What touchpoints preceded this opportunity conversion?

How it works on I/O Mesh

  1. Step 1

    Webhook fabric

    Create custom webhook receivers with schema inference and policy preview — n8n (Beta multi-tenant install), Grok/Hermes, or any HMAC-capable HTTP client.

  2. Step 2

    Marketing connectors

    Mautic/Matomo (and related growth-suite) events on dept.marketing.events.* are Beta multi-tenant mesh installs. Funnel steps and multi-touch attribution feed the same mesh as CRM.

  3. Step 3

    Automation studio

    YAML DAG workflows with visual canvas and n8n handoff (Beta) — retire simple loops without losing governed batch paths; growth suite remains Beta.

  4. Step 4

    CRM API bidirectional sync

    Twenty and EspoCRM connectors (Beta multi-tenant installs) plus REST push/pull — pipeline state stays on I/O Mesh as system of record for agents. Salesforce is a live CRM connector where you already run it — catalog listing is not Connected.

Departments

  • Sales
  • Marketing
Operational mesh

dept.* stream patterns

  • dept.sales.events.lead
  • dept.marketing.events.mautic
  • dept.marketing.events.matomo
  • dept.sales.events.salesforce
Browse data product catalog →

What ships today

  • Custom webhook receivers with test-send and rotate-secret
  • Marketing automation + attribution (Mautic/Matomo Beta multi-tenant installs)
  • Automation studio with mesh publish nodes and n8n handoff (Beta)
  • CRM API connections for Twenty and EspoCRM (Beta; Salesforce is a live CRM connector where you already run it — catalog listing is not Connected)

Governed MCP tools

  • preview_email_campaign
  • dry_run_automation_workflow
  • summarize_campaign_context
Typical company stage
scaleup
Evaluation path
Leads and automations often sit outside governed agent context. Native GTM pipeline on dept.sales.* (Beta growth-suite). Salesforce is a live CRM connector where you already run it — a catalog name is not Connected. No public lift %. Create a workspace when ready.
Pricing
Estimate usage meters and add-ons

Outcome metrics

Leading indicator
Leads with scored context attached
Lagging indicator
Pipeline conversion, outreach reply rate

Related solutions

B2B SaaS

PLG-to-enterprise learning loops across engineering, product, sales, CS, and support — governed dept.* products agents can consume, not a company-wide vector dump.

GTM and RevOps

Revenue learning loops: pipeline, support burden, and renewal context on one fabric — QBR and forecast narratives from governed facts, not CRM-only copilots. Growth suite (Mautic, n8n) mesh installs sit on the same fabric.

Start compounding this workflow — create a workspace with the use case pre-selected.

Create a workspace Explore platform Browse all use cases