Demio n8n integrationAutomate Demio with n8n.
A webinar seat should never depend on someone copying an email address by hand. The Demio n8n integration exposes 4 operations across 2 resources, events and reports, so a workflow can register people, read the schedule and measure who actually showed up.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Demio n8n integration give you?
It connects your Demio webinars to everything else you run, without a browser tab. n8n ships a Demio node with 4 operations spread over 2 resources: events, which you read and register people to, and reports, which tell you what happened during a session. Each operation is a step in a workflow, so registration and follow up stop being manual chores.
Start with the case that hurts the most, registration. A signup form drops a row in Google Sheets, a Schedule Trigger reads the new rows on a fixed interval, and event.register pushes each person into the right session. First Name and Email are the only required fields, so even a two question form carries enough to work.
The second case sits at the other end of the session. Once a webinar is over, report.get returns the participation data for one session, and the Status filter sorts the room: people who attended, people who left early, people who never joined. Send the first group a thank you through SendGrid and the last group a replay link through Gmail, in the same run.
The third one is quieter and saves a surprising amount of back and forth. event.getAll with the Type filter on upcoming returns the sessions still ahead, which is all you need to post the week's schedule into Slack every Monday morning so nobody asks when the next one runs.
The node covers the operations in the catalogue. Anything that sits outside that list goes through the HTTP Request node, which calls any endpoint of the Demio API and reuses the very same credential through its predefined authentication, so you stay in one workflow instead of two tools.
Two practical notes before you build. Get Many stops at Limit unless Return All is switched on, which is the classic reason a list looks short. And Demio has no trigger node in n8n, so the starting point is yours to pick: a Schedule Trigger on a fixed interval, an n8n Webhook called by another service, or the trigger of a different tool. The n8n review walks through that choice, and the n8n training goes deeper on expressions.
How do you connect Demio to n8n?
- 01
Generate the API key in Demio
Open Account Settings, then the API section, and generate a pair. Demio gives you an API Key and an API Secret, and both are needed. This screen is reserved to accounts with Owner status, so if the API entry is missing, the account you are logged into is not the owner of the workspace.
- 02
Create the Demio credential in n8n
In n8n, go to the Credentials menu and create a Demio credential, the stored login that workflows reuse. Paste the API Key and the API Secret into their fields and save. A credential is created once and shows up in every workflow afterwards, so you never retype these values.
- 03
Add the node and pick an operation
Drop a Demio node into the canvas and select the credential from its dropdown list. Choose the Resource first, Event or Report, then the operation. The parameters below change with that choice, which is why the node asks for an Event ID in one case and a Session Name or ID in another.
What can the Demio node do?
The Demio node exposes 4 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Event
3 operationsGet an event
event.getWhat you see in n8n
Notes & use cases
Pulls one event with the dates attached to it, so a workflow can check a session before it sends anything to a registrant.
Key parameters
- Event ID: the Demio identifier of the event, required, usually passed from an earlier node as
{{ $json.field }}. - Active: in Additional Fields, returns only the active dates of a series instead of everything ever scheduled.
- Session ID: in Additional Fields, points at one event date rather than the whole series.
Get many events
event.getAllWhat you see in n8n
Notes & use cases
Lists the events of the account, which is how a workflow discovers what exists instead of carrying identifiers written by hand in a text field.
Key parameters
- Return All: on, n8n follows the API pages and brings back every event; off, it stops at Limit.
- Limit: the maximum number of events returned when Return All stays off.
- Type: in Filters, keeps only automated, past or upcoming events, which is the fastest way to build a schedule.
Register an event
event.registerWhat you see in n8n
Notes & use cases
Adds a person to an event, and to one precise date when a session is given. It turns a form answer into a confirmed seat.
Key parameters
- First Name and Email: both required, usually mapped from the incoming item as
{{ $json.field }}. - Event Name or ID: picked from the list, or set with an expression when the event varies per run.
- Custom Fields: in Additional Fields, key/value pairs beyond the predefined Company, Phone Number or Website fields.
Report
1 operationGet a report
report.getWhat you see in n8n
Notes & use cases
Brings back the participation report of a single session, which is where attendance stops being a feeling and becomes data you can route.
Key parameters
- Session Name or ID: the session the report belongs to, required, chosen from the list or set with an expression.
- Event Name or ID: optional, chosen from the list or set with an expression when the event varies per run.
- Status: in Filters, keeps only attended, completed, left-early, did-not-attend or banned participants.
Need help automating Demio with n8n?
A person reads every message.
