DEMIO n8n INTEGRATION: AUTOMATE DEMIO WITH N8N

This action retrieves participation and engagement reports for specific Demio events and sessions. Essential for post-webinar analysis and triggering follow-up sequences based on actual attendance.

Key parameters:

• Credential to connect with: Required dropdown for selecting your Demio API credentials.
• Resource: Pre-set to "Report," indicating you're working with reporting data.
• Operation: Set to "Get" to retrieve report information.
• Event Name or ID: An optional text field to specify which event's report you want to pull. Accepts dynamic expressions or static values.
• Session Name or ID: An optional text field for targeting a specific session within an event series, useful for recurring webinars.
• Filters: An expandable section where you can add filter criteria to refine the report data returned.

Use cases:

• Pull attendance data after each webinar to update contact records in your CRM with "attended" or "no-show" tags
• Trigger different email sequences based on whether registrants actually attended
• Generate weekly analytics reports by fetching session data and pushing it to your BI tool or spreadsheet

This action automatically registers a participant for a specified Demio event. It's the cornerstone action for building lead-to-webinar automation pipelines that eliminate manual data entry.

Key parameters:

• Credential to connect with: Required dropdown to select your authenticated Demio credentials.
• Resource: Set to "Event," indicating the registration pertains to webinar events.
• Operation: Configured as "Register" to add a participant to the specified event.
• Event Name or ID: A required field where you specify which event the participant should be registered for. Accepts either the event name or its unique ID.
• First Name: An optional text field for the participant's first name—can be static or dynamically mapped from previous nodes.
• Email: An optional text field for the participant's email address, which is typically required by Demio for registration.
• Additional Fields: Expandable section to include extra participant details like last name, company, or custom fields if supported.

Use cases:

• Auto-register new leads from Typeform submissions directly into your next webinar
• Trigger registration when a contact reaches a specific stage in your CRM pipeline
• Build a Zapier-style automation where purchasing a product automatically enrolls buyers in an onboarding webinar

This action fetches multiple event records from your Demio account in a single request. Perfect for dashboards, bulk operations, or when you need to work with your entire event catalog programmatically.

Key parameters:

• Credential to connect with: Required dropdown to select your Demio authentication credentials.
• Resource: Set to "Event" to indicate you're retrieving event-type data.
• Operation: Configured as "Get Many" to fetch multiple records simultaneously.
• Return All: A toggle switch that, when enabled, retrieves every available event without limitations. When disabled, the Limit parameter controls the maximum count.
• Limit: A numeric field (defaulting to 100) that caps how many events are returned when "Return All" is off.
• Filters: An expandable section where you can add criteria to narrow down which events are retrieved.

Use cases:

• Generate a weekly report of all upcoming webinars for your marketing calendar
• Sync your complete event list to Airtable or Google Sheets for team visibility
• Filter and retrieve only events from a specific date range for quarterly analysis

This action retrieves detailed information about a specific Demio event using its unique identifier. It's your go-to when you need to fetch current event settings, registration status, or scheduling details for use elsewhere in your workflow.

Key parameters:

• Credential to connect with: A required dropdown where you select your authenticated Demio account credentials to authorize the API request.
• Resource: Pre-set to "Event," indicating you're working with event data in Demio.
• Operation: Set to "Get," specifying that this action retrieves information rather than creating or modifying.
• Event ID: A required text field where you enter the specific event's identifier. This can be a static value or dynamically pulled from a previous node in your workflow.
• Additional Fields: An optional section for extended customization if supported by your use case.

Use cases:

• Pull event details to populate a confirmation email with webinar date, time, and join link
• Check event status before triggering registration workflows
• Fetch event metadata to sync with your Notion project management tool