Skip to content
EventOS
IntegrationsCreate an event

Integrations: EventOS inside your stack

An event does not run alone — orders, check-ins and updates reach your CRM and pipeline. This is what connects today.

Webhooks to your pipeline

An organisation points an HTTPS endpoint at the business facts it needs. Every delivery is signed (HMAC-SHA256), retried for up to twelve hours and journaled. Through Zapier, Make or n8n the facts land in HubSpot, Salesforce, Dynamics or Marketo — no custom code.

Facts an endpoint can subscribe to

  • EVENT_CREATED
  • EVENT_UPDATED
  • EVENT_PUBLISHED
  • EVENT_CANCELLED
  • EVENT_DELETED
  • ORDER_CREATED
  • ORDER_STATUS_CHANGED
  • ATTENDEE_CHECKED_IN

Contacts and guest history

Each organisation keeps its own contact list: buyers import from paid orders in one action, and a contact's card carries their events — roles, the latest one and check-ins. The guest sees the same trail in their own wallet across every organiser.

Checkout inside your site

The registration page embeds at /embed/e/<slug> — the organisation whitelists the exact domains allowed to frame it, so the widget cannot be pasted onto a phishing page.

Telegram

The organisation's own bot answers guests and delivers tickets; event groups coordinate the door and the team in the messenger they already use.

On the roadmap

Signed API keys for direct REST access and native two-way connectors for HubSpot, Salesforce, Dynamics and Marketo are planned. Today the webhook channel plus the contacts API covers the sync — including the guest's history across events.