Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

SimplyBook.me

SimplyBook.me integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect SimplyBook.me with Flows360

SimplyBook.me integration for Flows360 workflows.

Use the SimplyBook.me 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 10 actions and 6 triggers.

Available actions

  • Create Booking
  • Set Booking Comment
  • Add Client
  • Create Note
  • Create Detailed Report
  • Cancel Booking
  • Delete Client
  • Get Bookings
  • Plus 2 additional declared actions.

Available triggers

  • New Booking
  • Booking Change
  • Booking Cancellation
  • New Client
  • New Invoice
  • New Offer

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: SimplyBook.me
  • Package: @activepieces/piece-simplybookme@0.1.6
  • Exact artifact digest: sha256:7288e17143628e9af13733863063afa9cd0bd6739870181e2e11b835b9c39b6c
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. 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 Booking (create_booking), Create a new booking using the book API method. Returns appointment info or throws exception if time not available. Classification: read.
  • Set Booking Comment (create_booking_comment), Set a comment for a booking Classification: read.
  • Add Client (create_client), Add a new client with specified data. Email, phone, or both may be required (check company settings). Classification: read.
  • Create Note (create_note), Create a note (generic) in the system Classification: read.
  • Create Detailed Report (create_detailed_report), Generate a detailed report (metrics, bookings, revenue) Classification: read.
  • Cancel Booking (cancel_booking), Cancel an existing booking. Returns true on success. Classification: read.
  • Delete Client (delete_client), Delete an existing client Classification: read.
  • Get Bookings (find_booking), Returns list of bookings filtered by given parameters Classification: read.
  • Get Client List (find_client), Returns list of clients associated with company. Search by phone number, email address, or name. Classification: read.
  • Find Invoice (find_invoice), Find invoices with filters and pagination Classification: read.

Trigger contracts

  • New Booking, webhook.
  • Booking Change, webhook.
  • Booking Cancellation, webhook.
  • New Client, polling.
  • New Invoice, polling.
  • New Offer, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects16
Supported actionsNot published
Triggers6

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Company Login Required
  • User Login Required
  • User Password Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Booking Yes No Create a new booking using the book API method. Returns appointment info or throws exception if time not available.
Set Booking Comment Yes No Set a comment for a booking
Add Client Yes No Add a new client with specified data. Email, phone, or both may be required (check company settings).
Create Note Yes No Create a note (generic) in the system
Create Detailed Report Yes No Generate a detailed report (metrics, bookings, revenue)
Cancel Booking Yes No Cancel an existing booking. Returns true on success.
Delete Client Yes No Delete an existing client
Get Bookings Yes No Returns list of bookings filtered by given parameters
Get Client List Yes No Returns list of clients associated with company. Search by phone number, email address, or name.
Find Invoice Yes No Find invoices with filters and pagination
New Booking Yes No webhook trigger declared by the pinned package.
Booking Change Yes No webhook trigger declared by the pinned package.
Booking Cancellation Yes No webhook trigger declared by the pinned package.
New Client Yes No polling trigger declared by the pinned package.
New Invoice Yes No polling trigger declared by the pinned package.
New Offer Yes No polling trigger declared by the pinned package.

Triggers

New Booking · Webhook

Triggers when a new booking is created in SimplyBook.me

Booking Change · Webhook

Triggers when a booking is changed in SimplyBook.me

Booking Cancellation · Webhook

Triggers when a booking is canceled in SimplyBook.me

New Client · Poll

Triggers when a new client is added (via booking or manually) in SimplyBook.me

New Invoice · Poll

Triggers when a new invoice is generated/paid in SimplyBook.me (requires Accept Payments feature)

New Offer · Poll

Triggers when a new offer (proposal or quote) is created (bookings with promo: false)

Setup

Setup

  1. Add the SimplyBook.me 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:
  • Company Login (companyLogin), required.
  • User Login (userLogin), required.
  • User Password (userPassword), required; stored as a sensitive connection value.
  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-simplybookme@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 actions and 6 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required SimplyBook.me 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-simplybookme@0.1.6 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