← All integrations Implementation guide · Microsoft Dynamics 365

Eventtia and Dynamics 365, step by step.

This 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.

Talk to us See the steps
Connection
Webhooks + APIContacts, leads and the tables you choose.
Tools
n8n, Zapier or your backendThree ways to build it.
Built by
Your team or oursOur build is a scoped, quoted service.
Timeline
1 to 4 weeksA simple webhook setup takes about one week.
Proposed mapping

What can move from Eventtia to Dynamics 365.

A proposed mapping to validate for your project.

  1. New registrationattendee_created
    Contact or Lead, created or updated
  2. Registration changeattendee_updated
    Contact or Lead fields
  3. Event created or updatedevent_createdevent_updated
    To define with your team
  4. Paymentpayment_created
    To define with your team
Three ways to build it

With n8n, Zapier, or directly.

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-code

With Zapier

A 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 request

Directly

Your 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 control
Steps

From webhook to Dynamics 365 record.

  1. Step 01

    Create two webhooks

    In 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.

  2. Step 02

    Filter your events

    Account webhooks cover every event in the account. Keep only the events you want, and start with a test event.

  3. Step 03

    Connect Dynamics 365

    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.

  4. Step 04

    Test, then go live

    Run a few test registrations and check the records in Dynamics 365. Then switch on your real events.

FAQ

Dynamics 365 integration questions.

Is there an Eventtia app in Microsoft AppSource?

No. Eventtia connects to Dynamics 365 through webhooks and our API, directly, through n8n or through Zapier.

How long does it take?

Typically 1 to 4 weeks. A simple webhook setup can be live in one week. A larger scope can take longer, and we agree the timeline when we scope the project.

Does it work with Dynamics 365 on-premises?

The Zapier app supports Dynamics 365 online only. For an on-premises environment, the direct route from your backend is the one to scope.

Planning a Dynamics 365 integration?

Tell us what you need in Dynamics 365. We will tell you what the integration involves and who should build it.

Talk to us All integrations