Skip to main content
Swan integrates with the apps below. Under the hood they connect through a few different mechanisms, but from your side they all work the same way: connect the app once, and its actions become tools the agent can call directly — reading records, creating or updating them, managing lists or pipelines, and so on. Three integrations are deep enough to have their own pages: HubSpot, Salesforce, and Slack. Web scraping and public-web data collection are built into Swan itself (powered by Apify) — nothing to connect there.

​
Connecting an app

Connect an app from Tools — search or browse the catalog there and click the app’s card. Depending on the app, you’ll either go through an OAuth flow or paste in an API key generated from that app’s own settings — Swan tells you which when you go to connect it. Most connections are shared at the org level, so the whole team uses the same connection once it’s set up. (Reddit is the one exception today, connected per user.)

​
The catalog

  • CRM / sales: HubSpot, Salesforce, Attio, Pipedrive, Zoho CRM, Microsoft Dynamics 365, Close CRM
  • Prospecting / market data: Apollo, Hunter, SimilarWeb
  • Outreach and email platforms: Instantly, LemList, Reply.io, Outreach, HeyReach, ActiveCampaign, Mailchimp
  • Calls and meetings: Gong, Fireflies, Fathom, Recall.ai, Zoom
  • Scheduling: Calendly, Cal.com
  • Google Workspace: Calendar, Docs, Sheets, Meet, Ads, Analytics, Search Console
  • Ads and social: LinkedIn Ads, Reddit Ads, Reddit, Instagram
  • Project management and docs: Asana, ClickUp, Linear, Monday.com, Notion
  • Support and customer messaging: Intercom, Zendesk, Plain
  • Product and analytics: Amplitude, Mixpanel, Productboard, Typeform
  • Voice / AI: Vapi, ElevenLabs
  • Billing: Stripe
  • Data and automation: Airtable, Zapier, Gamma
New integrations are added regularly — Tools is the live catalog, so check there (use its search) if something you use isn’t listed here yet. Each app’s description and instructions (visible when you connect it) explain what it’s meant for and how Swan expects to use it — for example, Hunter is for lead/email discovery workflows separate from Swan’s own built-in enrichment, and Salesforce covers contacts, leads, accounts, opportunities, and sequences via both direct tools and raw SOQL queries.

​
Not in the catalog?

Two escape hatches cover almost anything else:
  • Connect it over MCP. If the tool exposes an MCP server, add it as a custom MCP server — its tools join the agent’s toolkit like any catalog app.
  • Call its API directly. Store the tool’s API key as a secret and ask Swan to call the API — in chat or from a trigger. See direct API access.

​
Credit costs

Reading data is generally free; most actions that write or create something in the connected app cost 1 credit, same as a HubSpot write. A handful of tools cost more or less — check the tool’s own description if you’re unsure, or see credits for how credit costs work overall.

​
Apps that can fire triggers

Some of these apps don’t just expose tools — they can also fire a Swan trigger when something happens on their side (for example, a new deal in Pipedrive, a completed transcription in Fireflies, a new row in a connected Google Sheet, or a schema change in an Airtable base). See app events for how that’s configured.

​
Common questions

Do I need to be a HubSpot user to connect an app like Attio or Pipedrive? No — these are independent of your CRM choice. You can run Swan with any combination of these connected, including none. Is a connected app shared across my whole org, or just for me? Shared across the org for almost every integration — once someone connects it, everyone’s triggers and conversations can use it. Reddit is the one app connected per individual user today. What happens to a trigger that depends on an app I later disconnect? The trigger stays configured, but firing or running it fails until the app is reconnected. Can I restrict which actions an app’s tools are allowed to take? Yes — open the app in Tools and use its capabilities list: disable any individual tool, mark it as requiring approval before the agent uses it, or restrict it to Admins only. The same controls exist for every toolkit, including custom MCP servers.