A Mailchimp sync with conditions
Only contacts who've met an engagement threshold, only certain plans, only after a conversation closes. Built against both APIs for conditions a tag or segment can't express.
Marketing wants Intercom contacts in Mailchimp, the support lead wants new conversations in Slack, and someone else wants Fin to stop handing off every billing question. Those requests don't belong in the same corner of Intercom. An App Store app helps your team see things, a Data connector lets Fin look things up mid-conversation, and the API covers whatever neither reaches.
If a person needs to see it, look for an app. If Fin needs to know it before replying, it's a connector, and a slow or bloated endpoint behind it is what makes Fin hand off.
There's no deep sync between an Intercom inbox and Zendesk, and that's no oversight: the two compete for much of the same work. Fin can now run inside Zendesk, resolving tickets with Zendesk kept as the system of record, but that's Fin answering Zendesk tickets, not the two inboxes sharing account and conversation history.
That leaves two situations. Either the business runs both on purpose, chat and sales messaging in Intercom and ticketing in Zendesk, and needs a custom link so each side sees what the other knows. Or it's moving from one to the other and needs data carried across once, not an ongoing integration. Our Intercom vs Zendesk page covers the choice itself.
Only contacts who've met an engagement threshold, only certain plans, only after a conversation closes. Built against both APIs for conditions a tag or segment can't express.
Account context and conversation history kept consistent in both, for teams who've chosen to run the two side by side.
A small, fast lookup in your own system that answers inside Intercom's time limit and returns only the fields Fin should see.
Contacts, conversations and attributes carried across once, with a check that counts match on both sides.
Yes. The Slack app from the App Store posts new conversations and replies into a Slack channel, and most teams set it up without custom work.
Not through a deep native sync between the two inboxes. Fin can work inside Zendesk as an AI agent, but a business using Intercom for chat and Zendesk for tickets still needs a custom connection, or a one-time migration if it's moving off one of them.
Yes, through an App Store app that syncs contact data, so Intercom audiences can be used for Mailchimp campaigns without exporting a CSV.
A long list across messaging, marketing, CRM, billing and analytics tools, and it changes often. Coverage is strongest for common SaaS stacks. Anything specific to how your business runs usually means a Data connector or the API.
It's an API call you set up so Fin can fetch or send customer-specific data during a conversation, such as an order status from Shopify or an invoice from Stripe. Templates cover common apps, and you can build one from scratch for your own system.