StealthSeminar
SchedulingConnect AI agents to StealthSeminar, an evergreen and automated webinar platform. Agents read a webinar's type, timezone, and upcoming session times, then register attendees into a chosen session. There is no action to list or remove a registration.
What This Integration Enables
This is a two action connector, and both actions are worth understanding precisely because there is nothing else here to fall back on. Get Webinar Registration Information reads a webinar's public registration detail by its short ID, the code of up to six characters that appears in its registration page URL, and returns the title, the type, the timezone, the duration, the registration page and tracking configuration, and the list of upcoming session times available for registration. Register Attendee registers a person for one of those sessions, requiring their email address and a start time that exactly matches one of the upcoming times the first action returned, and optionally capturing the name, SMS number, timezone, GDPR consent flag, custom registration fields and link and UTM parameters. It returns the created registration including the attendee record and any auto login details.
Two boundaries follow directly from that and are easy to assume wrongly. This connector does not create, configure or publish a webinar. Webinars are built in StealthSeminar and this connector addresses one that already exists by its short ID. And it does not read registrants back: there is no action here that lists who has registered, retrieves a registration, or removes one. The registration record you get is the one returned by the call that created it, so a flow that needs a roster keeps its own, written to whichever system is going to act on it. That asymmetry, a write with no matching read and no delete, is the single most important design fact about this connector.
The type field returned by Get Webinar Registration Information deserves its own paragraph, because StealthSeminar is an evergreen and automated webinar platform and the field tells you which kind of thing the session actually is: automated, replay, live or hybrid. An automated or replay session is a recording playing to a schedule. That is a legitimate and widely used format, and it is also a fact the person being registered has a reasonable interest in. Reading the type before registering somebody is what lets a flow keep the invitation honest, and this connector makes it a single call.
There are no triggers here. StealthSeminar does have webhooks for register, attend, missWebinar, attendReplay and conversion, but they are configured in the StealthSeminar dashboard rather than through the API, so nothing in this connector registers a callback and no StealthSeminar event starts a flow through it. Flows begin wherever the lead qualifies: a form, a CRM stage change, a scoring threshold, a scheduled segment read.
One operational note that is unusual enough to state plainly. StealthSeminar's documented registration endpoints are public, so this service defines no configuration items and requires no API key, token or account credential. The short ID is the entire address. That makes the connector trivially easy to configure and it puts the whole burden of getting the right webinar onto whoever supplies that six character code.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A qualified lead placed into the next session automatically
A demand generation team scores leads in the CRM and wants the ones that cross a threshold in front of the product webinar without another email in the chain. When a contact in HubSpot reaches the qualifying stage, the agent calls Get Webinar Registration Information for the webinar's short ID, reads the upcoming session times and picks the next one that is far enough out to give the person notice in their own timezone, which the same response provides. It calls Register Attendee with the contact's email and name, the chosen start time passed back exactly as returned, and the original campaign's link and UTM parameters so the registration carries its own attribution rather than having it stitched on later. It writes the returned registration back onto the CRM contact, because nothing in this connector will tell it later that the person registered.
A roster the flow keeps for itself
There is no action here that lists registrants, so a team that wants to know who is coming has to build that record as it goes. The agent maintains it deliberately: every successful Register Attendee response is appended to Google Sheets with the email, the session start time, the webinar short ID and the campaign parameters submitted, and the same facts are written to the contact record in the CRM. Before each session it reads its own roster rather than the platform's, filters to the people registered for that start time, and sends a reminder through Gmail with the timezone the platform reported for that webinar rather than the sender's. Where a registration call fails, the failure is recorded and surfaced rather than retried in a loop, because a retry against an API with no unregister action is how somebody gets registered twice.
Keeping the invitation honest about what the session is
A campaign is being built to promote a session, and the copy has not been written yet. Before anything is sent, the agent calls Get Webinar Registration Information for the short ID the campaign will point at, and reads the type. It returns the title, the type, the duration and the upcoming times to the campaign owner in Slack, and where the type is automated or replay it says so in those words. The copywriter then writes an invitation that describes what the attendee will actually get. The agent also re-reads the upcoming times immediately before each send, because a schedule configured six weeks ago and a schedule today are not always the same list, and a campaign quoting a session time that no longer exists produces a registration failure at exactly the moment the audience is paying attention.
Human-in-Loop Highlight
Register Attendee is the gate, and it is a gate for two reasons that compound. The first is the type field. Get Webinar Registration Information returns whether a webinar is automated, replay, live or hybrid, which means the connector can tell you, before it registers anybody, that the session your email describes as live is a recording playing on a schedule. Registering a segment into an automated session under copy that promises a live speaker is a claim about your own event that the agent will make at volume and cannot walk back, because the confirmation email leaves StealthSeminar the moment the call succeeds and this connector exposes no action to unregister anyone. The second reason is the address. StealthSeminar's registration endpoints are public and a webinar is identified only by a short ID of up to six characters, so possession of that code is the entire authorization. There is no account credential scoping the call to your own webinars. A transposed character in a campaign configuration does not produce an authentication error, it produces a successful registration of your customers into a stranger's webinar, complete with a confirmation email from a company they have never heard of, and no read action in this connector will ever tell you it happened. So the first run of any new campaign stops before it reaches an audience. The agent posts to the campaign owner: "Short ID k7v2qp resolves to 'The 20 Minute Close', type: automated, duration 47 minutes, timezone America/Chicago, next upcoming times 14 May 11:00, 14 May 15:00, 15 May 11:00. The invitation copy for this campaign says 'join me live on Thursday'. Registering 840 contacts against the 15 May 11:00 session will send each of them a confirmation for an automated session, and there is no unregister action here. Confirm this is the right webinar and the right session, and either approve the copy as it stands or send me the corrected version first." A person confirms the short ID, the type and the wording once, and the segment goes. That is the human-in-the-loop moment in webinar operations: an agent can read exactly what a session is, and only a person can decide whether the invitation tells the truth about it.
Agent Capabilities
2 actionsWebinars
1- Get Webinar Registration Information Returns a webinar's public registration detail by its short ID, the code of up to six characters taken from its registration page URL. Returns the title, the type (automated, replay, live or hybrid), the timezone, the duration, the registration page and tracking configuration, and the list of upcoming session times available for registration. The type is what lets a flow keep an invitation honest about whether the session is a recording, and the upcoming times are the only valid values for the start time on a registration.
Registrants
1- Register Attendee Registers a new attendee for a webinar identified by its short ID. Requires the attendee's email and a start time that exactly matches one of the upcoming session times returned by Get Webinar Registration Information. Optionally captures the name, SMS number, timezone, GDPR consent, custom registration fields and link and UTM parameters, so attribution travels with the registration rather than being reconstructed afterwards. Returns the created registration including the attendee record and any auto login details. This connector exposes no action to list, retrieve or remove a registration afterwards, so the response is the only record of it a flow will get, and there is no undo.
Frequently Asked Questions
What can FlowRunner do with StealthSeminar?
FlowRunner agents can run Get Webinar Registration Information and Register Attendee in StealthSeminar.
Does connecting StealthSeminar to FlowRunner require OAuth?
No. StealthSeminar needs no credentials at all, so there is no key to obtain, store, or rotate.
Can StealthSeminar trigger a FlowRunner workflow automatically?
StealthSeminar doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with StealthSeminar
$100 in credits. No card required. Connect in minutes.