Opening website
Loading Evara...
A polished experience is almost ready.
Powered by Evara
Connect Make once, then use it across the pages, workflows, analytics, and customer actions Evara already manages.
Create a secure webhook or connector path for the Evara events your scenarios should receive.
Use form submissions, orders, bookings, contact updates, and campaign events to start Make scenarios.
Pass clean customer, page, source, and conversion data into downstream workflows.
Extend Evara workflows into the rest of your stack without losing the source context.
Use Make inside Evara without treating it as a disconnected embed. Connect it to the pages, forms, CRM records, payments, workflows, analytics, and conversion events that need it.
Make stays connected to the Evara pages, customer records, conversion events, and workflows that need it. No brittle connector chain required.
| Data type | Direction | Sync frequency | Notes |
|---|---|---|---|
| Outbound webhooks | Evara → Make | Real-time on event | Signed with X-Evara-Signature: sha256= header |
| Inbound API calls | Make → Evara | On scenario run | Read + update contacts, pages, orders via public API |
| Event schema versioning | Evara → Make | Per release | Stable v1 schema; deprecations flagged 30 days ahead |
| Retry + delivery receipt | Evara → Make | On webhook failure | 5x exponential backoff; failed deliveries surfaced as notification |
| Per-event scenario filter | Evara → Make | On configuration | Filter triggers by tag, segment, or custom condition before send |
