Video conferencing platform for businesses and professionals
Sessions.us currently provides 13 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Booking Created
Triggered when a new booking is created.
Booking Started
Triggered when a booking starts.
Booking Ended
Triggered when a booking ends.
Event Created
Triggered when a new event is created.
Event Published
Triggered when an event is published.
Event Started
Triggered when an event starts.
Event Ended
Triggered when an event ends.
Event New Registration
Triggered when a new registration for an event occurs.
Session Created
Triggered when a new session is created.
Session Started
Triggered when a session starts.
Session Ended
Triggered when a session has ended.
Takeaway Ready
Triggered when a takeaway becomes available.
Transcript Ready
Triggered when a session has ended.
Create Session
Quickly create a session.
Create Event
Quickly create an event.
Publish Event
Quickly publish an event.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Sessions.us event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Booking Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Sessions.us action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Session
Combine Sessions.us with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
Booking Created
Finishes with
Create Session, then preserve the outcome in Coherence
The exact authentication fields depend on Sessions.us. The workflow structure stays straightforward:
Authorize the Sessions.us account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Sessions.us or provide a complementary trigger or action.
Sessions.us currently provides 13 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Sessions.us currently lists 13 triggers and 4 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Sessions.us triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
