Skip to content
Notis

Turn a clear WhatsApp yes into a confirmed booking

When a new request reaches your Notis webhook, have Notis check the 2chat conversation and confirm the matching pending Cal booking after an unambiguous approval.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Confirm booking by uid

Confirms an existing booking by `bookinguid` if the booking exists and is in a state allowing confirmation (e.g., not already cancelled or confirmed); this finalizes the booking, does not modify its details, and should typically be performed once.

Why this helps

A customer may approve a proposed time in chat, while the booking still waits for someone to find and confirm it in Cal.

  • Confirm bookings after clear customer approval.
  • Cut the handoff between chat review and Cal.
  • Avoid acting on ambiguous or unmatched conversations.

Setup

Build it in a few focused steps.

  • 1Connect 2chat and Cal once in the Notis portal.
  • 2Create an automation and name it for WhatsApp booking approval.
  • 3Tell Notis to inspect the relevant 2chat conversation, find the matching pending Cal booking, and confirm it only when the customer's approval and booking identity are clear.
  • 4Pick the Notis webhook trigger and choose where run reports should go.
  • 5Test with one real example, including an ambiguous approval, and check the run report.

Questions about this workflow

Does this trigger automatically fire from a 2chat event?

No 2chat trigger event is available here. The workflow starts when a request reaches the Notis webhook; the prompt can then use the connected 2chat and Cal context.

What if several bookings could match?

The instruction should require a clear match before confirming. Unclear cases should be reported for manual review.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link 2chat to Cal. A trigger fires from one place; an action lands in another.

2chat triggers

Cal actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add member to team

Adds a new member to a specified team within an organization by creating a team membership.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add organization attribute option

Adds a new option to an organization's attribute, requiring a display `value` and a `slug` unique for that attribute.

ActionInstant

Delete oauth client webhook

Permanently deletes a specific webhook subscription of an oauth client in the cal application, stopping its notifications.

ActionInstant

Cancel booking via uid

Cancels an existing and active cal.com booking using its unique identifier (uid).

ActionInstant

Check calendar availability

Retrieves free/busy availability for a specified calendar to aid scheduling without revealing event details; requires an existing, accessible calendar, noting that data granularity can vary.

ActionInstant

Check gcal synchronization status

Call this read-only action to verify the connection and synchronization status of a user's google calendar integration with cal.

ActionInstant

Check ics feed calendar endpoint

Checks an ics feed url (expected as a query parameter) to verify its validity, accessibility, and icalendar data integrity.

ActionInstant

Check Stripe status

Verifies if stripe is correctly connected to the cal scheduling system and functional for processing payments, reporting only on the integration's status.

ActionInstant

Connect any two apps with Notis in the middle.

2chat and Cal, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cal.