Verified 30 August 2026
What Day.ai integrates with
Six auto-syncing integrations, four agent connectors, one MCP server. No Salesforce integration is documented and Outlook is not supported. If your company runs Microsoft, the product's whole mechanism has no input.
The complete list
| System | Kind | What it does |
|---|---|---|
| Gmail | Auto-sync | Emails, thread summaries, contacts. The core of the product |
| Google Calendar | Auto-sync | Events and attendees |
| Slack | Auto-sync | Messages, channels, directory |
| Gong | Auto-sync | Recordings and transcripts |
| Granola | Auto-sync | Meeting notes |
| Zapier | Auto-sync | Inbound only. People and organizations |
| HubSpot | Connector | Agent reads and acts on objects and pipelines |
| Linear, Notion, Affinity | Connector | Agent tools, on request |
An integration syncs on its own. A connector only works when someone asks the agent. That decides whether data is there when you look, or only when you prompt for it.
From Day.ai's integrations guide, 15 May 2026.
What you will connect another way
- SalesforceNo sync, no connector, no documented API path. We checked their integrations guide, every changelog page back to June 2024, the product pages and the subprocessor list.
- Outlook and Microsoft 365Email and calendar ingestion is Google only. Microsoft appears nowhere, including on their subprocessor list.
- Data warehouse and billingNo Snowflake, BigQuery or customer-facing Stripe integration documented.
- Outbound ZapierTheir words: "There are no outbound triggers from Day AI to Zapier at this time." Zapier's directory confirms it: one action, zero triggers, and that action cannot create an opportunity.
Worth reconciling before you buy. Day.ai says it "can sit alongside what you already have" and layers onto "whatever system of record the client already runs." On the evidence, that resolves to HubSpot and Affinity. For a Salesforce shop, sitting alongside means running two systems that do not talk.
The part most people miss
There is no documented public REST API. The programmatic surface is an MCP server at day.ai/api/mcp, OAuth 2.0, 20+ tools, and it requires a paid agent tier. Supported clients are Claude on web, mobile and desktop, Cursor, and Claude Code. ChatGPT is not named.
Day.ai is also an MCP client, which is how the HubSpot, Linear, Notion and Affinity connectors work. If you are comparing CRMs on integration breadth, this is the axis that will matter in two years and nobody is comparing on it yet.
Day.ai integration questions
Does Day.ai have a public API?
No REST API is documented. The programmatic surface is the MCP server with OAuth 2.0 and a TypeScript SDK, and it requires a paid agent tier.
How does the Zoom integration work?
It is a meeting bot, not a data integration. It joins calls for events with a Zoom link in your Google Calendar, so it is effectively a calendar feature. Zoom is absent from Day.ai's own integrations guide despite being prominent on the product pages.
Can Day.ai sit alongside our existing CRM?
If that CRM is HubSpot or Affinity, yes, through an agent connector. If it is Salesforce or anything else, there is no documented path.
Where we come in
We build the connections, and own them after
Six things plug straight in and everything else takes a middle step. We build that middle step, test it against real records, and stay accountable for it when something changes at either end.
- Your stack connected, tested with your own data rather than samples
- The direction of every connection chosen deliberately
- The awkward cases handled before somebody finds them
- One person to call when a vendor changes something
Free, no call required
The Day.ai setup guide
Not ready to talk to anyone? Take this instead. One email, nothing else unless you ask for it.