Skip to content
Sessions.us logoAircall logo

Connect Sessions.us to Aircall

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

Automation ideas

What you can build with Sessions.us and Aircall

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

  • Booking Created in Sessions.us creates Comment a Call in Aircall

    Triggered when a new booking is created.

  • Call Ended in Aircall creates Create Session in Sessions.us

    Triggers when a call ends.

  • Booking Created in Sessions.us creates Create a Contact in Aircall

    Triggered when a new booking is created.

  • Call Ended in Aircall creates Create Event in Sessions.us

    Triggers when a call ends.

  • Booking Created in Sessions.us creates Find Call in Aircall

    Triggered when a new booking is created.

  • Call Ended in Aircall creates Publish Event in Sessions.us

    Triggers when a call ends.

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