BigMarker
SchedulingRun BigMarker webinars from your flows. Agents create and update conferences, register attendees, keep registration data in sync, and browse channels to route events to the right webinar hub.
What This Integration Enables
Webinar programs die in the plumbing between the signup form and the platform, and BigMarker's API is built to remove that plumbing entirely. FlowRunner agents create and update conferences inside the right channel, register people the moment they sign up anywhere, keep registration data reconciled in both directions, and hold onto the one asset teams keep losing: each registrant's unique join URL, written back wherever the follow-up will happen. - Turn [Typeform](/integrations/typeform) responses into confirmed registrations with custom fields and UTM attribution intact - Enroll new [Shopify](/integrations/shopify) buyers into an onboarding webinar as part of the order flow - Bulk-register contact lists from [Google Sheets](/integrations/google-sheets) and write the join URLs back - Spin up recurring webinars programmatically in the right channel with title, timing, and privacy set - Keep the registrant list reconciled against the CRM, with cancellations and pending states surfaced for review The channel structure matters here: BigMarker organizes webinars into hubs, and the connector's channel lookup means an agent routes each new event to the right hub instead of piling everything into one. The other structural advantage is the upsert: Update Registration matches by conference and email and creates the registration when none exists, which lets sync flows run repeatedly against the same list without ever producing a duplicate seat.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Form to confirmed seat, with attribution
A [Typeform](/integrations/typeform) response lands with name, email, company, and the UTM source that brought them. The agent checks List Registrants for a duplicate, then calls Register Person with the custom fields and UTM attached. The response includes the registrant's unique join URL, which writes to the CRM record and into the confirmation flow. Marketing later reports signups by source without reconstructing anything, because attribution rode along at registration time.
The customer onboarding webinar that fills itself
When [Shopify](/integrations/shopify) fires On New Order for a product with a live onboarding series, the agent finds the next session with List Conferences filtered to future events, registers the buyer with Register Person and their order id as the external user ID, and posts the new attendee to the customer success channel in [Slack](/integrations/slack). Every buyer gets invited to the session that teaches them the product, and nobody maintains the invite list.
The bulk registration with a checkpoint
A partner hands over 400 contacts in [Google Sheets](/integrations/google-sheets) for a co-hosted event. The agent reads the rows, validates emails, dedupes against List Registrants, and presents the summary: 371 new, 18 already registered, 11 malformed. The webinar owner approves, Register Person runs down the list, and the join URLs write back to a new sheet column. The 11 bad rows go back to the partner instead of bouncing as confirmation emails.
Human-in-Loop Highlight
Register Person does not quietly add a row to a list. Each call enrolls a real email address, which triggers BigMarker's confirmation to that person's inbox with a unique join URL, and in bulk flows that multiplies fast: point the agent at the wrong sheet tab, or the right tab with last quarter's contacts still in it, and 400 people receive an invitation to an event they never asked about, from your brand, unrecallable. So FlowRunner's bulk registration flows stop before the first send. The agent does the validation, deduplication, and counting, then presents the docket: which conference, how many net-new emails, which source list, sample rows included. The webinar owner looks at the sample, catches that these are the Q1 churned accounts, and redirects. The gate costs thirty seconds. The apology email it prevents costs credibility with 400 people at once.
Agent Capabilities
8 actionsConferences
4- List Conferences Lists webinars with pagination and filters by role, lifecycle type such as future, past, or happening now, and title search. The lookup behind "find the next onboarding session" logic.
- Get Conference Retrieves one webinar in full by ID: title, purpose, start time, duration, privacy, recording details, and complete configuration. The inspection step before updates and reporting.
- Create Conference Creates a new webinar inside a channel with title, start time, duration, purpose, schedule type, webcast mode, and privacy. Returns the ID and the registration URL that every downstream flow needs.
- Update Conference Updates an existing webinar by ID, changing only the fields provided. The reschedule and correction tool, used with care once registrants exist, because their plans move with it.
Registrations
3- List Registrants Lists a conference's registrants with email, name, unique attendance URL, and tracking data, with filters by email, registration window, and canceled or pending status. The dedup check and the reconciliation read.
- Register Person Registers a person for a webinar with email, first name, last name, optional custom fields, UTM source, and external user ID, returning their unique join URL. The write that reaches an inbox, and the reason bulk flows carry a human checkpoint.
- Update Registration Updates an existing registration matched by conference and email, changing only the custom field values provided, and creating the registration if none exists. The upsert that keeps registration data synced without duplicates.
Channels
1- List Channels Lists the webinar hubs you can access, with ID, URL, name, overview, and host information. The routing step that puts each new conference in the right hub.
Frequently Asked Questions
What can FlowRunner do with BigMarker?
FlowRunner agents can run List Conferences, Get Conference, and Create Conference in BigMarker, plus 5 more actions.
Does connecting BigMarker to FlowRunner require OAuth?
No. BigMarker connects to FlowRunner with an API key, no OAuth flow required.
Can BigMarker trigger a FlowRunner workflow automatically?
BigMarker doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with BigMarker
$100 in credits. No card required. Connect in minutes.