Integrations

Connect Eventtia to the systems you already run.

Payment providers and single sign-on are built into the platform. CRMs, marketing platforms and internal tools connect through webhooks and our REST API, mapped to your own fields. AI agents connect through our MCP server.

Talk to us See the list

Connect

PaymentsBuilt in

CRM & workflowsWebhooks + API

AI assistantsMCP server

Your systems. The right connection for each.

Three ways to connect

Built in, built on the API, or through agents.

Built into the platform

Payment providers, single sign-on and Google Analytics. Each one is configured for your account.

Built on webhooks and the API

CRMs and marketing platforms. Your team or ours maps Eventtia data to your objects and fields, as a scoped project. Typically 1 to 4 weeks.

Through AI agents

Our MCP server lets assistants such as Claude and ChatGPT read and act on your events, with the permissions of the connected user. Eventtia is an official plugin in ChatGPT and is listed in Claude's connectors library.

Beyond one-way sync

Deep integrations, in both directions.

Most event platforms push a registration to the CRM and stop there. Our clients run integrations that go both ways, and cover the full journey, from login to invoice.

The CRM ID, stored

Eventtia stores your CRM's record ID on the attendee. Every update carries it, so your CRM matches the record directly, with no duplicates.

Attendance, not just registration

Check-ins, cancellations and status changes update the same CRM record, so you know who came.

Your systems write back

Through our REST API, your CRM or finance tool can update attendees, and mark a registration as paid when the bank transfer arrives.

Login with your member account

Attendees register with your brand's own login. The form is pre-filled, each member registers once, and the CRM ID is known from the start.

One webhook for all events

An account webhook covers every event of a brand or an entity. No setup per event.

Stable field keys

Each form field keeps the same internal key across events, so your CRM maps the fields once.

Rich payloads

Webhooks include the event location (city, region, country) and event custom fields, such as a campaign ID, so your CRM needs no extra API calls.

Data lineage

Each registration shows where it came from: your own system or the Eventtia page.

Scoped access inside a group

In a group account, webhooks and API access can be limited to one entity's events, with a dedicated API user and a staging environment for tests.

Our own n8n nodes, covering the create and update actions of our API, are coming soon.

Good practice

Five rules for a clean CRM sync.

What we learned from our client projects. These rules keep data clean on both sides, whatever CRM you run.

Separate marketing opt-in

Collect marketing consent as its own field, apart from the terms and conditions.

Keep consent text plain

Put plain text in form fields and legal links in the form footer. Some CRMs reject HTML in the data they receive.

Store the CRM ID once

Save the CRM record ID on the first sync, then use it for every update.

Let finance write back

Let your CRM or accounting tool send payments back, so finance and the event team see the same status.

Test in staging

Test against a sandbox or staging environment first. Connect production only to production.

Integrations and implementation guides.

CRM and marketing

10 systems

Salesforce

CRM

Registrations and consent, in your Salesforce org.

Webhooks and our API, mapped to your objects and fields.

Webhooks + APIHow it works

HubSpot

CRM

A guide to send registrations to HubSpot contacts.

A step-by-step guide to connect Eventtia to HubSpot: directly, through n8n or through Zapier.

How-to guideRead the guide

Microsoft Dynamics 365

CRM

A guide to send registrations to Dynamics 365 contacts or leads.

A step-by-step guide to connect Eventtia to Dynamics 365: directly, through n8n or through Zapier.

How-to guideRead the guide

Tribe CRM

CRM

Registrations to invoices, payments back.

Registrations create contacts and invoices in Tribe CRM through n8n. When a payment arrives in Tribe, the registration is marked as paid in Eventtia.

Custom buildRead the guide

Selligent

Marketing

Attendee data for marketing campaigns.

Send attendee and consent data to Selligent for marketing campaigns through a custom webhook integration.

Custom buildRead the guide

LINE

Messaging

Sessions and seats in a LINE app.

Show event sessions and available seats in your LINE app through a custom webhook integration.

Custom build

n8n

Automation

Low-code workflows on our webhooks.

n8n workflows receive Eventtia webhooks and call our API to reach your other tools.

Webhooks + API

Zapier

Automation

Automate workflows with Eventtia Zaps.

Connect Eventtia with your other tools using available Zaps. Contact our team to get set up.

ZapsAsk about setup

Accounting

Registrations and payments to invoicing.

Invoices created and updated in Pennylane from Eventtia registrations, through n8n workflows.

Built on n8n

Messaging

Welcome attendees on WhatsApp.

Send attendees a welcome message on WhatsApp.

Welcome message

Payments

7 systems

Stripe

Payments

Card payments at registration.

Connect your Stripe account and take payments for tickets and paid registrations.

Built inHow it works

Adyen

Payments

Enterprise payments at registration.

Take payments for tickets and registrations through your Adyen account.

Built inHow it works

PayPal

Payments

Pay with PayPal.

Let attendees pay for tickets and registrations with PayPal.

Built inHow it works

Mercado Pago

Payments

Local payments across Latin America.

Accept the payment methods your attendees use in Latin American markets.

Built inHow it works

Payments

Online payments in Latin America.

Take ticket and registration payments through your PayU account.

Built inHow it works

Payments

Online payments in Colombia.

Take ticket and registration payments through your Wompi account.

Built inHow it works

Worldline

Payments

Payments for European events.

Take ticket and registration payments through your Worldline account.

Built inHow it works

Identity and analytics

2 systems

Single sign-on

Identity

Your team signs in with your identity provider.

SAML 2.0 and OpenID Connect, for example with Okta.

Built in

Google Analytics 4

Analytics

Registration pages in your GA4 property.

Add your GA4 tag in the event settings to measure your registration pages.

Built in

AI assistants, through our MCP server

4 systems

Claude

AI assistant

Run your events from Claude.

Eventtia is listed in Claude's connectors library. Connect it, sign in, and Claude reads and acts on your events with your permissions.

MCP serverAbout the MCP server

ChatGPT

AI assistant

The official Eventtia plugin for ChatGPT.

Install Eventtia from ChatGPT's plugin directory, sign in, and ChatGPT reads and acts on your events with your permissions.

ChatGPT pluginHow to install it

Microsoft Copilot

AI assistant

Run your events from Microsoft Copilot.

Connect our MCP server to Copilot to read and act on your events, with your permissions.

MCP serverAbout the MCP server

Cursor

AI assistant

Build on your events from Cursor.

Connect our MCP server to Cursor to read and act on your events while you build.

MCP serverAbout the MCP server

Not on the list?

Tell us what you run.

Tell us which system you use. We will look at its API, its authentication and the data you need, and tell you what an integration involves.

FAQ

Integration questions.

Which CRMs does Eventtia integrate with?

Eventtia integrates with Salesforce, HubSpot and Microsoft Dynamics 365, and with other CRMs and marketing platforms such as Selligent and Tribe CRM, through webhooks and the Eventtia REST API. Payment providers and single sign-on are built into the platform.

Are Eventtia CRM integrations two-way?

Yes. Eventtia sends registrations, check-ins and status changes to the CRM through webhooks, and can store the CRM record ID on each attendee, so updates never create duplicates. The CRM or finance tool can write back through the Eventtia REST API, for example to update attendees or mark a registration as paid.

How does Eventtia send attendance and check-ins to a CRM?

When an attendee is checked in, Eventtia sends an attendee_updated webhook. The integration updates the record in the CRM, for example the Campaign Member status in Salesforce.

Can Eventtia store our CRM record ID?

Yes. Eventtia stores the CRM record ID on the attendee, in a private field visible to admins only. Every later webhook carries it, so the CRM matches the record directly, with no duplicates.

Can a CRM or finance tool mark an Eventtia registration as paid?

Yes, through the Eventtia REST API. When a payment arrives in your CRM or finance tool, it can mark the registration as paid in Eventtia, and reverse it if needed.

Does Eventtia have one-click CRM connectors?

Payment providers and single sign-on are built into Eventtia and configured per account. CRMs connect through webhooks and the Eventtia REST API, mapped to your own objects and fields, so the integration follows your CRM model, custom fields included.

Which Eventtia events trigger webhooks?

The documented Eventtia triggers cover new and updated attendees, events, invoices, workshops and business meetings, plus new payments. The full list is in the API documentation.

Can one Eventtia webhook cover all our events?

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.

Who builds a CRM integration with Eventtia, and how long does it take?

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.

Can AI agents use Eventtia?

Yes, through the Eventtia MCP server. Eventtia is listed in Claude's connectors library and as an official plugin in ChatGPT's plugin directory.

Planning an integration?

Tell us which systems you run. We will tell you what connecting them to Eventtia involves.

Talk to us Read about the API