Skip to main content
EzyConn

Integrations · Salesforce

There is no nativeSalesforce integration.

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

0
native Salesforce connectorsNo CRM 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 Salesforce without a Salesforce connector.

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

  • 01Create a LeadA completed qualification becomes a Lead with its answers mapped to fields.via Zapier
  • 02Log an ActivityThe transcript lands on the record rather than in a separate inbox.via Zapier
  • 03Open an OpportunityBooking events can create or update an Opportunity.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 CRM 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 Salesforce as the action

    Zapier handles the Salesforce 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 Salesforce 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.