Connect Salesforce to Elido

Coming Q3 2026. The Elido native Salesforce package is currently in Salesforce ISV review. It is not yet available on AppExchange. Sign up for early access at Dashboard → Integrations → Salesforce → Notify me.

The sections below describe what the native package will support, plus a working webhook-based workaround you can use today.

What the native package will include#

• OAuth 2.0 Connected App — no manual token management.
• Auto-creation of Salesforce Leads and Opportunities on Elido conversion events.
• Custom field mapping: utm_source, utm_campaign, click_id → Salesforce fields of your choice.
• Bidirectional sync: Salesforce Opportunity stage changes reflected in Elido campaign status.

Scopes required: api, refresh_token, offline_access.

Today: use generic webhooks as a bridge#

While the native package is in review, you can forward Elido events to Salesforce using one of these approaches:

Option A — Salesforce Flow + Elido Webhook#

1. In Salesforce, create a Flow with a Platform Event trigger.
2. In Elido, go to Dashboard → Webhooks → Add → Generic. Paste your Salesforce Webhook listener URL.
3. Enable the conversion.recorded event. Elido sends an HMAC-signed POST; verify the signature in your Flow before processing.

Option B — Zapier or Make.com as middleware#

Use the Elido Zapier app or Make.com connector as a bridge. Both can receive an Elido trigger and create a Salesforce record without writing code.

Option C — Direct API call from your backend#

If you control the conversion event server-side, call both the Elido Conversions API and the Salesforce REST API in the same request handler. No middleware needed.

Prepare for the native package launch#

When the package launches:

1. Install it from AppExchange.
2. Create a Connected App in Salesforce (Setup → App Manager → New Connected App). Set the callback URL to what Elido provides at launch.
3. Add the Connected App's client ID and secret in Elido.
4. Authorize via OAuth. Map fields in the Elido UI.

We'll email everyone on the notify list with exact steps the day the package goes live.

Troubleshooting (webhook bridge)#

Signature verification failing in Salesforce — Use the raw request body (before any JSON parsing) as the HMAC input. The signature header is X-Elido-Signature: sha256=<hex>. See the Webhooks guide for the full verification recipe.

Events not arriving in Salesforce — Check Dashboard → Webhooks → Delivery log. A 4xx from Salesforce's side means the endpoint is rejecting the payload (auth mismatch, wrong URL). A 5xx means Salesforce errored on its side.

Zapier bridge hitting Zapier's task limit — High-traffic links generate many click events. Use threshold.exceeded as the trigger instead of link.clicked to reduce task consumption.