Connect Salesforce to Elido

Elido has no Salesforce connector today. It is planned, with no date set. The sections below describe what it is meant to support, plus workarounds you can use now.

What the connector is planned to include

• OAuth 2.0 Connected App, with no manual token management.
• Automatic creation of Salesforce Leads and Opportunities from Elido conversion events.
• Custom field mapping, plus Salesforce Opportunity stage changes reflected in Elido campaign status.

Today: bridge with webhooks or the API

Until a connector exists, use 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 link events you need, such as link.created or link.updated. Elido sends an HMAC-signed POST. Verify the signature in your Flow before processing.

Option B: Zapier as middleware

Use the Elido Zapier app as a bridge. It can receive an Elido trigger and create a Salesforce record without writing code.

Option C: poll the analytics API

Run a scheduled job that reads click data from the Elido analytics API and writes records through the Salesforce REST API. Clicks are not pushed one by one, so this is a poll. Salesforce link tracking walks through it.

When a connector ships

A webhook bridge you build now will keep working. Nothing needs preparing today. Watch the changelog for the launch.

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: v1=<hex>, computed over {timestamp}.{raw_body} with the X-Webhook-Timestamp header. See the Webhooks guide for the full recipe.

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