Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Formitable

Restaurant reservation and guest management platform

CategorySales And Crm
Authenticationcustom
Version0.0.8
Published scopes0 published scopes
Last updatedSeptember 26, 2026

Overview

Connect Formitable with Flows360

Restaurant reservation and guest management platform

Use the Formitable 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 no declared actions and 16 triggers.

Available actions

  • No actions are declared in this pinned package.

Available triggers

  • Booking Created
  • Booking Accepted
  • Booking Changed
  • Guest Checked In
  • Guest Checked Out
  • Booking Canceled
  • Plus 10 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: Formitable
  • Package: @activepieces/piece-formitable@0.0.8
  • Exact artifact digest: sha256:13d04332228fd9be20def036a208c714a9bb70cf1c011ab4ae90d48dd5d1e2ef
  • 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

No actions are declared by this package version.

Trigger contracts

  • Booking Created, webhook.
  • Booking Accepted, webhook.
  • Booking Changed, webhook.
  • Guest Checked In, webhook.
  • Guest Checked Out, webhook.
  • Booking Canceled, webhook.
  • Booking Failed, webhook.
  • Booking Option Created, webhook.
  • Booking Option Accepted, webhook.
  • Booking Option Canceled, webhook.
  • Booking Option Expired, webhook.
  • Order Placed, webhook.
  • Message Sent by Customer, webhook.
  • Message Sent to Customer, webhook.
  • Review Created, webhook.
  • Review Request, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects16
Supported actionsNot published
Triggers16

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Booking Created Yes No webhook trigger declared by the pinned package.
Booking Accepted Yes No webhook trigger declared by the pinned package.
Booking Changed Yes No webhook trigger declared by the pinned package.
Guest Checked In Yes No webhook trigger declared by the pinned package.
Guest Checked Out Yes No webhook trigger declared by the pinned package.
Booking Canceled Yes No webhook trigger declared by the pinned package.
Booking Failed Yes No webhook trigger declared by the pinned package.
Booking Option Created Yes No webhook trigger declared by the pinned package.
Booking Option Accepted Yes No webhook trigger declared by the pinned package.
Booking Option Canceled Yes No webhook trigger declared by the pinned package.
Booking Option Expired Yes No webhook trigger declared by the pinned package.
Order Placed Yes No webhook trigger declared by the pinned package.
Message Sent by Customer Yes No webhook trigger declared by the pinned package.
Message Sent to Customer Yes No webhook trigger declared by the pinned package.
Review Created Yes No webhook trigger declared by the pinned package.
Review Request Yes No webhook trigger declared by the pinned package.

Triggers

Booking Created · Webhook

Triggers when a new booking is created.

Inputs

  • restaurant · string
Booking Accepted · Webhook

Triggers when a booking is accepted.

Inputs

  • restaurant · string
Booking Changed · Webhook

Triggers when a booking is updated.

Inputs

  • restaurant · string
Guest Checked In · Webhook

Triggers when a guest checks in at the restaurant.

Inputs

  • restaurant · string
Guest Checked Out · Webhook

Triggers when a guest checks out from the restaurant.

Inputs

  • restaurant · string
Booking Canceled · Webhook

Triggers when a booking is canceled.

Inputs

  • restaurant · string
Booking Failed · Webhook

Triggers when a booking fails.

Inputs

  • restaurant · string
Booking Option Created · Webhook

Triggers when a booking option is created.

Inputs

  • restaurant · string
Booking Option Accepted · Webhook

Triggers when a booking option is accepted. A booking.accepted event will also be fired.

Inputs

  • restaurant · string
Booking Option Canceled · Webhook

Triggers when a booking option is canceled.

Inputs

  • restaurant · string
Booking Option Expired · Webhook

Triggers when a booking option expires.

Inputs

  • restaurant · string
Order Placed · Webhook

Triggers when a takeaway order is made or a gift voucher is purchased.

Inputs

  • restaurant · string
Message Sent by Customer · Webhook

Triggers when a message is sent by the customer.

Inputs

  • restaurant · string
Message Sent to Customer · Webhook

Triggers when a message is sent by the restaurant to the customer.

Inputs

  • restaurant · string
Review Created · Webhook

Triggers when a review is created.

Inputs

  • restaurant · string
Review Request · Webhook

Triggers when a review request can be sent to the customer (typically 1 day after reservation).

Inputs

  • restaurant · string

Setup

Setup

  1. Add the Formitable 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-formitable@0.0.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 0 actions and 16 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 0 exercised action entrypoints and 16 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Formitable 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-formitable@0.0.8 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