--- title: "AI and Agents" description: "Use OutboundSync's API, Agent Skills, and Webhooks in agentic workflows — plus CRM AI on HubSpot, Salesforce, Close, and Attio." canonical: "https://outboundsync.com/docs/integrations/ai-and-agents/" lastUpdated: "2026-08-04T00:00:00.000Z" sourceKind: "source-mdx" --- > **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, or Attio. OutboundSync supports agentic GTM work on two tracks: 1. **First-party surfaces** — 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. 2. **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 Use these together. A common loop is: **Skills** (or a custom agent) call the **API** before launch, then **Webhooks** notify your stack when sync health changes after you send. | Surface | What agents use it for | Start here | |---|---|---| | **API** | Preflight and inspect CRM connections, Sources, account status, and webhook config without opening the admin UI | [API overview](/docs/api/) | | **Agent Skills** | Install once (`npx skills`), then ask in plain language — launch readiness, CRM analysis, copy, deliverability | [Agent Skills](/docs/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](/docs/webhooks/) | Inbound SEP paste URLs are still **Sources** (engagement → OutboundSync). Product **Webhooks** are OutboundSync → your HTTPS endpoint for Sync Monitoring — see [Sources and delivery](/docs/how-it-works/webhooks-and-delivery/) if you need the inbound path. - [OutboundSync API](/docs/api/) — Create keys, verify /me, and inspect connections for agent or script preflight. - [Agent Skills](/docs/skills/) — Install the public skill pack for launch checks, CRM analysis, copy, and deliverability. - [Webhooks](/docs/webhooks/) — Register Sync Monitoring endpoints for sync.failed and sync.recovered. ## Skills vs CRM AI Keep the jobs separate: | Job | Prefer | Why | |---|---|---| | How do I use the OutboundSync API / which skill next? | OutboundSync [API skill](/docs/skills/api/) + [API docs](/docs/api/) | Auth, vocabulary, discovery, routing | | Am I ready to launch? Sources wired? Sync healthy? | OutboundSync [Preflight](/docs/skills/preflight/) + [API](/docs/api/) | Reads OutboundSync account/connection state — not a substitute for CRM chat | | Sync Monitoring webhooks / deliveries / sync.failed | [Sync monitoring](/docs/skills/sync-monitoring/) + [Webhooks](/docs/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](/docs/skills/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](/docs/skills/catalog/) | 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, and Attio 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 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](https://knowledge.hubspot.com/integrations/connect-your-hubspot-account-to-chatgpt) · [Claude connector](https://knowledge.hubspot.com/integrations/set-up-and-use-the-hubspot-connector-for-claude) · [remote MCP](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server) (endpoint `mcp.hubspot.com`) for Cursor and other MCP clients — OutboundSync how-tos: [HubSpot guides below](#hubspot-data-in-chatgpt-and-claude) | Timeline events, engagement, and properties OutboundSync updates | | **Salesforce** | Agentforce / Einstein on CRM objects | [ChatGPT](https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/chatgpt.html) · [Claude](https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/claude.html) · [Cursor](https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/cursor.html) — [hosted MCP overview](https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/hosted-mcp-servers-overview.html) (endpoint pattern `api.salesforce.com/platform/mcp/v1/…`) | Tasks, EmailMessage / activity OutboundSync writes — see [Identifying OutboundSync activity](/docs/integrations/crm/salesforce/setup-and-configuration/identifying-outboundsync-activity-in-salesforce/) | | **Attio** (beta) | [Ask Attio](https://attio.com/platform/ask) inside the workspace | Install Attio from Claude Connectors or ChatGPT Apps ([setup](https://mcp.attio.com/)) · [Attio MCP docs](https://docs.attio.com/mcp/overview) for Cursor and other clients (endpoint `mcp.attio.com/mcp`) | Notes and activity OutboundSync logs on people/companies — [Attio CRM beta](/docs/integrations/crm/attio/) | | **Close** (beta) | Chloe AI and Close workflows inside Close | [ChatGPT app](https://chatgpt.com/apps/close/asdk_app_694574813e548191bac45327be0a61d1) · Claude Connectors (search Close) · [Cursor](https://cursor.com/en-US/install-mcp?name=Close&config=eyJ1cmwiOiJodHRwczovL21jcC5jbG9zZS5jb20vbWNwIiwidHlwZSI6InN0cmVhbWFibGVIdHRwIn0%3D) — [Close MCP docs](https://help.close.com/integrations/close-mcp-server) (endpoint `mcp.close.com/mcp`) | Lead activity OutboundSync syncs into Close — [Close CRM beta](/docs/integrations/crm/close/) | **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 These are the step-by-step OutboundSync guides for HubSpot’s connectors (third-party AI on top of HubSpot records OutboundSync has populated). - [Using HubSpot data in ChatGPT](/docs/integrations/ai-and-agents/using-hubspot-data-in-chatgpt/) — Prompts and patterns for HubSpot connectors in ChatGPT. - [Connecting HubSpot to Claude](/docs/integrations/ai-and-agents/connecting-hubspot-to-claude/) — Set up Claude workflows using HubSpot data. - [ChatGPT connectors with HubSpot](/docs/integrations/ai-and-agents/chatgpt-connectors-with-hubspot/) — Connect HubSpot to ChatGPT and compare connector approaches. © 2026 OutboundSync. All rights reserved. Trademarks held by their owners.