ClickMeeting

Run ClickMeeting webinars and online meetings from your flows. Agents create, update, and delete conference rooms, register attendees, and pull past session statistics for reporting.

9 actions API key available

ClickMeeting website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A webinar sign-up lands from the registration form on the website

List Registrations confirms the person is not already registered for the room

The registrant is synced to the CRM so marketing sees webinar interest on the contact record

A confirmation email with the room URL and join details goes out to the attendee

The day before the event, the agent compares confirmed registrations against the room's capacity plan

The event owner reviews the registration picture and decides whether to add a second session, adjust the room, or leave it alone

What This Integration Enables

Webinars are recurring operations dressed up as events. The room setup, the registration handling, the reminder sequence, and the attendance report are the same every time, which makes them agent work. FlowRunner agents create and update ClickMeeting conference rooms from your event plans, register attendees captured from forms and CRMs, reconcile registration lists before the event, and pull session statistics into your reporting stack afterward. The part worth being opinionated about: the webinar platform should never be the system of record. Registrations belong in your CRM, attendance belongs in your reporting, and ClickMeeting is where the event happens. This connector keeps all three in agreement without a person shuttling CSVs between them. - Create, update, and delete conference rooms from workflow logic - Register attendees from any form, CRM, or sign-up source, with dedup on the way in - Reconcile active and pending registrations before events - Pull per-session attendee and visitor counts into reporting after each event

Without FlowRunner

Registration lists in three places The form tool, the webinar platform, and the CRM each hold a different version of who is coming

Manual room setup per event Every webinar means clicking through room creation, copying URLs into emails, and hoping the settings match last time

Post-event numbers on request Attendance stats live inside the platform, and reporting means someone exports them after being asked twice

With FlowRunner

One registration pipeline Sign-ups flow from form to room to CRM in a single agent pass, deduplicated on the way in

Rooms created by workflow Agents create and configure conference rooms from the event calendar, with URLs distributed automatically

Attendance as a dataset Session stats land in your reporting sheet after every event, without anyone logging in to fetch them

Use Case Scenarios

Form to room to CRM, one pass

A sign-up arrives from [Typeform](/integrations/typeform). The agent calls List Registrations to check for an existing entry, then Register Person to enroll the attendee with their custom field answers intact. A [HubSpot](/integrations/hubspot) contact is created or updated with the webinar touchpoint, and a confirmation with the room URL goes out through [Gmail](/integrations/gmail). Every registrant exists in exactly three places, and all three agree, because one flow wrote all of them.

The recurring webinar series that runs itself

A monthly product webinar is a calendar entry, not a project. On schedule, the agent calls Create Conference with the standard name pattern, access type, and duration, emails the host their URL, and opens registration. The week of the event, List Registrations feeds a reminder sequence for confirmed attendees and a nudge for pending ones. If the date moves, Update Conference changes the schedule and the agent re-notifies everyone who registered, so the change costs the team one edit instead of an afternoon.

The morning-after attendance report

The day after each session, the agent calls List Sessions for the room, then Get Session for the newest occurrence, and writes start time, duration, attendee count, and visitor count to [Google Sheets](/integrations/google-sheets). Registrants who did not attend get flagged back to the CRM for a follow-up sequence. Marketing opens a spreadsheet that is already current, and the show-up rate conversation happens with numbers instead of impressions.

Human-in-Loop Highlight

Delete Conference removes a room and its scheduled session permanently, and a room is rarely just a room: it has an access URL already sitting in confirmed attendees' calendars and a registration list attached. An agent consolidating duplicate events or cleaning up a moved series could easily delete the room three hundred people plan to join. So FlowRunner flows treat room deletion as a proposal. The agent presents the room, its schedule, and its registration count from List Registrations, and the event owner confirms before Delete Conference fires. The same review applies when Update Conference would change a live event's time, because a schedule change is a promise broken to everyone already registered. Setup and sync run autonomously; changes that reach registered attendees wait for the person whose name is on the event, which is FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) pattern doing exactly what it exists for.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

9 actions

Conferences

Create Conference Creates a new conference room, meeting or webinar, with room type, name, and access type. Scheduled rooms take a start time and duration; permanent rooms stay available indefinitely. Returns the room ID and shareable access URL.
Get Conference Retrieves full details of a single room by its numeric ID: name, type, access settings, schedule, host and participant URLs, and registration configuration.
List Conferences Lists all conference rooms on the account, active and finished, with a Status filter to narrow to one or the other. The inventory call behind event dashboards and cleanup sweeps.
Update Conference Updates an existing room by ID. Only provided fields change; omitted fields keep their values. Can change name, access type, schedule, duration, password, timezone, and language.
Delete Conference Permanently deletes a room and its scheduled session by numeric ID. Cannot be undone, which is why this page's human gate exists. Past recordings and reports may be retained by ClickMeeting separately.

Registrations

Register Person Registers a person for a room that requires registration, with first and last name, email, and any custom registration fields the room defines. Returns the created registration record.
List Registrations Lists registrants for a room filtered by status: Active for confirmed, Pending for awaiting confirmation. Each entry carries the submitted fields and registration date. The dedup and reminder backbone.

Sessions

List Sessions Lists past sessions of a room, each with session ID, start and end times, and attendee counts. The entry point for post-event reporting.
Get Session Retrieves detailed statistics for a single past session: precise start and end times, duration, and attendee and visitor counts.

Frequently Asked Questions

What can FlowRunner do with ClickMeeting?

FlowRunner agents can run List Conferences, Get Conference, and Create Conference in ClickMeeting, plus 6 more actions.

Does connecting ClickMeeting to FlowRunner require OAuth?

No. ClickMeeting connects to FlowRunner with an API key, no OAuth flow required.

Can ClickMeeting trigger a FlowRunner workflow automatically?

ClickMeeting doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with ClickMeeting

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us