Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified public/og/concepts--custom-field-type-reference.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified public/og/portals--submission-change-notifications.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
33 changes: 32 additions & 1 deletion src/content/docs/apps/bizzabo-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,12 @@ title: "Bizzabo"
description: "Bizzabo is an event management platform offering a comprehensive tool suite to help organizations plan, manage, and execute events."
---

import { Note } from '@compat';
import { Note, Accordion, AccordionGroup } from '@compat';

<img src="/logo/apps/bizzabo-integration.png" alt="Bizzabo logo" width="52" height="52" style={{borderRadius:"12px"}} />

![Sessionboard and Bizzabo logos](/images/kb/sessionboard-bizzabo-integration-banner.png)

Sessionboard users can connect their events with Bizzabo to sync session and speaker data from Sessionboard to Bizzabo. This one-way integration is a user-friendly process that facilitates data transfer to Bizzabo once users have approved and scheduled their sessions in Sessionboard.

---
Expand Down Expand Up @@ -158,3 +160,32 @@ To disconnect from the integration, go to your Organization > Settings > Integra
Once the integration is disconnected, you can reconnect using a separate API key or reuse the same credentials.

Disconnecting the integration will disconnect all mapped events. Previously-synced sessions will not be able to be resynced even if you remap the same events. The integration should only be disconnected if you intend to sync to a new organization.

---

## FAQ

<AccordionGroup>
<Accordion title="Which direction does data sync?">
One way, from Sessionboard to Bizzabo. Sessions and speakers you approve and schedule in Sessionboard are pushed to Bizzabo; changes made in Bizzabo are not brought back into Sessionboard.
</Accordion>
<Accordion title="What credentials do I need to connect?">
The client ID, client secret, and account ID associated with your Bizzabo event. Enter them at the organization level under **Organization > Settings > Integrations**.
</Accordion>
<Accordion title="How often does the sync run?">
With continuous sync enabled, records are created and updated on a regular interval of approximately 30 minutes. You can also push a manual sync at any time from **Sessions > Agenda > Options > Sync to Bizzabo**.
</Accordion>
<Accordion title="What happens in Bizzabo when I delete a session or speaker in Sessionboard?">
Nothing is removed from Bizzabo. Deleting a session or speaker in Sessionboard, or changing its status, does not delete the record in Bizzabo — you delete it there manually.
</Accordion>
<Accordion title="Can I map more than one event?">
Yes, more than one event can be mapped per Sessionboard organization, but every Bizzabo event must be associated with the same client ID, client secret, and account ID. Once a Bizzabo event has been mapped to a Sessionboard event, neither can be re-mapped to another event.
</Accordion>
<Accordion title="Why are session times wrong in Bizzabo?">
Check that the time zones in both events match before syncing. In Sessionboard, confirm the timezone on the event's Details page. If you need to change it, contact [support@sessionboard.com](mailto:support@sessionboard.com).
</Accordion>
</AccordionGroup>

## Still having issues?

Email [support@sessionboard.com](mailto:support@sessionboard.com) and include the connection name, the mapped event, and the session or speaker that did not sync. Do not send your client secret.
46 changes: 38 additions & 8 deletions src/content/docs/apps/grip-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,11 @@ title: "Grip"
description: "Grip is an AI-powered event networking solution for virtual, hybrid, and in-person events. Sync your Sessionboard session and speaker data to Grip."
---

import { Note } from '@compat';
import { Accordion, AccordionGroup } from '@compat';

<img src="/logo/apps/grip-integration.png" alt="Grip logo" width="52" height="52" style={{borderRadius:"12px"}} />

<Note>
🚨 Need Assistance? Contact Sessionboard 🚨
</Note>

![Grip](/images/kb/52f10188-Integration-3--1.png)
![Sessionboard and Grip logos](/images/kb/52f10188-Integration-3--1.png)

Grip is the leading AI-powered event networking solution for Virtual, Hybrid, and In-person events.

Expand Down Expand Up @@ -60,12 +56,21 @@ Once the integration is connected, a window will appear prompting you to map you

## Event Settings

Once you have selected your event mapping you will be required to enter your Speaker Data Type ID*, which is required to proceed. This will allow for all net new speakers that are created from Sessionboard to have the correct Data Type.Groups and Session Roles are all optional fields and if you wish to use those within Grip you can also provide that information at this time.
Once you have selected your event mapping you will be required to enter your Speaker Data Type ID*, which is required to proceed. This will allow for all net new speakers that are created from Sessionboard to have the correct Data Type. Groups and Session Roles are all optional fields and if you wish to use those within Grip you can also provide that information at this time.

![Event Settings](/images/kb/b2588580-image-png-Feb-26-2026-08-01-21-8357-PM.png)

If you would like to leverage Session Roles you must include a Speaker Role ID in order to sync your Moderator and Chairpersons

### Remove deleted sessions and speakers

The Integration section of the event settings includes two options that let Sessionboard handle removals in Grip for you:

- **Remove Deleted Sessions** — sessions that have been deleted in Sessionboard are deleted from Grip on the next sync.
- **Remove Deleted Speakers** — speakers who no longer hold an accepted session in Sessionboard are no longer speakers in Grip. Their Grip registration is never deleted: they are moved to the data type you set in **Default Data Type ID** (for example, the event's Attendee type) and stay in the Grip event as contacts, so anyone who is also a regular attendee keeps their access. If they are later re-added to an accepted session, they are restored as speakers on the next sync.

**Default Data Type ID** is required when **Remove Deleted Speakers** is enabled. If it is missing, the removal is skipped and retried on a later sync.

---

## Map session fields
Expand Down Expand Up @@ -106,7 +111,7 @@ Below is a list of standard fields that will be synced. Field(s) with an asteris

## Syncing sessions and speakers IMPORTANT INFORMATION
Before syncing your event, please review the following important notes:
- Sessions and/or speakers will not be removed from Grip if speaker and/or session statuses are changed in Sessionboard. Admins will have to manually delete the session/speaker record in Grip.
- By default, sessions and speakers are not removed from Grip if speaker and/or session statuses are changed in Sessionboard — admins have to manually delete the session/speaker record in Grip. To have Sessionboard handle removals automatically, enable **Remove Deleted Sessions** and **Remove Deleted Speakers** in the [event settings](#remove-deleted-sessions-and-speakers).
- Speakers that are pre-existing in Grip will be updated
- Only accepted sessions, and their associated speakers, will sync to Grip.
- Sessions must have a date, time, track and location to be synced.
Expand Down Expand Up @@ -162,6 +167,31 @@ This will open the mapping window. A list of existing mappings will be displayed

---

## FAQ

<AccordionGroup>
<Accordion title="Which direction does data sync?">
One way, from Sessionboard to Grip. Sessions and speakers you approve and schedule in Sessionboard are pushed to Grip; changes made in Grip are not brought back into Sessionboard.
</Accordion>
<Accordion title="How often does the sync run?">
With continuous sync enabled, records are created and updated on a regular interval of approximately 30 minutes. You can also push a manual sync at any time from **Sessions > Agenda > Options > Sync to Grip**.
</Accordion>
<Accordion title="Which sessions and speakers sync to Grip?">
Only accepted sessions and their accepted speakers. Sessions must have a date, time, track, and location, and sessions that have already passed will not sync. Each speaker needs a unique email address.
</Accordion>
<Accordion title="What happens in Grip when I remove a session or speaker in Sessionboard?">
That depends on your event settings. With **Remove Deleted Sessions** enabled, deleted sessions are deleted from Grip on the next sync. With **Remove Deleted Speakers** enabled, speakers with no remaining accepted session are moved to your **Default Data Type ID** and stay in the Grip event as contacts. With both options off, nothing is removed from Grip and you delete the records there manually.
</Accordion>
<Accordion title="Where do I enter the Grip API token?">
At the organization level, under **Organization > Settings > Integrations**. Connect the Grip integration, add a new connection, and enter the API token associated with your Grip event.
</Accordion>
<Accordion title="Can I sync individual sessions instead of the whole agenda?">
Yes. On the Agenda tab, select the sessions you want to sync, then click **More > Sync to Grip**.
</Accordion>
</AccordionGroup>

---

### Integration Support

If you are experiencing problems with syncing (i.e. error messages or data not appearing in Grip), email support@sessionboard.com with the following information:
Expand Down
Loading