With n8n
An n8n workflow starts on an Eventtia webhook, can read more data from our API, and writes to Dynamics 365 through the Dataverse Web API with n8n's HTTP Request node. The built-in Dynamics node covers accounts only.
Low-codeThis guide shows how to send Eventtia registrations to Microsoft Dynamics 365 with our webhooks and API, as the contacts or leads you choose. Build it with n8n, with Zapier, or directly from your backend. Our team can build it with you as a scoped project.
attendee_createdContact or Leadattendee_updatedContact or Lead fieldsExample mapping. Through n8n, Zapier or directly.
A proposed mapping to validate for your project.
attendee_createdattendee_updatedevent_createdevent_updatedpayment_createdRegistration is only half the story. Your CRM also needs to know who came. Each change in Eventtia sends an attendee_updated webhook, so the record in Dynamics 365 follows the attendee from registration to check-in.
A new registration creates or updates a contact or lead.
When the attendee is scanned at the entrance, Dynamics 365 shows it: a field on the contact or lead, or the check-in record if you use the event features of Dynamics 365 Customer Insights.
A cancellation, a confirmation, a rejection or a new attendee type updates the same record.
On the first sync, Dynamics 365 returns the ID of the record it created. Eventtia stores this ID on the attendee, in a private field that only admins see. Every later update carries the ID, so Dynamics 365 finds the record directly. No search, no duplicates. Your systems can also write back through our REST API: update an attendee, or mark a registration as paid when your finance tool receives the payment.
Dynamics 365 creates the record and returns its ID.
The ID is saved on the attendee, visible to admins only.
Check-ins, cancellations and status changes carry the ID back to Dynamics 365.
An n8n workflow starts on an Eventtia webhook, can read more data from our API, and writes to Dynamics 365 through the Dataverse Web API with n8n's HTTP Request node. The built-in Dynamics node covers accounts only.
Low-codeA Zap sends Eventtia data to Dynamics 365 with Zapier's Microsoft Dynamics 365 CRM app, a premium app for Dynamics 365 online. Our Zapier app is available on request: our team sets you up.
No code, on requestYour backend receives the webhook and calls the Dataverse Web API. Use this when you need full control, high volumes or an on-premises environment.
Full controlIn Eventtia, create one account webhook for attendee_created and one for attendee_updated, with an authenticated API call, both pointing to your workflow or backend.
Account webhooks cover every event in the account. Keep only the events you want, and start with a test event.
For Dynamics 365 online, register an app in Microsoft Entra ID, add it as an application user in your environment, and give it a security role with access to contacts or leads. On-premises versions need their own authentication and network setup, defined when we scope the project. Then map fields and decide the matching key with your team.
Run a few test registrations and check the records in Dynamics 365. Then switch on your real events.
Eventtia sends a webhook for each new registration and each change, including check-in, cancellation and status changes. The integration creates or updates the contact or lead in Dynamics 365, and records attendance in a field, or in the check-in record if you use the event features of Dynamics 365 Customer Insights.
Yes. Eventtia sends event data to Dynamics 365 through webhooks, and stores the Dynamics 365 record ID on each attendee, so every update matches the right record. Dynamics 365 or your other systems can write back to Eventtia through the REST API, for example to update an attendee or mark a registration as paid.
Yes. Eventtia stores the Dynamics 365 record ID on the attendee, in a private field visible to admins only. Every later webhook carries it, so Dynamics 365 matches the record directly, with no search and no duplicates.
Through Eventtia webhooks and the Eventtia REST API, mapped to your own Dynamics 365 tables and columns. You can build it directly, with n8n, or with Zapier. Eventtia does not use a generic one-click connector, so the integration follows your Dynamics 365 model.
Yes. An Eventtia account webhook covers every event in the account, with no setup per event. In a group account, it can be limited to one entity's events.
Your developers, with the Eventtia API and webhooks, or the Eventtia team, as a scoped and quoted project. It typically takes 1 to 4 weeks. A simple webhook setup can be live in one week.
Eventtia connects to Dynamics 365 through webhooks and the Eventtia API, directly, with n8n or with Zapier. It is not an AppSource app, so the mapping follows your Dynamics 365 setup.
The direct route, from your backend, can work with an on-premises environment and is scoped in the project. The Zapier app supports Dynamics 365 online only.
Tell us what you need in Dynamics 365. We will tell you what the integration involves and who should build it.