Skip to content
IMAP logoSessions.us logo

Connect IMAP to Sessions.us

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

IMAP triggers
1
IMAP actions
4
Sessions.us triggers
13
Sessions.us actions
4

Automation ideas

What you can build with IMAP and Sessions.us

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

  • New Email in IMAP creates Create Session in Sessions.us

    Trigger when a new email is received

  • Booking Created in Sessions.us creates Mark Email as Read/Unread in IMAP

    Triggered when a new booking is created.

  • New Email in IMAP creates Create Event in Sessions.us

    Trigger when a new email is received

  • Booking Created in Sessions.us creates Copy Email in IMAP

    Triggered when a new booking is created.

  • New Email in IMAP creates Publish Event in Sessions.us

    Trigger when a new email is received

  • Booking Created in Sessions.us creates Move Email in IMAP

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