Skip to content
Sessions.us logoDrupal logo

Connect Sessions.us to Drupal

Move data between Sessions.us and Drupal the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Sessions.us triggers
13
Sessions.us actions
4
Drupal triggers
3
Drupal actions
6

Automation ideas

What you can build with Sessions.us and Drupal

A few flows teams run between Sessions.us and Drupal. Use one as a starting point, or build your own from scratch.

  • Booking Created in Sessions.us creates Call Service in Drupal

    Triggered when a new booking is created.

  • Polling by ID in Drupal creates Create Session in Sessions.us

    A trigger that polls the Drupal site by ID.

  • Booking Created in Sessions.us creates Create Entity in Drupal

    Triggered when a new booking is created.

  • Polling by ID in Drupal creates Create Event in Sessions.us

    A trigger that polls the Drupal site by ID.

  • Booking Created in Sessions.us creates List Entities in Drupal

    Triggered when a new booking is created.

  • Polling by ID in Drupal creates Publish Event in Sessions.us

    A trigger that polls the Drupal site by ID.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Sessions.us and acts in Drupal, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.