You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found a bug? Please fill out the sections below. 👍
Issue Summary
Cal.com - Teams paid plan user.
Workflows are enabled upon When new event is booked and Disable default confirmation emails for attendees is enabled.
I need to confirm the new events booked using /confirm API call, when I call the API, pending events are confirmed, but the workflow that is supposed to be triggered upon When new event is booked does not get triggered. Manual "Confirm" on the bookings page does trigger the workflow.
Steps to Reproduce
Create new event
Enable Request confirmation
Create webhook subscriber that will confirm the booking using its booking UID.
Enable When new event is booked workflow and enable Disable default confirmation emails for attendees
Book an event.
Event is confirmed via /confirm API
Actual Results
Actual result: no notification email is sent as set in the Workflow.
Expected Results
Expected: API confirmation of a booking should have triggered the workflow.
The text was updated successfully, but these errors were encountered:
Found a bug? Please fill out the sections below. 👍
Issue Summary
When new event is booked
andDisable default confirmation emails for attendees
is enabled.I need to confirm the new events booked using
/confirm
API call, when I call the API, pending events are confirmed, but the workflow that is supposed to be triggered uponWhen new event is booked
does not get triggered. Manual "Confirm" on the bookings page does trigger the workflow.Steps to Reproduce
Request confirmation
When new event is booked
workflow and enableDisable default confirmation emails for attendees
/confirm
APIActual Results
Actual result: no notification email is sent as set in the Workflow.
Expected Results
Expected: API confirmation of a booking should have triggered the workflow.
The text was updated successfully, but these errors were encountered: