RequiredVercel
Production hosting, preview deployments, edge delivery, and scheduled execution for the ConferenceOS application.
Application → global delivery
Integrations
Connect your AI to the whole event.
Give Claude or ChatGPT live conference context and permissioned workflows across ticketing, email, schedules, check-in, partners, and reporting—while every provider stays under your control.
Model-neutral MCP · Governed actions · Provider-owned accountsConferenceOSEvent graph
Clerk
Stripe
Resend
Inngest
Beehiiv
Anthropic
OpenAIMMCP
{}Webhooks
ASKquestions grounded in live event data
ACTthrough permissioned event workflows
CHECKsensitive changes pause for approval
TRACEevery agent action stays visible
01Technical integration directory
The connection layer, in detail.
For operators and implementation teams: every integration has a defined job, boundary, and relationship to the shared event model.
01
Platform foundation
The services that keep the system running.
A deliberately small core handles delivery, durable event data, and role-aware access.
Required
RequiredPostgreSQL / Neon
The durable system of record for events, people, sessions, inventory, payments, partners, and content.
Every workflow → one event graph
Full platformClerk
OAuth, user profiles, protected workspaces, and role-shaped access for every participant in the event.
People → the right workspace
02
Revenue and communication
Money and messages stay attached to the event.
Direct provider accounts handle transactions and audience delivery while ConferenceOS preserves operational context.
Native connectorStripe
Hosted checkout, payment confirmation, discount codes, refunds, and signed webhook reconciliation.
Purchase → registration
Native connectorResend
Confirmations, invitations, reminders, operational notices, and report delivery from event-aware workflows.
Event state → timely email
Native connectorBeehiiv
Add or update contacts and apply event-specific tags without manually moving registration lists.
Registration → publication audience
Native connectorKit
Synchronize attendees and event context into creator-led email automations and subscriber workflows.
Registration → subscriber journey
Native connectorMailchimp
Keep event contacts and campaign segments aligned with the registration record inside ConferenceOS.
Registration → campaign segment
03
Automation and intelligence
Let specialist services do specialist work.
Capabilities turn on when an event needs them and remain replaceable at the edge of the platform.
Native connectorInngest
Durable background jobs, scheduled reminders, delivery retries, and event-driven operational workflows.
Domain event → reliable work
AI connectionAnthropic / Claude
Connect Claude to live conference context and permissioned workflows through the agent interface.
Claude → governed event work
AI connectionOpenAI / ChatGPT
Connect ChatGPT to the same event graph, role permissions, approval gates, and action history.
ChatGPT → governed event work
Optional capabilityUploadThing
Managed uploads for speaker photos, sponsor assets, venue maps, and other event files.
Role portal → managed asset
Feed connectorMeetup
Bring community event listings into the organization experience through API or feed-based synchronization.
Community calendar → event surface
04
Team notifications and messaging
Event events, delivered where the team already is.
Outbound notifications go to the channel a crew already watches during a show, rather than to another inbox nobody has open.
SlNative connector
Team chatSlack
Selected event notifications delivered through a saved incoming webhook, chosen per event.
Event activity → your channel
DcNative connector
Team chatDiscord
The same event notification set delivered through a saved Discord incoming webhook.
Event activity → your server
TwOptional capability
SMSTwilio
Optional SMS for the messages that genuinely cannot wait for email, sent from a sender you configure. Recipients must have a confirmed opt-in.
Urgent notices → attendee handset
05
Audience, CRM and acquisition
The commercial side of the event, connected to the same records.
Sponsor and attendee relationships live against the event record, and campaign spend reports against it rather than beside it.
TnNative connector
CRMTwenty
Open-source CRM adapter with batched export of contacts and saved segments. Writes preview before they commit.
Event contacts → CRM records
MoNative connector
CRMMonday.com
Board-mapped adapter for teams already running sponsor and speaker pipelines on Monday.
Pipelines → boards
LoAlways available
CRMBuilt-in CRM
A local contact spine with role history across events, so a CRM is not a prerequisite for running one.
Contacts → event history
GaNative connector
MarketingGoogle Ads
Campaign connection for registration acquisition, managed from the promotions surface.
Campaigns → registrations
LiNative connector
MarketingLinkedIn Ads
The channel most B2B conferences actually buy on, connected to the same event.
Campaigns → registrations
MeNative connector
MarketingMeta Ads
Meta campaign connection for events with a consumer or community audience.
Campaigns → registrations
LuRead connector
TicketingLuma
Read guests, ticket types, and calendar events from Luma for paid registration. Two-way push and webhook ingest are on the roadmap, not shipped.
Luma guests → event records
06
Open interfaces
Extend the system without surrendering the core.
ConferenceOS exposes structured interfaces for software, agents, and workflows that need safe event context.
APIOpen interface
SoftwareREST API
Versioned endpoints let approved applications read and work with event, schedule, sponsor, and registration data.
External software → event services
MCPGoverned interface
AgentsMCP tools
Permissioned tools let approved assistants read event context, complete bounded work, request approval, and record the result.
Agent → governed event action
WHExtension path
EventsSigned webhooks
Publish verified event changes to downstream CRM, operations, analytics, and custom workflow endpoints.
State change → downstream system
CSVNo lock-in
PortabilityExports
Keep essential records portable for reporting, handoff, analysis, and systems that do not need a live connection.
Event data → portable record
02A connected handoff
One purchase. Four systems. Zero list shuffling.
Integrations matter when they remove work between moments—not when they merely appear in a settings screen.
A ticket is purchased
Stripe confirms payment; ConferenceOS creates the registration and preserves the transaction context.
The attendee joins the audience
The selected email provider receives the contact and event-specific tags without a spreadsheet import.
Automation takes over
Inngest schedules reminders and retries while Resend handles transactional delivery.
Every interface sees the same truth
Role portals, APIs, reports, and agents read the resulting event state from one connected model.
03Integration principles
Connected without being captive.
The platform keeps operational truth coherent while leaving specialist data in specialist systems the team owns.
Your provider accounts
Payments, messages, and audiences stay in accounts the event team controls.
Environment-scoped keys
Secrets stay outside the codebase and are isolated between development, preview, and production.
Graceful optionality
Non-core connections can be disabled without breaking the event record or public experience.
Planned native adapters
More direct connections where the workflow earns them.
Monday.com sync is live today. Luma, HubSpot, Discord, Meetup, and Salesforce are on the integration roadmap. Signed webhooks and portable exports provide the extension path in the meantime.
LumaHubSpotDiscordMeetupSalesforce
Bring the AI your team already uses
Open the live demo