Trigger-based automations — reminders, follow-ups, webhooks — across the booking lifecycle.
64
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./packages/scheduling/docs/skills/workflows/SKILL.mdnew-booking — fires when a booking is createdbefore-event — offset minutes BEFORE startTimeafter-event — offset minutes AFTER endTimereschedule — booking rescheduledcancellation — booking cancelledno-show — a host marked an attendee as no-show| Action | Sends |
|---|---|
email-host | Email to the organizer |
email-attendee | Email to the attendee |
email-address | Email to a fixed address (e.g. ops@example.com) |
sms-attendee | SMS to the attendee's phone (requires attendee phone custom field) |
sms-host | SMS to the host |
sms-number | SMS to a fixed number |
webhook | HTTP POST to a URL |
Step offsetMinutes is relative to the trigger time. For before-event
use positive values (we apply them with a minus sign internally).
In email subjects / bodies and SMS bodies:
{eventName} — event type title{attendeeName}, {attendeeEmail} — first attendee{hostName}, {hostEmail} — organizer{startTime}, {endTime} — formatted in host's timezone{location} — meeting URL or address{cancelUrl}, {rescheduleUrl} — public magic linksWhen a booking fires a trigger, the hook dispatcher materializes rows in
scheduled_reminders. A recurring job processes due rows and fires the
actual emails/SMS/webhooks. Framework-side recurring jobs handle the
polling.
| User | Action |
|---|---|
| "Email attendees 24h before the meeting" | create-workflow --trigger before-event --steps '[{action: email-attendee, offsetMinutes: 1440}]' |
| "Text me when someone books" | create-workflow --trigger new-booking --steps '[{action: sms-host, ...}]' |
| "Stop all reminders on an event type" | toggle-workflow to disable |
e9a2f0e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.