Use “Start delivery work from a paid Cal.com booking” in Recued. When a booking is reported paid, combine its current intake with your delivery rules, then review a new project or tasks in an existing one—no CRM required.
Start delivery work from a paid Cal.com booking
Use “Start delivery work from a paid Cal.com booking” in Recued. When a booking is reported paid, combine its current intake with your delivery rules, then review a new project or tasks in an existing one—no CRM required.
Complete workflow
Use Paid Booking Fulfillment - Cal.com in Recued. When Cal.com reports a booking paid, combine its current intake with your delivery rules, then review a new delivery project or tasks in an existing one—no CRM required.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
A paid booking starts delivery work
This automatic recipe accepts only a signed BOOKING_PAID event, then re-reads the current booking and its attendees through the paired Cal.com account. It combines the booking intake with your fulfillment instructions to propose delivery work. No CRM is required: current attendee and host emails are the only people AI may assign.
The recipe stops if the booking now reads as cancelled or rejected. It does not copy a payment amount or claim accounting settlement; the signed event says Cal.com reported the booking paid, while the provider read-back supplies the current booking details.
Existing or new project
Choose an existing project to add tasks there, or leave it blank to propose one new local project. A task owner must exactly match a current attendee or host email. Missing intake, unclear ownership, invalid dates, and low-confidence suggestions stay in the review output. If no task passes those checks, no empty project is created.
Approval and source limits
Preview changes nothing, and its automatic-run output is not saved as a review page. Apply mode pauses before creating the project and tasks. The webhook result is not itself a durable fulfillment or accounting record.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
max tasks
setting
=
12
write mode
setting
=
apply
confidence threshold
setting
=
0.8
existing project ref
setting
=
fulfillment instructions
setting
=
[object Object]
Uses (7 operations)
core.webhook.event.get
recued-core.calcom.booking.read
recued-core.calcom.booking.attendee.search
core.work-entity.get
core.ai.extract
core.work-entity.project.create
core.work-entity.task.create
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
2 more aren't listed here. You'll see them at install.