Skip to main content
EzyConn

Integrations · Intercom

There is no nativeIntercom integration.

We would rather say that here than let you find out during a trial. Moving conversations between tools is a real need, and there is a real way to do it today — it runs through automation rather than through a Intercom-shaped connector we have not built.

0
native Intercom connectorsNo messaging platform connector is built, and none is scheduled.
17
events you can act onDelivered to Zapier and to signed webhooks.
6
channels that are nativeSlack · WhatsApp · Microsoft Teams · Zapier · Zoom · SMS

What works today

Reaching Intercom without a Intercom connector.

EzyConn publishes 17 event types. Zapier receives them, and Zapier already speaks Intercom. That is one hop more than a native integration and it is available now.

  • 01Create a conversationPush an escalated EzyConn conversation into Intercom.via Zapier
  • 02Sync contact detailsWhatever the conversation captured maps onto the contact.via Zapier
  • 03Notify on bookingBooking events can post into the inbox your team watches.via Zapier

The event contract

What actually leaves the platform.

Generated from the delivery list in the API. An event that is not on it is dropped, so this is the promise rather than a description of one.

  • agent.assigned
  • agent.unassigned
  • booking.cancelled
  • booking.completed
  • booking.confirmed
  • booking.created
  • booking.no_show
  • booking.reminder_due
  • booking.rescheduled
  • contact.created
  • conversation.closed
  • conversation.created
  • conversation.updated
  • message.received
  • message.sent
  • order.created
  • reservation.created

7 of them cover the booking lifecycle, which is usually the part a messaging platform actually wants.

Setting it up

Three steps, no engineering.

  1. Step 01

    Create a Zap

    Pick EzyConn as the trigger and choose one of the 17 events.
  2. Step 02

    Choose Intercom as the action

    Zapier handles the Intercom authentication and field mapping.
  3. Step 03

    Test it with a real conversation

    Every delivery is logged, so a failure is visible rather than silent.

Prefer to skip Zapier? The same events are available as signed webhooks — see the developer docs.

We publish what we have not built.

If a native Intercom connector is the thing that decides it for you, tell us — that is useful, and it is a better outcome than discovering the gap after you have migrated.