Skip to content
Sessions.us logoTableau logo

Connect Sessions.us to Tableau

Move data between Sessions.us and Tableau 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
Tableau triggers
9
Tableau actions
5

Automation ideas

What you can build with Sessions.us and Tableau

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

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

    Triggered when a new booking is created.

  • 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 Run Extract Refresh Task 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 Refresh Workbook 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)

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