CMS integration

Drupal + Sequel

Sync Sequel events into Drupal as content nodes and embed webinar experiences directly into the pages your team already manages.

Get a demo

Read the setup guide

Your Drupal site runs the page. Sequel runs the webinar.

Drupal gives your team full control over content, UX, and page structure. Sequel brings the webinar into that same structure — embedded on your own pages, registered through your own forms, and kept in sync as a Drupal content type — so your event platform and your CMS work as connected parts of one website instead of two separate systems.

Every webinar in Sequel carries a Sequel Event ID, and that single identifier is what both systems share. It renders the webinar through the embed, registers users through the Sequel API, and keeps webinar data flowing into Drupal.

What you can do

Drupal and Sequel, connected

Embed webinars on any Drupal page
Register with your form or ours
Sync events into Drupal automatically

One template renders every webinar

Add a plain text field for the Sequel Event ID to your webinar content type, then add the Sequel embed to that content type's Twig template and pass the field into it — {{ node.field_sequel_event_id.value }} — instead of hardcoding the ID. One template can then render any webinar on your site.

From then on, publishing a webinar is a content task. Editors paste the Event ID into the field and Sequel renders the experience — no template change, and no new implementation for every event.

Choose how people register

There are two ways to handle registration. Both end with the full Sequel experience on your page — the choice only affects who renders the form.

Sequel's embed handles everything — Add the embed to your Drupal webinar page and it runs the whole lifecycle in the same place: the registration form before the event, the live webinar at event time, and the on-demand replay afterwards. No registration API integration is required, and registrant data stays available in Sequel and through Sequel's integrations.
Your own form, from any provider — Keep the form you already use: Marketo, HubSpot, Pardot, Eloqua, a Drupal webform, or something fully custom. The registration reaches Sequel either server-side, where your backend or marketing automation posts to the Sequel registration API, or client-side through Sequel's form-integration script. Sequel detects the successful registration, replaces the form, and renders the webinar inline.

Use your own form when registration needs to reach your CRM or marketing automation first, enforce your own validation, or match a design you already have. Otherwise the Sequel embed is the fastest path.

Keep Drupal in sync automatically

Webinar pages don't have to be built by hand. Sequel can create, update, and unpublish Drupal nodes as events change in Sequel, so your site reflects what your team has scheduled without anyone copying details between two systems. There are two routes, depending on how much you want to own.

Sequel-managed sync — Sequel operates the sync service and calls your Drupal JSON:API directly, so your team builds no webhook receivers and no sync logic of its own.
Zapier — Prefer to wire it yourself? Trigger on Sequel events being created, updated, or deleted, map the fields to your webinar content type, and let Zapier create, find, and update the matching Drupal node. No code required.

What happens in Drupal when an event changes in Sequel:

Event created: Create a webinar node, storing the Sequel Event ID
Event updated: Find the node by Event ID and update the mapped fields
Event deleted: Delete or unpublish the node (unpublish recommended)

Field mapping

Sequel works with Drupal's core JSON:API module, or with a custom endpoint your team provides. During onboarding, both teams agree how Sequel event fields map to your webinar content type.

A typical mapping

Event ID: field_sequel_event_id — required, and the lookup key for every sync
Title: Title
Description: Body or description field
Start and end time: Date fields
Cover image: Banner or image field

Custom CMS metadata fields can be included — share the machine names and the defaults you want.

Security and access

Sequel authenticates to your Drupal API with HTTP Basic Authentication, using Drupal's core module over HTTPS only. Your team creates a dedicated integration user — never a personal account — with the minimum permissions the sync needs: create, edit, and delete or unpublish webinar content.

Credentials are shared through a secure channel, stored encrypted in Sequel's secrets vault, and never logged or exposed.

Also connects with