Which Service Does What
| Service | What it's for | Direction |
|---|---|---|
| Zoom | Registers contacts for the Zoom webinars and meetings connected to your events, then sends attendance back to Rhythm. | Rhythm sends registrations to Zoom; Zoom sends check-in data back. |
| Cadmium EventScribe | Runs your conference mobile app and receives registrations for the sessions, functions, add-ons, and courses people purchased. | Rhythm sends registration data to EventScribe. |
| eShow | Manages exhibitor booths and brings booth purchases made in eShow into Rhythm as event registrations. | eShow booth purchases are pulled into Rhythm — the only one of the three that runs this direction. |
flowchart TD
A[What do you need?] --> B{Running a webinar or virtual meeting?}
B -->|Yes| C[Connect Zoom]
A --> D{Running a conference with a mobile app?}
D -->|Yes| E[Connect Cadmium EventScribe]
A --> F{Selling exhibitor booths?}
F -->|Yes| G[Connect eShow]
Zoom: Webinars and Meetings
Connect Zoom when you want Rhythm to register attendees in a Zoom webinar or meeting and give each person a unique join link. You approve the connection from Zoom's own sign-in page. Your organization can connect more than one Zoom account at the same time, which helps when departments or event series use separate Zoom accounts. After you connect a Zoom account, its settings page includes Reauthorize so you can approve the connection again without removing and reconnecting it.
Warning
Each registrant's join link belongs to that person and that registration; it is not the webinar's address with a different code swapped in. Do not build or edit a saved join link by hand, such as by changing only the webinar ID in a link you already have on file. The rest of the link is tied to the original registrant, so editing it by hand is likely to create a broken link instead of a working one for someone else.
See How Rhythm Registers People for Zoom Webinars and Meetings to learn what happens after someone registers.
Zoom's attendance notice must include an identifier Rhythm can match to the original registration before a join or leave can update anything in Rhythm. When Zoom sends that match, Rhythm records the check-in time on the matching registration as soon as the person joins. When Zoom does not send it, such as when the notice uses a different identifier than the one Rhythm registered the person under, Rhythm cannot tell which registration to update. In that case, Zoom can show the person as having attended while their Rhythm registration still has no join time.
Tip
Zoom meeting registration is newer in Rhythm than Zoom webinar registration. If you plan to use Zoom meetings instead of webinars for an event, confirm with Rhythm support that meeting registration is available and working for your account before you rely on it. Zoom's own connection or reauthorization screen can list meetings before Rhythm fully supports them for your account, so seeing meetings there does not confirm that meeting registration is ready for you.
Cadmium EventScribe: The Conference App
Connect EventScribe when your conference uses Cadmium's mobile app and you want registrants to see their sessions, functions, add-ons, and courses there automatically. To set it up, choose the Rhythm event that feeds EventScribe, then map that event's registration packages to the access levels EventScribe uses. That mapping helps the app show the right content to the right registrants.
eShow: Exhibitor Booths
Connect eShow when your association sells exhibitor booths through eShow and wants those purchases recorded in Rhythm automatically, instead of entering them by hand. Zoom and EventScribe send registrations out of Rhythm, but eShow works in reverse: Rhythm pulls booth purchases from eShow and creates matching registrations in the Rhythm event you choose. Rhythm uses a badge-allocation formula based on booth size to decide how many badges each purchase includes.
When Rhythm Has No Direct Connection
Zoom, EventScribe, and eShow are the event and webinar platforms Rhythm connects to directly. If your association uses a different event app, exhibitor system, or marketing tool, Rhythm's open API can still move data between the two systems. Your organization's developers or the other vendor need to build against it, because there is no ready-made connection to turn on. Before you scope that build, check whether the other system can push data to Rhythm on its own or only allows Rhythm to poll it for updates. That difference determines which side of the connection you build first.
Some common needs already have a path through Zapier instead of a custom build. If you want a new Rhythm event registration to reach another system, such as badge-printing software, a Zapier event stream can carry that registration data out of Rhythm. Zapier can also connect Rhythm to Google Groups and to EZ Texting, though Rhythm does not provide setup or implementation support for either connection. You would work with Zapier directly or with a third party familiar with it, and for EZ Texting you still need to decide what Rhythm data you want to send before building the flow.
A form hosted outside Rhythm, such as one built directly on your association's website, does not automatically send its submissions into Rhythm. That handoff needs its own integration, typically built against the open API, rather than happening on its own because the website and Rhythm both belong to your association. The same applies when you want to display Rhythm data on an external site. Rhythm's API can supply information such as committee rosters or current-member status, but your website developers still have to build the part that pulls that data and displays it there. Rhythm does not build or host that side of the integration.
Setting Up More Than One
You can connect any combination of these three services. Connecting one does not require or affect the others. Start with the service your next event needs, then return to this page when a later event needs a different connection.