Integrations

Your event, in the systems you already use

AttendBeacon keeps the event's record. Your CRM, your team's channels and your automations are kept in step with it, without exporting and importing by hand.

One record, kept in step everywhere

Every registration, check-in and lead happens in AttendBeacon first. From there it travels to the systems you connect as it happens, and every delivery can be traced.

Included in every event, free or licensed
Connected once for the workspace, with a choice of which events take part
Credentials kept in Azure Key Vault, never in the database
A delivery log, so you can see what was sent, when, and whether it arrived

CRM

Every registration in your CRM, as it happens

Contacts, registrations, check-ins and leads from the stands are written to your CRM and kept up to date, so sales and marketing work from what really happened at the event.

Dynamics 365 and Customer Insights - Journeys

Contacts, event registrations, check-ins and leads in Dynamics 365, and real-time triggers so a journey can follow up the moment somebody registers or walks in. Check-in at the door, without custom development.

Salesforce

Contacts, registrations, check-ins and leads, kept in step through Salesforce's own API.

HubSpot

Contacts with their registrations, check-ins and leads, kept in step through HubSpot's own API.

How a CRM stays in step

One record per person, updated rather than duplicated: a ticket registered, renamed and cancelled within a minute is a single update
You choose which events a connection includes
Each record's state is visible, with a log of every delivery and retry
Leads only when the attendee agreed to share their details with the sponsor
AttendBeacon stays the system of record; your CRM is kept in step, never the other way round

Teams and Slack

Tell the team where they already talk

Post alerts to a Microsoft Teams or Slack channel, written for people rather than systems.

New registrations and cancellations as a digest, not a message per ticket
Nearly sold out and sold out, per ticket type
The doors opening, milestones and arrivals per hour on the day
Per channel: which events, which alerts and which language
Names only when you switch them on, and never an email address

Power Automate and Zapier

Automate the rest

Start a flow when somebody registers, checks in or becomes a lead, or let a flow issue a free ticket.

A custom connector for Power Automate and Logic Apps, built from the OpenAPI description
A Zapier app with instant triggers
Plain JSON with the same id on every retry, so a flow recognises a repeat
API keys that can only read, or read and issue tickets

Developers

Webhooks and a REST API

Everything the connectors use is open to your own systems too.

Signed webhooks

Registered, updated, cancelled, checked in, paid and more, sent to your address as it happens.

Signed in the Standard Webhooks format, so any receiver can verify them
Retries, and a delivery log for every call
Event types that are never renamed once published

REST API

Read events, attendees, orders and check-ins, and issue free tickets, with an OpenAPI description.

API keys per workspace, shown once and kept only as a hash
Scopes: read only, or read and issue tickets
An inbound address where another ticketing platform or Zapier posts attendees, each imported once

Your data

Only where you send it

An integration sends your event's data only to the systems you connect, and only what that connection needs. Those systems are yours: where they keep the data follows their settings and your agreement with their provider. AttendBeacon itself stays in the EU.

What stays in the EU

Product names are trademarks of their owners. AttendBeacon is not affiliated with or endorsed by them.

Connect your first system

Integrations are set up in the workspace and included in every event, free or licensed.

Open the workspace All features