Integrations
Webhooks
Send ECARD events to your own systems (CRM, automations).
Webhooks let ECARD call a URL of your choice whenever an event occurs (for example, the creation of a contact). This lets you automate your workflows: each new event in ECARD can trigger an action in your own tools, in real time.
Configure a webhook
- Open Integrations → Webhooks.
- Enter the destination URL (the endpoint that will receive the calls).
- Choose the events to send (e.g. new contact).
- Save. Deliveries are logged to make tracking and diagnosis easier.
Your endpoint should respond quickly (2xx status). A screenshot of the delivery log would help illustrate the tracking.
Example
You want a newly scanned contact to automatically create a lead in your CRM:
- Create an endpoint on the CRM side (or through a tool like Make/Zapier) that receives the data.
- In ECARD, add a webhook to that URL on the "new contact" event.
- Test with a real contact: check that it's received on the CRM side and check the delivery log on the ECARD side.
Use cases
- Automatically create a lead in your CRM for every new contact.
- Notify an internal channel (Slack, Teams) through an intermediary service.
- Trigger an automation scenario (n8n, Make, Zapier, and so on).
Troubleshooting
- My endpoint receives nothing. Check the URL and that the event is actually selected; look at the delivery log to see the attempts and response codes.
- The calls fail. Make sure your endpoint is public, reachable over HTTPS, and responds with a 2xx code; a slow endpoint or one returning an error can cause the delivery to fail.
- Duplicates. Make your processing idempotent on the receiving side in case the same event can be re-sent.
Good to know
- Treat received data as sensitive and secure your endpoint (HTTPS, verification secret if available).
- The CRM/API integrations module is available depending on your plan.
- See also Integrations and the Glossary.