Easily Integrate Salesforce Webhooks with your application.

https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/ens-supported-events.html

Steps to receive Salesforce Webhooks

  • Sign up for your free Hooky account.
  • Create a new Webhook Source, and select Salesforce. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
  • Step 1
  • Step 2
  • Once a webhook is received from Salesforce, you'll see it under the Live Logs section of your webhook source.
  • Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Save countless hours integrating Salesforce webhooks into your application.

Integrating Salesforce Webhooks Using Javascript

Integrating Salesforce webhooks with Hooky in your Javascript based application is straight forward. Just grab the SDK, and call a function when that webhook is received.

Integrating Salesforce Webhooks Using Ruby

Integrating Salesforce webhooks with Hooky in your Ruby or Ruby on Rails application is straight forward. Just grab the SDK, and call a method when that webhook is received.

Configuring Salesforce Webhook Authentication

Here's how it works

Supported Salesforce Webhook Events

TransactionalSendEvents

Indicates that the email was sent to the email provider.

TransactionalSendEvents

Indicates that the email was not sent and includes the reason.

TransactionalSendEvents

Indicates that the email bounced and includes the reason.

EngagementEvents

Indicates that the email was opened.

EngagementEvents

Indicates that the recipient clicked a link in the email.

EngagementEvents

Indicates that the recipient clicked the unsubscribe link in the email.

TransactionalSendEvents

Indicates that the SMS message was sent to the aggregator.

TransactionalSendEvents

Indicates that the SMS message was not sent and includes the reason.

TransactionalSendEvents

Indicates the most recent transmission status between Salesforce and the mobile device. Not the final disposition. This information is provided by our delivery partners and mobile carriers but is not available in all locales. No actions to take.

TransactionalSendEvents

Indicates that the SMS message bounced and includes the reason.

TransactionalSendEvents

Indicates that the SMS message was delivered.