Skip to content
Omni logoSessions.us logo

Connect Omni to Sessions.us

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

Omni triggers
0
Omni actions
9
Sessions.us triggers
13
Sessions.us actions
4

Automation ideas

What you can build with Omni and Sessions.us

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

  • Booking Created in Sessions.us creates Create a document in Omni

    Triggered when a new booking is created.

  • Booking Created in Sessions.us creates Create a schedule in Omni

    Triggered when a new booking is created.

  • Booking Created in Sessions.us creates Delete a document in Omni

    Triggered when a new booking is created.

  • Booking Started in Sessions.us creates Create a document in Omni

    Triggered when a booking starts.

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