Dynamics 365 event management, connected to AirLST.Your CRM keeps the contact. AirLST runs the event.
For Dynamics 365 event management, AirLST connects to Microsoft Dynamics 365 through its REST API: contacts and lists come in as guests, and invitation status, RSVPs and attendance go back to the contact. There is no off-the-shelf connector; the integration is built as a project with our Integration Services, to fit your Dynamics 365 setup.
| Direction | Data | Status |
|---|---|---|
| Dynamics 365 → AirLST | Contacts, marketing list | Synced |
| AirLST → Dynamics 365 | RSVP, attendance, no-show | Synced |
| AirLST → BI | Attendance report | Scheduled |
- 9:42 AMREST 18 contacts from list “Partner Day 2026” updated · Dynamics 365
- 9:42 AMREST James Walker · RSVP “Accepted” written back · contact
Your CRM knows the customer. Your event tool knows who showed up.
Contacts, accounts or marketing lists from Dynamics 365 become guests, without an Excel export in between.
Invitation status, RSVP, attendance and no-shows go back to the contact for follow-up.
Records, fields and directions are defined for your Dynamics 365 setup, not forced into a template.
Guest and event data stay on AirLST servers in Germany, GDPR compliant.
Microsoft Dynamics event management without the spreadsheet.
As long as guest lists travel between Dynamics 365, the agency and the front door as files, there are several versions, duplicate contacts and results that never reach the CRM. With the integration, both systems know the same guest: Dynamics 365 for the relationship, AirLST for invitation, registration, check-in and reporting.
- Into AirLSTContacts, accounts or marketing lists from Dynamics 365 as guests, with groups such as VIP or partner.
- Back to Dynamics 365Invitation status, RSVP, attendance and no-shows on the contact.
- Rules per fieldWhich field goes where, which side wins on conflicts, how duplicates are handled: defined in the project.
- Technical routeThe AirLST REST API; details of your Dynamics 365 environment are clarified with our Integration Services.
Illustrative. Records and fields are defined for your Dynamics 365 environment in the project.
From the first call to the first synced event.
Because every Dynamics 365 environment is set up differently, the integration starts with your data model, not with a generic connector. Our Integration Services team plans it with your CRM team and takes it to go-live.
Which direction, which records, which system of record: contacts in, results back, or both.
Fields, groups and status values are mapped; duplicates and conflicts get clear rules.
A test event checks the sync and the log; then production. Every change stays traceable.
Effort and timeline depend on your setup:
An integration is a user. It has rights, and it has a log.
The Dynamics 365 integration accesses AirLST with its own key and only the rights it needs, and every access is recorded in the change log. Guest and event data stay with AirLST in Germany; what Dynamics 365 processes on its side is governed by your agreement with Microsoft.
- Hosted in GermanyGuest and event data on servers in Germany, including data exchanged through the integration.
- GDPR compliantData processing terms and the deletion policy are in the Trust Center; technical details on API security:
- TISAX assessedThe information security assessment standard of the automotive industry, passed by AirLST.
Example. You decide which rights the integration key gets.
CRM or event software: who does what?
Dynamics 365 event management works best when each system does its own job. Dynamics 365 manages contacts, accounts and customer journeys; AirLST runs the event: invitations, registration, guest list, seating chart, name badges and check-in, through to the attendance report. The integration connects the two, so the event result ends up on the contact.
Dynamics 365 knows who you invited. AirLST knows who came. The integration tells your CRM.
How is Dynamics 365 connected?
Through the AirLST REST API. Unlike Salesforce and HubSpot, for which AirLST has ready-made connectors, Microsoft Dynamics 365 is connected as an integration project: our Integration Services team defines with your CRM team which records and fields are exchanged, in which direction, and how conflicts and duplicates are handled. API Access is included from the Professional plan.
What else does AirLST connect to?
- Integrations overview: REST API, Salesforce and HubSpot connectors, MCP for AI assistants
- Event CRM: contacts and history across events
- Event reporting: attendance and no-shows for your BI tool
- Integration Services: design, field mapping, testing, go-live
- Event management software: many events, one standard, connected to your IT


