Skip to content
Sessions.us logoFormbricks logo

Connect Sessions.us to Formbricks

Move data between Sessions.us and Formbricks 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
Formbricks triggers
3
Formbricks actions
16

Automation ideas

What you can build with Sessions.us and Formbricks

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

  • Booking Created in Sessions.us creates List Surveys in Formbricks

    Triggered when a new booking is created.

  • Response Created in Formbricks creates Create Session in Sessions.us

    Triggers when someone starts answering a survey (a new response is created).

  • Booking Created in Sessions.us creates Get Survey in Formbricks

    Triggered when a new booking is created.

  • Response Created in Formbricks creates Create Event in Sessions.us

    Triggers when someone starts answering a survey (a new response is created).

  • Booking Created in Sessions.us creates Update Survey Status in Formbricks

    Triggered when a new booking is created.

  • Response Created in Formbricks creates Publish Event in Sessions.us

    Triggers when someone starts answering a survey (a new response is created).

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 Formbricks, 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.