AI and Agents
AI and Agents
Use OutboundSync's API, Agent Skills, and Webhooks in agentic workflows — plus CRM AI on HubSpot, Salesforce, Close, Attio, Pipedrive, and HighLevel.
When to use this guide: You are wiring OutboundSync into an agent harness (Cursor, Claude Code, Codex, and similar), or you want ChatGPT / Claude / in-CRM AI to reason over outbound activity OutboundSync already synced into HubSpot, Salesforce, Close, Attio, Pipedrive, or HighLevel.
OutboundSync supports agentic GTM work on two tracks:
- First-party surfaces — hosted MCP, the public API, installable Agent Skills, and Sync Monitoring Webhooks — so agents can inspect readiness, run structured workflows, and react when outbound→CRM sync fails or recovers.
- CRM AI surfaces — each CRM’s own assistants, connectors, or MCP servers over data OutboundSync wrote into that CRM. OutboundSync does not ship a first-party ChatGPT or Claude app for CRM chat; you use the CRM vendor’s path (and our HubSpot how-tos where we have them).
Agentic workflows with OutboundSync
Section titled “Agentic workflows with OutboundSync”Use these together. A common loop is: connect MCP (or Skills / REST) before launch, then Webhooks notify your stack when sync health changes after you send.
| Surface | What agents use it for | Start here |
|---|---|---|
| MCP | Call OutboundSync API v1 tools from Cursor, Claude Code, and similar without REST boilerplate | OutboundSync MCP setup |
| API | Preflight and inspect CRM connections, Sources, account status, and webhook config without opening the admin UI | API overview |
| Agent Skills | Install once (npx skills), then ask in plain language — launch readiness, CRM analysis, copy, deliverability |
Agent Skills |
| Webhooks | Receive signed sync.failed / sync.recovered POSTs so an agent or ops handler can alert, open a ticket, or re-check the pipeline |
Webhooks |
Inbound SEP paste URLs are still Sources (engagement → OutboundSync). Product Webhooks are OutboundSync → your HTTPS endpoint for Sync Monitoring — see Sources and delivery if you need the inbound path.
Skills vs CRM AI
Section titled “Skills vs CRM AI”Keep the jobs separate:
| Job | Prefer | Why |
|---|---|---|
| How do I use the OutboundSync API / which skill next? | OutboundSync API skill + API docs | Auth, vocabulary, discovery, routing |
| Am I ready to launch? Sources wired? Sync healthy? | OutboundSync Preflight + API | Reads OutboundSync account/connection state — not a substitute for CRM chat |
| Sync Monitoring webhooks / deliveries / sync.failed | Sync monitoring + Webhooks | Platform-emitted alerts — not SEP Sources paste URLs |
| Campaign replies, follow-ups, platform attribution from fields already in HubSpot or Salesforce | OutboundSync CRM analysis | Structured intents over OutboundSync engagement signals in those CRMs (no OutboundSync API key) |
| Cold copy, omnichannel plans, deliverability, agency/integration lookups | Other Agent Skills | Playbooks that do not require opening the CRM UI |
| “What happened on this Account / Lead / person in the CRM?” | That CRM’s AI or MCP (below) | Sees the same notes, tasks, EmailMessages, and timeline OutboundSync wrote — plus the rest of the CRM |
Deeper Salesforce, Close, Attio, Pipedrive, and HighLevel guidance inside the public skills pack is planned after this docs hub lands. Until then, use CRM analysis for HubSpot/Salesforce field questions, Preflight for wiring, and each CRM’s own AI/MCP for live record chat.
CRM AI surfaces by product
Section titled “CRM AI surfaces by product”OutboundSync’s job is to land outbound activity on the right CRM records. Once that data is present, use the CRM vendor’s AI path — we do not duplicate every connector tutorial here (HubSpot is the worked example).
| CRM | In-CRM AI | External agents (ChatGPT, Claude, Cursor, …) | OutboundSync data to ask about |
|---|---|---|---|
| HubSpot | HubSpot’s AI features on contacts/companies | ChatGPT connector · Claude connector · remote MCP (endpoint mcp.hubspot.com) for Cursor and other MCP clients — OutboundSync how-tos: HubSpot guides below |
Timeline events, engagement, and properties OutboundSync updates |
| Salesforce | Agentforce / Einstein on CRM objects | ChatGPT · Claude · Cursor — hosted MCP overview (endpoint pattern api.salesforce.com/platform/mcp/v1/…) |
Tasks, EmailMessage / activity OutboundSync writes — see Identifying OutboundSync activity |
| Attio (beta) | Ask Attio inside the workspace | Install Attio from Claude Connectors or ChatGPT Apps (setup) · Attio MCP docs for Cursor and other clients (endpoint mcp.attio.com/mcp) |
Notes on people, plus OutboundSync custom-object records when the write toggle is on — Attio CRM beta |
| Close (beta) | Chloe AI and Close workflows inside Close | ChatGPT app · Claude Connectors (search Close) · Cursor — Close MCP docs (endpoint mcp.close.com/mcp) |
Lead activity OutboundSync syncs into Close — Close CRM beta |
| Pipedrive (beta) | Pipedrive AI on Person records | Pipedrive MCP for ChatGPT, Claude, and other MCP clients | Notes OutboundSync writes on Persons — Pipedrive CRM beta |
| HighLevel (beta) | HighLevel AI on Contact records | HighLevel MCP for ChatGPT, Claude, Cursor, and other MCP clients — setup guide | Notes OutboundSync writes on Contacts — HighLevel CRM beta |
Practical pattern: keep OutboundSync Skills + API for launch and Sync Monitoring; connect the CRM’s MCP or connector when you want the agent to query or summarize synced outbound activity next to pipeline and ownership data.
Vendor MCP endpoints, OAuth, and scopes change — use the CRM’s own setup docs as source of truth. OutboundSync only needs a healthy CRM connection and sync so the activity exists for those tools to read.
HubSpot data in ChatGPT and Claude
Section titled “HubSpot data in ChatGPT and Claude”These are the step-by-step OutboundSync guides for HubSpot’s connectors (third-party AI on top of HubSpot records OutboundSync has populated).
