Automate Demio Webinar Registration with Typeform & n8n

Picture this: your webinar is in two hours, your Typeform is full of eager signups, and you are still copy-pasting email addresses into Demio like it is 2009. Your coffee is cold, your patience is gone, and one typo away from inviting “jonh.doe@gmial.com” instead of “john.doe@gmail.com”.

Or, you could let n8n quietly handle everything in the background, while you focus on your slides, your pitch, or your snack situation.

This guide walks you through a ready-to-use n8n workflow template that automatically registers Typeform respondents for a Demio webinar the moment they hit submit. Same data, zero manual imports, way fewer sighs.

Why bother automating webinar registration?

If you have ever exported a CSV from Typeform and imported it into Demio, you already know the answer. Manual registration is slow, boring, and surprisingly easy to mess up.

By connecting Typeform to Demio with n8n, you can:

• Save hours of repetitive copy-paste work
• Cut down on typos, duplicates, and missing attendees
• Give people instant confirmation instead of “we’ll add you later” vibes
• Scale your marketing campaigns without scaling your spreadsheet headaches

In short, the workflow turns “Ugh, I have to process these signups” into “Oh, that just happens now.”

What this n8n workflow template actually does

Under the hood, this is a simple two-node n8n workflow that quietly does a very useful job:

1. Typeform Trigger node
   This listens for new Typeform submissions via a webhook. Whenever someone completes your form, this node grabs their responses.
2. Demio node
   This takes the data from Typeform and calls the Demio API to register that person for a specific Demio event.

The flow is straightforward:

Typeform submission → Typeform Trigger fires → n8n sends data to Demio → Demio registers the attendee for your chosen event.

No files to download, no imports to run, no “Oops, I forgot to add yesterday’s signups.”

What you need before you start

Before you hit import on the JSON template, make sure you have:

• An n8n instance (cloud or self-hosted)
• A Typeform account with the form you want to use
• A Demio account with an existing event and its event ID
• API credentials:
  • Typeform: API token for webhook access
  • Demio: API key or token, depending on the Demio API version you use
• The n8n workflow template JSON (from the template link above)

Once you have those, you are ready to connect everything and retire your manual registration routine.

Inside the template: key fields to understand

You do not have to be a JSON whisperer to use this template, but it helps to know what the important bits do.

Typeform Trigger node

• webhookId: Unique ID that n8n uses to map the incoming webhook. You do not usually need to edit this manually.
• formId (optional): If you set this, the trigger will only fire for that specific Typeform. If you leave it blank, it can listen to any form, which is risky if you use multiple forms.
• credentials: This links the node to the Typeform credentials you create in n8n.

Demio node

• operation: register This tells n8n to register an attendee in Demio.
• eventId: The numeric ID of your Demio event. In the template, it is set to 357191 as an example. You will replace this with your actual event ID.
• email and firstName: These are mapped from Typeform responses using n8n expressions, for example:
  • {{$json["What's your email address?"]}}
  • {{$json["Let's start with your name."]}}

  You will update these expressions to match your exact question text.

• credentials: The Demio API credentials you store in n8n.

Once these are correctly wired, n8n moves data from Typeform to Demio automatically every time the form is submitted.

Quick setup guide: from template to working automation

Let us walk through the setup in a clean, no-drama sequence. You can do all of this inside the n8n editor.

Step 1: Import the workflow template into n8n

Open your n8n instance and:

• Go to the workflow editor
• Click the Import button
• Paste the JSON from the template

You should immediately see two nodes connected: Typeform Trigger and Demio. That is your basic automation skeleton.

Step 2: Set up Typeform credentials and webhook

Now connect the Typeform side so n8n can actually receive submissions.

• In n8n, open Credentials and click Create → choose Typeform.
• Add your Typeform API token and save.
• Open the Typeform Trigger node and select the Typeform credential you just created.
• If you are using one specific form, set the formId in the node so only that form triggers the workflow.
• If you leave formId blank, any form can fire the webhook, which is usually not ideal if you have multiple forms.
• Activate or start the workflow. n8n will create a webhook URL and automatically register it with Typeform for you.

At this point, Typeform knows where to send new responses, and n8n is listening.

Step 3: Configure Demio credentials in n8n

Next, connect Demio so n8n is allowed to register attendees on your behalf.

• In n8n, create new Demio credentials:
  • Use your Demio API key or token, depending on the API type you use.
• Open the Demio node in the workflow.
• Select your Demio credential in the credentials section.

Now n8n can talk to Demio securely without exposing tokens in your workflow.

Step 4: Map Typeform answers to Demio fields

This is where you tell n8n which Typeform answer should become which Demio field. The template already includes example expressions, but you will likely need to tweak them.

Example expressions from the template:

• email: {{$json["What's your email address?"]}}
• firstName: {{$json["Let's start with your name."]}}

To get this right for your form:

• Run a test submission in Typeform.
• Check the sample JSON in n8n from the Typeform Trigger node.
• Note the exact question text keys that appear in the JSON.
• Update the expressions in the Demio node to match those keys exactly.

Once mapped correctly, every new respondent will arrive in Demio with the right email and first name, instead of “undefined” or empty fields.

Step 5: Set your real Demio event ID

The template uses a placeholder event ID: 357191. You will replace that with your real event.

• In Demio, find your event ID:
  • It is usually visible in the event URL or in the event settings.
• Open the Demio node in n8n.
• Set the eventId field to your actual numeric ID.

From now on, every Typeform respondent will be registered for that specific Demio webinar.

Step 6: Test the workflow

Time to test that everything works before you trust it with real leads.

• Submit a test entry in your Typeform.
• In n8n, check that the Typeform Trigger node shows a successful execution.
• Look at the Demio node output:
  • If it succeeds, you should see a confirmation payload from Demio.
  • If it fails, n8n will show the response body, which can reveal issues like:
    • Invalid or expired API token
    • Missing required fields
    • Duplicate attendee errors

Once the test passes, you officially never have to manually register attendees for that event again.

Best practices so your automation behaves like a pro

Now that the workflow runs, a few small improvements can make it more robust and less fragile.

• Clean up email addresses Use a Function node before Demio to normalize email casing and remove sneaky spaces. Less chance of “email not valid” errors.
• Use a Set node to tidy fields Add a Set node before the Demio node to:
  • Rename fields
  • Provide default values when something is missing
  • Keep only the fields you actually need
• Handle temporary API issues gracefully Use n8n’s Retry options or error workflows so a short Demio or network hiccup does not permanently lose a registration.
• Respect GDPR and consent If you operate in regions with privacy regulations:
  • Capture consent in Typeform with a checkbox or explicit question.
  • Include that field in your workflow so you have a record of lawful basis for processing.
• Prevent duplicate attendees If Demio offers attendee lookup:
  • Call the lookup endpoint before registering.
  • Or handle 409 / duplicate responses gracefully by skipping or updating instead of failing the whole workflow.
• Log registrations elsewhere Want extra visibility?
  • Add another node after Demio to log successful registrations to Google Sheets, Airtable, or your CRM.

With these tweaks, your automation goes from “works most of the time” to “production ready and boringly reliable”. Which is exactly what you want from automation.

Advanced variations for power users

Once the basic “Typeform to Demio” flow is working, you can start getting fancy.

• Conditional registration Use a Switch node to only register people who explicitly opt in to the webinar. For example, check if a “Do you want to attend the webinar?” answer is “Yes” before sending them to Demio.
• Lead enrichment Add an extra HTTP Request node to call a service like Clearbit or your CRM and enrich the lead with company or industry data before registration.
• Delayed follow ups After a successful Demio registration, trigger:
  • A timed email sequence
  • A marketing automation flow in ActiveCampaign or HubSpot

  using their respective n8n nodes.

Same workflow, more value, without touching your CSV export button ever again.

Troubleshooting: when automation throws a tiny tantrum

If something does not work on the first try, here are common issues and how to fix them:

• Webhook not triggered
  • Check that the workflow is active in n8n.
  • Verify that Typeform has the webhook registered, or check the Typeform Trigger node log in n8n.
• Invalid field keys
  • Open a recent execution in n8n and inspect the JSON from the Typeform Trigger node.
  • Update your expressions in the Demio node to match the exact keys shown there.
• Authentication errors
  • Double check your API tokens for Typeform and Demio.
  • Confirm they have not expired and that they have the required permissions.
• Duplicate attendee error
  • Use a lookup step before registration if Demio supports it.
  • Or catch the error and handle it with conditional logic, such as skipping or updating the attendee instead of failing the run.

Security and compliance basics

Even when you are just trying to save yourself from spreadsheet duty, it is worth doing things securely.

• Store all API keys and tokens in n8n credentials, not hard coded in nodes.
• Avoid logging raw webhook payloads in public or shared logs, especially if they contain personal data.
• If you handle personal data:
  • Document what you collect, where it flows, and how long you keep it.
  • Make sure your Typeform and Demio settings align with your privacy policy.

Good security means you can enjoy automation without worrying about where your data is wandering off to.

Sample enhancement: clean data with a Function node

Want to tidy up names and emails before sending them to Demio? Drop a Function node between Typeform and Demio and use a small JavaScript snippet like this:

// Example Function node code (n8n)
const email = item.json["What's your email address?"]?.trim().toLowerCase();
const fullName = item.json["Let's start with your name."]?.trim();
return [{ json: { email, firstName: fullName } }];

This normalizes the email and trims the name, so Demio gets clean, predictable data every time.

Wrapping up: one less repetitive task on your plate

Connecting Typeform to Demio with n8n is a simple but powerful upgrade to your webinar workflow. The template already does most of the heavy lifting. You just:

• Import the JSON into n8n
• Plug in your Typeform and Demio credentials
• Map your question fields correctly