Event management software integrations.Connect your CRM, IT stack and AI assistants.
AirLST integrations connect your guest list with the rest of your company: contacts in from Salesforce or HubSpot, RSVPs and attendance back out, registrations from your own website, data for BI and finance. And through MCP, AI assistants talk directly to your event data.
Event data belongs in your systems. Not in a spreadsheet export.
From your CRM, campaign or website straight into the guest list, with no Excel file in between.
RSVP, attendance, no-shows and revenue back to the contact, your BI tool and finance.
Salesforce and HubSpot ready to go; SAP, Dynamics and marketing automation as a project.
MCP: your assistant works in AirLST, within your rights, with your data hosted in Germany.
Salesforce and HubSpot integration: contact in, result back.
Your CRM stays the system of record for contacts, AirLST for the event. The connector creates contacts, lists or campaign members as guests; invitation, RSVP, attendance and no-show go back to the contact as a status or activity. Sales and marketing keep working where they already are.
- SalesforceContacts and campaign members as guests; event status on the contact; connector available. Salesforce event management
- HubSpotContacts and lists as guests; RSVP and attendance as properties for workflows and sequences; trade show leads from lead retrieval (Exhibitor Edition) go to HubSpot as well. HubSpot event management
- SAP, Microsoft Dynamics, marketing automationConnected through the REST API, delivered as an integration project: SAP integration, Dynamics 365 integration.
- Fields and rulesWhich objects, which fields, which direction: defined with our Integration Services.
The event management API: create guests, read status, from any system.
The REST API is the way in for everything that has no ready-made connector: registration on your own website, the intranet, the ticketing system, the BI tool. Create and update guests, read status and attendance, pull reporting data; all on the same record your team sees in the back office.
"last_name": "Hayes",
"email": "laura.hayes@belventi.example",
"company": "Belventi Group",
"group": "Workshop A",
"status": "requested"
| code | VLWR0O47 |
| status | Requested |
| group | Workshop A |
| registration_url | https://…/r/VLWR0O47 |
Field names and endpoints are illustrative; the documentation is binding:
Contacts in, registrations in, results out: RSVP, attendance, no-shows, revenue.
API Access (REST) is included in the Suite and the event app from the Professional plan.
SDKs, webhooks, OAuth scopes and documentation:
Connect AI assistants: the AirLST MCP server.
Next to the REST API for systems, AirLST has an MCP server for AI assistants such as Claude, ChatGPT or GitHub Copilot, and, as a custom setup, Microsoft Copilot through Copilot Studio. The assistant uses it to work in AirLST in the conversation, today in Airstage for landing pages and registration forms, with the signed-in user’s permissions and fully logged. Connection, tools and security are on the AirLST MCP server page.
Connect AI agents, Microsoft Copilot and enterprise systems.
There are three ways into AirLST: connectors for your CRM, the REST API for every other system, and the MCP server for AI assistants. Standard means it works without a project; everything else is set up as a custom integration by our Integration Services team or your IT department.
One data flow, from Salesforce to follow-up
Here’s how a customer event runs when Salesforce is the system of record. The first four steps are standard; AI-assisted follow-up is set up per customer.
| Step | What happens, and how | Label |
|---|---|---|
| 1 · Salesforce contacts | The Salesforce connector syncs the campaign and its contacts; campaign members become guests in AirLST. | Standard |
| 2 · AirLST invitation | The event team sends invitations from AirLST, using guest groups from the campaign. | Standard |
| 3 · Registration and attendance | Guests register on the event site and check in at the door, all on the same guest record. | Standard |
| 4 · Status back to the CRM | Registrations, declines, attendance and no-shows flow back to Salesforce as campaign member status. | Standard |
| 5 · AI-assisted follow-up | An assistant, such as a Copilot Studio agent, gets attendance data through a REST API integration you set up and drafts follow-ups for sales. | Custom integration |
Which system connects how
A ready-made connector is only standard where one exists. For every other system, the REST API is the foundation of an integration project.
| System | Route | Label |
|---|---|---|
| Salesforce, HubSpot | Connector: contacts and campaigns or lists in, status and attendance back. | Standard |
| Your website, intranet, ticketing | REST API: create guests, read status and attendance, pull reports; included from Professional. | Standard |
| Claude, ChatGPT, GitHub Copilot, Cursor | AirLST MCP server: the Airstage tools, with the user’s permissions. MCP server | Standard |
| Microsoft Copilot (Copilot Studio) | Add the AirLST MCP server as a tool to an agent, then publish the agent to Teams and Microsoft 365 Copilot. How it works | Custom integration |
| Power Automate, Power Apps | Custom connector: per Microsoft, a wrapper around a REST API described in OpenAPI, also usable in Copilot Studio. For AirLST, built on the REST API as a project. | Custom integration |
| Power BI, Microsoft 365 | Reports and attendance data into dashboards and workflows through the REST API. | Custom integration |
| SAP, Microsoft Dynamics, marketing automation | Connected through the REST API, delivered as an integration project. | Custom integration |
MCP gives an assistant tools to use in a conversation; the REST API connects systems. An agent can use both once both are set up.
Every access runs with permissions and is logged, whether it’s a connector, API access or an assistant.
Use cases and real-world examples are on AI in events.
| Key | Last call | Status |
|---|---|---|
| Website · registration | 30 s ago | Active |
| Intranet · employee events | yesterday | Active |
| BI · finance | 6:00 AM | Active |
| Agency · test | – | Inactive |
Build your own application on top of the API.
Building an employee portal, a dealer cockpit or an internal agent? The REST API delivers guests, status, attendance and reporting data; your application brings the interface. Rights per key, a log entry per call, data hosted in Germany.
- REST APICreate and update guests, read status and attendance, pull reporting data; confirmed and in production use.
- Keys with rightsOne key per system with the roles of the guest list; revocable and logged.
- SDK, webhooks, OAuth
- With supportDesign, field mapping, testing and go-live with our Integration Services.
An integration is a user. It has rights, and it has a log.
Whether it’s a connector, an API key or an MCP connection, every access runs through the roles and rights of the guest list and is recorded in the change log. The data stays with AirLST in Germany; what a connected system or a language model processes on its own side is governed by your contract with that provider.
- Hosted in GermanyGuest and event data on servers in Germany, including when it’s exchanged through integrations.
- GDPR compliantData processing terms and the deletion policy are in the Trust Center; technical details on API security:
- TISAX assessedAirLST is assessed under TISAX, the information security assessment standard of the automotive industry.
Example. You assign rights per connection; the AI assistant inherits the role of the user who connected it.
The integration is the guest record, seen from the outside.
Your CRM, website, BI tool and AI assistant read and write the same guest as your team, the check-in app and reporting. That’s why there’s no export going stale and no import creating duplicates.
Event CRMContacts across all events
Guest List ManagementOne source of truth for the whole team
Event Website BuilderLanding pages without code
Invitation EmailsDigital invitations in your brand design
Event RegistrationForms, RSVPs, plus-ones
Event TicketingTamper-proof QR tickets
Seating ChartsTables and seats from the guest list
Workflow AutomationAutomate workflows
Event AppAgenda and ticket on the phone
Event Check-inScan instead of search at the door
Access ManagementCheck-in, badges, gates: the whole entrance
Name BadgesPrinted on arrival
Lead RetrievalScan leads at the booth
Event SurveysPost-event feedback
Reporting & AnalyticsAttendance, no-shows, reporting- You are here
API & IntegrationsConnect CRM and IT 
AI integration (MCP)Connect Claude, ChatGPT or Copilot
Hosting, encryption and data processing are described in the Trust Center; our Integration Services handle the design and implementation of integrations. How many events run on one standard, connected to your IT, is covered on the event management software page.
What is an event API?
An event API is an interface that lets other systems read and write event data: create CRM contacts as guests, hand over registrations from your own website, and push RSVPs, attendance and no-shows back to your CRM, marketing automation or BI tool. In AirLST that is a REST API, complemented by ready-made connectors for Salesforce and HubSpot; integrations with SAP, Microsoft Dynamics and marketing automation platforms are delivered as a project.
The point of event management software integrations isn’t moving data around; it’s ending the export. As long as guest lists travel as Excel files between CRM, agency and the front door, there are several versions, duplicate contacts and results that never make it back to the CRM. With the API, your CRM stays in charge of contacts, AirLST stays in charge of the event, and both know the same guest. On top of that comes MCP: through the Model Context Protocol, AI assistants talk to AirLST, for questions and prepared actions within the user’s rights.
The integration isn’t a data export. It’s the guest record, seen from the outside.
RESTAPI for guests, status, attendance, reporting; from Professional
2Ready-made connectors: Salesforce, HubSpot; SAP and Dynamics as a projectMCPModel Context Protocol for Claude, ChatGPT, your own agents and Microsoft Copilot (Copilot Studio)How does an integration with AirLST work?
- Define the goal. Which direction, which data, which system of record: contacts in, registrations in, results out.
- Choose the route. A connector for Salesforce or HubSpot; the REST API for your website, intranet, BI, SAP, Dynamics and marketing automation; MCP for AI assistants.
- Create a key. One key per system with the roles of the guest list; only the rights the purpose needs.
- Map the fields. Which field goes where, which group gets which status; handle conflicts and duplicates, with our Integration Services.
- Test and go live. Test event, check the sync, read the log, then production; every change stays traceable.
- Run it. Connectors run automatically; API calls and MCP access are logged; keys can be revoked at any time.
How is MCP different from the API?
The REST API connects AirLST with other systems and is programmed by developers: one call, one response, one defined field. MCP connects AirLST with AI assistants and is used by people in conversation: the AirLST MCP server describes tools such as “add a page” or “build the form from the guest fields”, and the assistant picks them based on the request. Both access the same data, with the same rights.
The API is for systems, MCP is for conversations. Both see the same guest, and both can only do what the user can.
For an event team, that means a landing page with a registration form takes shape in a conversation, while you watch live and approve. Airstage is connected today, other modules follow; the tools and the OAuth sign-in are described on the AirLST MCP server page.
What does the integration work with?
With the event CRM as the contact base across events, the guest list as the record behind every endpoint, event registration for sign-ups from outside, event reporting for BI, workflow automation for if-then rules, and special configurations with integrations.
- Integration Services: design, field mapping, testing, go-live
- Trust Center: hosting, encryption, data processing
- Event management software: many events, one standard, connected to your IT
- Automotive events: TISAX-assessed data handling for integrations in the automotive industry