Skip to content
Tableau logoSessions.us logo

Connect Tableau to Sessions.us

Move data between Tableau 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.

Tableau triggers
9
Tableau actions
5
Sessions.us triggers
13
Sessions.us actions
4

Automation ideas

What you can build with Tableau and Sessions.us

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

  • Workbook Event in Tableau creates Create Session in Sessions.us

    Triggers when a workbook event occurs (created, updated, or deleted)

  • Booking Created in Sessions.us creates Download View in Tableau

    Triggered when a new booking is created.

  • Workbook Event in Tableau creates Create Event in Sessions.us

    Triggers when a workbook event occurs (created, updated, or deleted)

  • Booking Created in Sessions.us creates Run Extract Refresh Task in Tableau

    Triggered when a new booking is created.

  • Workbook Event in Tableau creates Publish Event in Sessions.us

    Triggers when a workbook event occurs (created, updated, or deleted)

  • Booking Created in Sessions.us creates Refresh Workbook in Tableau

    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 Tableau 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.