Skip to content
Apify logoSessions.us logo

Connect Apify to Sessions.us

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

Apify triggers
2
Apify actions
6
Sessions.us triggers
13
Sessions.us actions
4

Automation ideas

What you can build with Apify and Sessions.us

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

  • Watch Actor Runs in Apify creates Create Session in Sessions.us

    Triggers a Flow on Apify Actor run events

  • Booking Created in Sessions.us creates Get Dataset Items in Apify

    Triggered when a new booking is created.

  • Watch Actor Runs in Apify creates Create Event in Sessions.us

    Triggers a Flow on Apify Actor run events

  • Booking Created in Sessions.us creates Run Actor in Apify

    Triggered when a new booking is created.

  • Watch Actor Runs in Apify creates Publish Event in Sessions.us

    Triggers a Flow on Apify Actor run events

  • Booking Created in Sessions.us creates Run Task in Apify

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