Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Sessions.us

Video conferencing platform for businesses and professionals

CategoryBusiness Intelligence
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Sessions.us with Flows360

Video conferencing platform for businesses and professionals

Use the Sessions.us connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 13 triggers.

Available actions

  • Create Session
  • Create Event
  • Publish Event
  • Custom API Call

Available triggers

  • Booking Created
  • Booking Started
  • Booking Ended
  • Event Created
  • Event Published
  • Event Started
  • Plus 7 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Sessions.us
  • Package: @activepieces/piece-sessions-us@0.2.0
  • Exact artifact digest: sha256:3ac91b2fc6405c5500309bd03247b8264d99392533133f245e1083ea2999979c
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Session (create_session), Quickly create a session. Classification: read.
  • Create Event (create_event), Quickly create an event. Classification: read.
  • Publish Event (publish_event), Quickly publish an event. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Booking Created, webhook.
  • Booking Started, webhook.
  • Booking Ended, webhook.
  • Event Created, webhook.
  • Event Published, webhook.
  • Event Started, webhook.
  • Event Ended, webhook.
  • Event New Registration, webhook.
  • Session Created, webhook.
  • Session Started, webhook.
  • Session Ended, webhook.
  • Takeaway Ready, webhook.
  • Transcript Ready, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects17
Supported actions4
Triggers13

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Session Yes No Quickly create a session.
Create Event Yes No Quickly create an event.
Publish Event Yes No Quickly publish an event.
Custom API Call Yes No Make a custom API call to a specific endpoint
Booking Created Yes No webhook trigger declared by the pinned package.
Booking Started Yes No webhook trigger declared by the pinned package.
Booking Ended Yes No webhook trigger declared by the pinned package.
Event Created Yes No webhook trigger declared by the pinned package.
Event Published Yes No webhook trigger declared by the pinned package.
Event Started Yes No webhook trigger declared by the pinned package.
Event Ended Yes No webhook trigger declared by the pinned package.
Event New Registration Yes No webhook trigger declared by the pinned package.
Session Created Yes No webhook trigger declared by the pinned package.
Session Started Yes No webhook trigger declared by the pinned package.
Session Ended Yes No webhook trigger declared by the pinned package.
Takeaway Ready Yes No webhook trigger declared by the pinned package.
Transcript Ready Yes No webhook trigger declared by the pinned package.

Supported actions

Create Session · Read

Quickly create a session.

create_session · Risk: low · Retry: safe

Inputs

  • name · string · Required, The name of the session
  • startAt · string · Required, Select a date and time
  • plannedEnd · string · Required, Select a date and time
  • timezone · string · Required, The timezone which the session will take place.
Create Event · Read

Quickly create an event.

create_event · Risk: low · Retry: safe

Inputs

  • name · string · Required, The name of the event
  • startAt · string · Required, Select a date and time
  • plannedEnd · string · Required, Select a date and time
  • timezone · string · Required, The timezone which the session will take place.
Publish Event · Read

Quickly publish an event.

publish_event · Risk: low · Retry: safe

Inputs

  • event · string · Required, The event you want to publish.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Booking Created · Webhook

Triggered when a new booking is created.

Inputs

  • permission · string
Booking Started · Webhook

Triggered when a booking starts.

Inputs

  • permission · string
Booking Ended · Webhook

Triggered when a booking ends.

Inputs

  • permission · string
Event Created · Webhook

Triggered when a new event is created.

Inputs

  • permission · string
Event Published · Webhook

Triggered when an event is published.

Inputs

  • permission · string
Event Started · Webhook

Triggered when an event starts.

Inputs

  • permission · string
Event Ended · Webhook

Triggered when an event ends.

Inputs

  • permission · string
Event New Registration · Webhook

Triggered when a new registration for an event occurs.

Inputs

  • permission · string
Session Created · Webhook

Triggered when a new session is created.

Inputs

  • permission · string
Session Started · Webhook

Triggered when a session starts.

Inputs

  • permission · string
Session Ended · Webhook

Triggered when a session has ended.

Inputs

  • permission · string
Takeaway Ready · Webhook

Triggered when a takeaway becomes available.

Inputs

  • permission · string
Transcript Ready · Webhook

Triggered when a session has ended.

Inputs

  • permission · string

Setup

Setup

  1. Add the Sessions.us connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-sessions-us@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 13 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Sessions.us connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-sessions-us@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com