What each integration syncs
Most connectors push accepted sessions and the people on them out of Sessionboard into a registration platform, event app, or website, on a schedule you control. A few pull data in. Use this page to decide which system owns which data before you connect anything; the per-app articles carry the click-by-click setup.
The matrix
Section titled “The matrix”| Integration | Direction | What moves | Trigger | Connected at | Who sets it up |
|---|---|---|---|---|---|
| Cvent | Sessionboard → Cvent | Accepted sessions and their speakers; optionally subsessions (as Programs), moderators, chairpersons, and session content | Manual Sync, or continuous (about every 30 minutes) | Organization | Your admin, with the Cvent API credentials |
| Swapcard | Sessionboard → Swapcard | Accepted sessions, content, and speakers; optionally moderators and chairpersons; speakers can be created as Swapcard users | Manual or continuous (about 30 minutes) | Organization | Your admin, with a Swapcard API key |
| Grip | Sessionboard → Grip | Accepted sessions and speakers; moderators and chairpersons with a Speaker Role ID; deleted sessions and un-accepted speakers can be removed on the next sync | Manual or continuous (about 30 minutes) | Organization | Your admin, with a Grip API token |
| Swoogo | Sessionboard → Swoogo | Accepted sessions and speakers; optionally chairpersons, moderators, and sponsors; optional removal of deleted or un-accepted records | Manual or continuous (about 30 minutes) | Organization | Your admin, with the Swoogo consumer key and secret |
| Bizzabo | Sessionboard → Bizzabo | Accepted sessions (with rooms) and speakers, with mapped session fields | Manual or continuous (about 30 minutes) | Organization | Your admin, with the Bizzabo client credentials |
| ExpoPlatform | Sessionboard → ExpoPlatform | Accepted sessions and confirmed speakers, with mapped session and speaker fields | Manual or continuous (about 30 minutes) | Organization | Your admin, with the ExpoPlatform access token and URL |
| Stova | Sessionboard → Stova | Accepted sessions and their speakers, with mapped session fields. Records are not removed from Stova when a status changes in Sessionboard | Manual or continuous (about 30 minutes) | Organization | Your admin, with the Stova credentials |
| ASP Events | Sessionboard → ASP | Accepted sessions and speakers to a Seminar; previously synced records are marked inactive when they leave the accepted set | Manual or continuous (about 30 minutes) | Organization | Your admin, with the ASP API key and secret |
| LiveBuzz | Sessionboard → LiveBuzz | Accepted sessions (seminars), theaters, and speakers (customers) to a campaign; choose which session roles go; optional removal when un-accepted | Manual or continuous (about 30 minutes) | Organization | Sessionboard adds the app for you; your admin saves the connection and mapping |
| Visit | Sessionboard → Visit | People on accepted sessions as visitors on a registration form; optionally sessions as activities | Manual or continuous (about 30 minutes) | Organization | Sessionboard adds the app for you; your admin saves the connection and mapping |
| Brella | Sessionboard → Brella | Speakers and content timeslots from accepted sessions; speakers come off a timeslot when they leave the accepted set | Manual or continuous (about 30 minutes) | Organization | Your admin, from Apps |
| Map Your Show | Map Your Show → Sessionboard | Active exhibitors (name, booths, website, description, logo) as exhibitors on the event, and their booth contacts linked to each company for Advocacy. Never deletes, never writes back | Manual, or every 6 hours until the event ends | Organization | Your Customer Success Manager, with the MYS API username, password and show code from your MYS account manager |
| Maritz RTS | Maritz → Sessionboard | Registrant profile fields (job title, company, bio, registration state) onto contacts that already exist. Never creates contacts, never writes back | Scheduled pull | Organization | Your admin, with RTS credentials from your Maritz project manager |
| ON24 | ON24 → Sessionboard | Past webinars and their speakers into the Speaker CRM | Manual import | Organization | Your admin, with the ON24 access token key, secret, and client ID |
| Gleanin | Sessionboard → Gleanin | Accepted sessions and speakers; optionally chairpersons and moderators; tracks or tags as Gleanin tracks. Share links come back to the speaker portal | Manual or continuous (about 30 minutes) | Organization | Your admin, with a Gleanin API token |
| Snöball | Sessionboard → Snöball | Sessions and speakers, so Snöball can generate share links you surface as a portal task | Snöball connects using an API token you create | Organization | You create the token; Snöball completes the connection |
| InGo | Widget embed | An InGo social-share widget inside the portal | — | Portal | Your admin, with the widget code from InGo |
| Docusign | Sessionboard → Docusign → Sessionboard | Agreements sent from contact, account, group, and pipeline records; signature status returns to the record | Per send | Each teammate connects their own Docusign login | Each sender |
| Single Sign-On | Identity provider → Sessionboard | Authentication for admins, portal users, and submitters (SAML, OIDC, or OAuth 2.0 Password) | At sign-in | Organization, enabled per event | Your IT team with your admin |
| Zapier | Either direction, per Zap | Triggers and actions on Sessionboard records to 6,000+ apps | Per Zap | Event, with an organization API token | Your admin |
| Webhooks | Sessionboard → your endpoint | Real-time notifications when data changes | Real time | Organization | Your developer |
| Public API | Either direction | Anything the API exposes, including SbQL and MCP for AI assistants | On request | Organization | Your developer |
Which way does it flow?
Section titled “Which way does it flow?”Sessionboard is the system of record for who is speaking and what they are presenting. Every outbound connector keeps the destination in step with the accepted program. Registration systems own who is attending, so speaker registration status comes back only where a connector pulls it (Maritz RTS) or where you build it with Zapier, webhooks, or the API.
Plan the boundary before setup:
- Decide where speakers are created first. If speakers apply through your submission form, Sessionboard creates the contact and the outbound sync creates them downstream.
- Decide what “removed” should mean in each destination. Grip, Swoogo, LiveBuzz, and ASP can remove or unpublish records that leave the accepted set. Brella takes the speaker off the timeslot but keeps both records, and Stova keeps them until you delete them there.
- Use standard fields wherever a connector maps fields. Custom fields sync only where the app article lists a mapping step.
Field mapping
Section titled “Field mapping”Connectors that push people or sessions decide which fields travel with a field map — one row per pair, Sessionboard field on the left, destination field on the right. The destination’s required fields are starred and always sent; everything else is optional, and a field with no row is not sent at all. The pickers are filtered by type, so a date can only land in a date field and a dropdown in a text or multi-answer field. Set the map up before the first sync, on the app’s Map Speaker Fields and Map Session Fields tabs, and read the sync result afterwards under Event → History → Integrations. Before you connect walks through the map, the reasons a mapped field can still be empty on the other side, and how to read a sync result.
Common questions
Section titled “Common questions”Can we control which sessions and speakers sync, or send only accepted ones?
Every outbound connector sends only accepted sessions and the people on them, so the accept/decline decision is the sync control. Most connectors let you also choose roles: turn moderators, chairpersons, sponsors, or custom roles on or off in the event settings of the mapping. On Grip, Swoogo, LiveBuzz, Brella, and ASP you can also decide what happens when a record leaves the accepted set. Speakers you do not want in the destination should stay out of the accepted set or in an unchecked role.
How often does it sync, and can we force an update?
Outbound connectors run when you click Sync on the mapping. Turn on Enable Continuous Sync and Sessionboard also pushes changes about every 30 minutes; a manual sync between intervals is still allowed. Continuous sync on LiveBuzz, Visit, and Brella requires at least one accepted session that has not ended.
What happens to duplicates, deletions, and edits across systems?
A mapped connector updates the records it created on the next sync instead of creating a second copy, so renaming a session or correcting a speaker’s details is reflected downstream rather than duplicated. Each app article states how it matches records; Brella and Visit, for example, match on the Sessionboard contact rather than the email address. Deletions and un-acceptances are handled per app: see the Remove Deleted Sessions and Remove Deleted Speakers settings on Grip and Swoogo, Remove from LiveBuzz when un-accepted, and the “marked inactive” behaviour on ASP. Stova keeps records until you delete them in Stova. One Sessionboard event maps to one destination event or campaign on each connector.
Can Sessionboard integrate with our registration platform?
Yes, for Cvent, Swoogo, Bizzabo, ExpoPlatform, Stova, Visit, LiveBuzz, and Maritz RTS, each covered in the table above. For registration systems without a connector, use Zapier to create registrations when a session is accepted, or have your developer use the public API and webhooks. Weigh platforms side by side in the event platform comparison.
Can we sync the agenda and speakers to our website (WordPress, Webflow, or a CMS)?
For most websites you do not need a connector. Agenda and speaker embeds drop a live agenda or speaker list into any page that accepts an embed, and a Program Site or content gallery publishes the program from Sessionboard directly. ASP Events and Stova have native website connectors. Anything else can read the public API.
Which mobile and networking apps are supported?
Swapcard, Grip, Brella, Bizzabo, ExpoPlatform, Stova, and Cvent. All are one-way from Sessionboard: accept and schedule sessions in Sessionboard and the app follows. Speaker registration or login in those apps is a setting on the connector, for example Sync Speakers as Users on Swapcard.
Can we connect our CRM, marketing platform, or AMS?
The Speaker CRM is the org-level contact database in Sessionboard; ON24 imports webinar history into it and Docusign sends agreements from its records. Salesforce, HubSpot, Marketo, and association management systems connect through Zapier, webhooks, or the public API. Member directories can also sign speakers in through Single Sign-On.
Can speakers sign in with our SSO, and can their profile be pre-filled?
Yes. SSO supports SAML, OIDC, and OAuth 2.0 Password, with separate configurations for submission forms, portals, and admin login, enabled per event. See Single Sign-On for what your identity provider needs to send. Without SSO, portal users sign in with a username and password or a magic link sent by email; see choose how portal users sign in.
What API access do we get, and is there a test environment?
Organization admins create tokens under Settings > API Tokens. A token covers the public API and SbQL. Claude, ChatGPT, and the other assistants connect separately, by signing in — see Connect AI assistants. API reads are cached for 3 minutes, while webhooks are real time. Create a separate token per integration so one can be revoked without affecting the others. See generating API tokens.
Who owns setup — us or Sessionboard?
Your admin connects most apps from Apps in the left sidebar with credentials from the other vendor (organization Settings > Integrations now opens Apps). LiveBuzz is added to your organization by Sessionboard on request to support@sessionboard.com; after that, the connection and event mapping are yours. Snöball completes its own connection using an API token you create. Docusign is connected per teammate.
We use a tool that is not listed (MapYourShow, SurveyMonkey, Dropbox, PandaDoc, Webex)
Check the App marketplace first, since it grows with customer demand. Otherwise: survey and evaluation links can be shared as a portal wiki page or task; documents to sign are covered by Docusign contracts or a file request; and anything with a Zapier app can be automated with Zapier. Email support@sessionboard.com with the tool and the data you need to move.
Related
Section titled “Related”- App marketplace — every connector, grouped by what it does
- Event platform comparison — website, app, badge, and registration capabilities side by side
- Accept or decline submissions — the status that drives every outbound sync