Resources · n8n integration

GoToWebinar n8n integrationAutomate GoToWebinar with n8n.

Your webinar list and your CRM should not need a human to stay in sync. The GoToWebinar n8n integration opens 22 operations across 6 resources, from creating a webinar to reading poll answers. There is no GoToWebinar trigger node, so workflows start on a schedule or from another tool.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the GoToWebinar n8n integration actually cover?

The GoToWebinar node ships inside n8n and talks to the GoToWebinar API for you. It exposes 22 operations spread over 6 resources: webinars, sessions, registrants, attendees, panelists and co-organizers. Work you would otherwise click through by hand becomes a workflow that runs on a schedule or on demand.

Start with registration. A form on your site captures a lead, the workflow calls Create a registrant with the Webinar Key Name or ID of the next session, then writes the same person into Google Sheets so marketing works from one list instead of three exports.

Then look at what happens after the room empties. Get many sessions returns the sessions that ran, Get many attendees returns who actually showed up, and Get details of an attendee reads the polls, questions or surveyAnswers tied to that person. Push the short version into Slack and the sales team sees the engaged names the same morning.

The third pattern is the webinar itself. Create a webinar sets the Subject and the Time Range, Update a webinar changes the description or the timezone later, and the registrant list moves into Mautic for the follow-up sequence. One workflow, no copy and paste between two consoles.

The catalog draws a clear line. What sits outside these 22 operations goes through the HTTP Request node, which calls any endpoint of the GoToWebinar API while reusing the same credential through predefined authentication. That keeps one login for everything.

Two things are worth knowing before you build. Return All chains the pages of the API and brings back every registrant or attendee; switched off, Limit caps how many items come back. And an expression, n8n's way of injecting a value from an earlier node in the shape {{ $json.field }}, replaces the dropdown wherever the key is not known in advance. Our n8n review goes into the platform itself, and the n8n training covers building these workflows end to end.

Connect

How do you connect GoToWebinar to n8n?

  1. 01

    Open an OAuth client in the Developer Center

    Authentication runs on OAuth2, the only method this credential supports. You need a GoToWebinar account with access to the Developer Center, then you create an OAuth client there. The client hands you two values once it is fully set up: a Client ID and a Client Secret. Keep that page open, you come back to it in the next step.

  2. 02

    Copy the callback URL into the redirect field

    In n8n, open the Credentials menu and create a GoToWebinar credential. n8n displays an OAuth Callback URL. Copy that value and set it as the Redirect URI of the OAuth client you just created in the Developer Center. This is the address GoToWebinar sends the browser back to once you approve access.

  3. 03

    Finish the connection and reuse it everywhere

    Paste the Client ID and the Client Secret into the n8n credential and run the OAuth connection. A credential is created once in that menu and every workflow reuses it: add a GoToWebinar node, pick the credential from the dropdown, then choose a resource and an operation. No second login to manage.

Actions

What can the GoToWebinar node do?

The GoToWebinar node exposes 22 operations across 6 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDeleteGet DetailsReinvite
Attendee✓✓✓
Co-Organizer✓✓✓✓
Panelist✓✓✓✓
Registrant✓✓✓✓
Session✓✓✓
Webinar✓✓✓✓

Attendee

3 operations
01

Get an attendee

attendee.get

What you see in n8n

Notes & use cases

Pulls back one attendee record, scoped to a single session of a single webinar.

Key parameters

  • Webinar Key Name or ID: the key of the webinar the attendee attended. Pick it from the list n8n loads, or write an expression when the key comes from an earlier node.
  • Session Key Name or ID: the key of the session attended, same list or expression choice.
  • Registrant Key: the registrant key of that attendee at the webinar session.
Use cases
a sales rep asks whether a named account sat through last Tuesday's demo, and the workflow answers without anyone opening the console.
02

Get many attendees

attendee.getAll

What you see in n8n

Notes & use cases

Lists everyone who attended one session, as one item per person for the rest of the workflow to loop over.

Key parameters

  • Webinar Key Name or ID: the webinar the attendees attended, from the list or from an expression.
  • Session Key Name or ID: the session they attended. A recurring webinar has several sessions, so this is what separates last month's room from this month's.
  • Return All: on, the node chains the API pages and returns every attendee. Off, Limit sets the maximum number returned.
Use cases
building the attended list that feeds a thank-you email and leaves the no-shows for a separate sequence.
03

Get details of an attendee

attendee.getDetails

What you see in n8n

Notes & use cases

Digs into what one attendee did during the session rather than the fact that they were there.

Key parameters

  • Webinar Key Name or ID and Session Key Name or ID: the webinar and the session, from the dropdown or an expression.
  • Registrant Key: the registrant key of the attendee at that session.
  • Details: pick one of polls for the poll answers, questions for the questions asked, or surveyAnswers for the survey answers.
Use cases
reading the poll answers of every attendee to score intent, so the follow-up matches what they said in the room.

Co-Organizer

4 operations
04

Create a coorganizer

coorganizer.create

What you see in n8n

Notes & use cases

Adds a co-organizer to a webinar so someone else can run it with you.

Key parameters

  • Webinar Key Name or ID: the webinar the co-organizer is hosting.
  • Is External: whether the co-organizer has no GoToWebinar account. It decides which of the fields below the node expects.
  • Organizer Key: the co-organizer's organizer key for the webinar.
  • Given Name and Email: the co-organizer's given name and email address.
Use cases
a partner agency co-hosts your quarterly session and gets added automatically when the webinar is created.
05

Delete a coorganizer

coorganizer.delete

What you see in n8n

Notes & use cases

Removes a co-organizer from a webinar.

Key parameters

  • Webinar Key Name or ID: the key of the webinar concerned.
  • Is External: by default only internal co-organizers, the ones with a GoToWebinar account, can be deleted. Set it to true to use this call for external co-organizers.
  • Co-Organizer Key: the key of the co-organizer to delete.
Use cases
an offboarding workflow clears a departing colleague from every upcoming session in one run.
06

Get many coorganizers

coorganizer.getAll

What you see in n8n

Notes & use cases

Returns the co-organizers attached to one webinar.

Key parameters

  • Webinar Key Name or ID: the webinar to retrieve all co-organizers from, chosen from the list or given as an expression.
  • Return All: on, every co-organizer comes back. Off, Limit sets the ceiling.
Use cases
an audit workflow runs weekly and flags any webinar whose co-organizer list no longer matches the team roster.
07

Reinvite a coorganizer

coorganizer.reinvite

What you see in n8n

Notes & use cases

Sends a co-organizer's invitation again for a given webinar.

Key parameters

  • Webinar Key: the webinar concerned. On this operation the field is a plain text key rather than a dropdown, so an expression fits naturally.
  • Is External: whether the co-organizer has no GoToWebinar account.
  • Co-Organizer Key: the key of the co-organizer to reinvite.
Use cases
the day before a big session, a workflow reinvites every co-organizer so nobody hunts through an old inbox.

Panelist

4 operations
08

Create a panelist

panelist.create

What you see in n8n

Notes & use cases

Registers a speaker as a panelist on a webinar.

Key parameters

  • Name: the name of the panelist to create.
  • Email: the panelist's email address, in the name@email.com shape the field suggests.
  • Webinar Key Name or ID: the webinar the panelist will present at, from the list or an expression.
Use cases
a guest speaker confirms in a shared sheet and the workflow adds them as a panelist on the right session, without a second form to fill.
09

Delete a panelist

panelist.delete

What you see in n8n

Notes & use cases

Drops a panelist from a webinar.

Key parameters

  • Webinar Key Name or ID: the webinar to delete the panelist from.
  • Panelist Key: the key of the panelist to delete. This is the key, not the speaker's name, so fetch it first if all you hold is a label.
Use cases
a speaker cancels two days out and the workflow clears them from the lineup as soon as the cancellation lands.
10

Get many panelists

panelist.getAll

What you see in n8n

Notes & use cases

Walks through the panelists attached to one webinar.

Key parameters

  • Webinar Key Name or ID: the webinar to retrieve all panelists from.
  • Return All: on, the node pages through the API and returns the full lineup. Off, Limit decides how many panelists come back.
Use cases
generating the speaker block of a landing page straight from the panelists recorded in GoToWebinar, so the page never drifts from reality.
11

Reinvite a panelist

panelist.reinvite

What you see in n8n

Notes & use cases

Issues the panelist invitation again for a webinar.

Key parameters

  • Webinar Key Name or ID: the webinar to reinvite the panelist to.
  • Panelist Key: the key of the panelist to reinvite, which you can read from Get many panelists in the step before.
Use cases
a rehearsal workflow reinvites the whole panel the morning of the session, chained after the operation that lists them.

Registrant

4 operations
12

Create a registrant

registrant.create

What you see in n8n

Notes & use cases

Signs someone up for a webinar from outside GoToWebinar, which is the operation most funnels revolve around.

Key parameters

  • Webinar Key Name or ID: the webinar of the registrant to create. This is the only field the node marks as required, so it is the one that blocks execution when empty.
  • First Name, Last Name and Email: the registrant's identity, listed outside the required block.
  • Additional Fields: 13 more, including Organization, Job Title, Industry, Source for what led to the registration, and Questions and Comments for what the person wrote during registration.
Use cases
your own landing page keeps the design and the tracking, and the workflow registers each lead behind the scenes.
13

Delete a registrant

registrant.delete

What you see in n8n

Notes & use cases

Cancels a registration on a given webinar.

Key parameters

  • Webinar Key Name or ID: the webinar of the registrant to delete.
  • Registrant Key: the key of the registrant to delete, which Get many registrants or Get a registrant gives you upstream.
Use cases
a deletion request arrives in your privacy inbox and the workflow removes the person from the upcoming session instead of leaving it on a checklist.
14

Get a registrant

registrant.get

What you see in n8n

Notes & use cases

Fetches one registration record, before the webinar has even run.

Key parameters

  • Webinar Key Name or ID: the webinar of the registrant to retrieve.
  • Registrant Key: the key of the registrant to retrieve. It is a key, not an email address, so pair it with the list operation when you only hold contact details.
Use cases
a support agent pastes a registrant key into a chat command and gets the registration back in the thread.
15

Get many registrants

registrant.getAll

What you see in n8n

Notes & use cases

Goes through the sign-up list of one webinar, one item per registrant.

Key parameters

  • Webinar Key Name or ID: the key of the webinar to retrieve registrants from.
  • Return All: on for a full export, because the node then chains the API pages by itself. Off, Limit sets how many registrants the node returns.
Use cases
a nightly sync mirrors the registrant list into your CRM so nobody rebuilds it from a downloaded file on the morning of the session.

Session

3 operations
16

Get a session

session.get

What you see in n8n

Notes & use cases

Reads one session of a webinar, the actual occurrence rather than the webinar shell.

Key parameters

  • Webinar Key Name or ID: the webinar the session belongs to, from the list or an expression.
  • Session Key: the session itself, typed as plain text on this operation.
Use cases
a reporting workflow that already carries a session key resolves it back to the session before writing anything into the dashboard.
17

Get many sessions

session.getAll

What you see in n8n

Notes & use cases

Sweeps the sessions across your account, with no webinar required up front.

Key parameters

  • Return All: on, every session comes back. Off, Limit caps the number returned.
  • Additional Fields: Time Range, required inside that collection, frames the window you are asking for; Webinar Key Name or ID narrows the sessions to a single webinar.
Use cases
a Monday report lists every session that ran in the past week, whichever webinar it belonged to.
18

Get details on a session

session.getDetails

What you see in n8n

Notes & use cases

Opens up what came out of a session instead of its schedule.

Key parameters

  • Webinar Key Name or ID and Session Key: the webinar and the session to read.
  • Details: performance for performance details, polls for poll questions and answers, questions for the questions and answers of a past session, or surveys for its surveys.
Use cases
collecting the survey results of each past session in one place, so the next agenda is built on what people asked rather than on a hunch.

Webinar

4 operations
19

Create a webinar

webinar.create

What you see in n8n

Notes & use cases

Schedules a new webinar from a workflow, so the calendar entry and the GoToWebinar event come from the same source.

Key parameters

  • Subject: required, the name of the webinar.
  • Time Range: required, and inside it Start Time and End Time are required too.
  • Additional Fields: Description, Timezone Name or ID, Is On-Demand, Is Password Protected, Experience Type (CLASSIC, BROADCAST, SIMULIVE) and Webinar Type: single_session for one meeting, series when attendees pick one of several times, sequence when the same people are expected at all sessions.
Use cases
a training program creates its whole term of sessions in one run.
20

Get a webinar

webinar.get

What you see in n8n

Notes & use cases

Retrieves a single webinar by its key.

Key parameters

  • Webinar Key: the key of the webinar to retrieve, typed as plain text here rather than picked from a list. That makes it the natural fit for a key carried by the previous node as an expression.
Use cases
a confirmation message needs the webinar details next to the registrant, and this operation supplies them right after the registration step.
21

Get many webinars

webinar.getAll

What you see in n8n

Notes & use cases

Scans the webinars in the account and hands them back one by one.

Key parameters

  • Return All: on, the node pages through everything. Off, Limit sets the maximum number of webinars returned.
  • Additional Fields: Time Range, required within that collection, defines the period the list covers.
Use cases
keeping a public schedule page in step with the account, refreshed on a Schedule Trigger rather than edited by hand.
22

Update a webinar

webinar.update

What you see in n8n

Notes & use cases

Edits a webinar that already exists, without recreating it and losing the registrations attached to it.

Key parameters

  • Webinar Key: required, the key of the webinar to update.
  • Notify Participants: a required boolean, so every call has to state it explicitly.
  • Update Fields: 8 optional fields, among them Subject for the name or topic, Description, Times, Timezone Name or ID, Is On-Demand for whether the webinar may be watched anytime, and Is Password Protected for whether attendees need a password to join.
Use cases
a speaker change rewrites the description on every affected session.
Need help

Need help automating GoToWebinar with n8n?

A person reads every message.

FAQ

GoToWebinar and n8n, the questions that come next

01Is the GoToWebinar n8n integration free?
On the n8n side, yes. The GoToWebinar node ships with n8n, so there is nothing to install and nothing extra to pay for the node itself. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves the same way in both places, which means you can prototype on one and run it on the other. What a GoToWebinar plan costs on its own is a separate question, and this page does not cover it. You will also need a GoToWebinar account with Developer Center access to create the OAuth client the credential relies on.
02What credentials do you need to connect GoToWebinar to n8n?
One OAuth2 credential, which is the only supported authentication method for this node. You start from a GoToWebinar account that has access to the Developer Center and create an OAuth client there. Two values come out of that client once it is finished: a Client ID and a Client Secret. In n8n you open the Credentials menu, create the GoToWebinar credential, and copy the OAuth Callback URL that n8n shows into the Redirect URI of your OAuth client. Then you paste the Client ID and Client Secret and run the connection. A credential is set up once and reused across every workflow, picked from the dropdown inside the node.
03What are the limits of the GoToWebinar node in n8n?
The node exposes 22 operations across 6 resources: webinars, sessions, registrants, attendees, panelists and co-organizers. Anything outside that catalog goes through the HTTP Request node, which calls any endpoint of the GoToWebinar API while reusing the same credential through predefined authentication, so you keep one login. On the listing operations, pagination is something you control: Return All chains the API pages and brings back the full set, while switching it off hands control to Limit, which sets the maximum number of items returned. And any field marked required stops the node from running when it is left empty.
04Can a workflow start from a GoToWebinar event?
Not from GoToWebinar itself. This tool has no trigger node in n8n, so a workflow about it starts somewhere else. Three routes cover almost every case. A Schedule Trigger runs the workflow at a fixed interval, which suits nightly registrant syncs or a post-session report. An n8n Webhook, meaning a URL n8n exposes and a third-party service calls, starts the run the moment a form is submitted or a payment clears. Or another tool's trigger opens the chain, and the GoToWebinar node comes second. In practice the pattern is the same: something else fires, the GoToWebinar operations follow.
05n8n or Make for GoToWebinar?
It comes down to four criteria, and neither tool wins all four. Hosting: n8n runs on your own server through Docker or npm, or on n8n Cloud; Make is hosted only, with no self-hosting option. Data control follows from that, since a self-hosted instance keeps webinar registrant data inside your own infrastructure. Cost model: Make bills per operation, which matters when you loop over a full attendee list every week. Visual logic: both draw the workflow on a canvas, and the choice there is mostly a matter of habit. If self-hosting and data control are not concerns for your team, the decision gets much closer.