Skip to content
PostHog logoSessions.us logo

Connect PostHog to Sessions.us

Move data between PostHog and Sessions.us 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.

PostHog triggers
1
PostHog actions
5
Sessions.us triggers
13
Sessions.us actions
4

Automation ideas

What you can build with PostHog and Sessions.us

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

  • New Event in PostHog creates Create Session in Sessions.us

    Triggers when a new event is captured in PostHog

  • Booking Created in Sessions.us creates Capture Event in PostHog

    Triggered when a new booking is created.

  • New Event in PostHog creates Create Event in Sessions.us

    Triggers when a new event is captured in PostHog

  • Booking Created in Sessions.us creates Create Project in PostHog

    Triggered when a new booking is created.

  • New Event in PostHog creates Publish Event in Sessions.us

    Triggers when a new event is captured in PostHog

  • Booking Created in Sessions.us creates Get Feature Flags in PostHog

    Triggered when a new booking 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 PostHog and acts in Sessions.us, 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.