The flow
Starts it 2Logic 5Service 11
The steps in the order they run, from what starts it.
- 1When Booking RequestedWebhookStarts it
- 2When Stripe Payment ConfirmedWebhookStarts it
- 3Set Booking DetailsSetLogic
- 4Set Booking IdentifierSetLogic
- 5Check Calendar for Open SlotGoogle CalendarService
- 6Add Event to CalendarGoogle CalendarService
- 7If Slot is AvailableIfLogic
- 8Email Booking ConfirmationGmailService
- 9Post to Stripe Payment APIHttp RequestService
- 10Email Slot UnavailabilityGmailService
- 11Email Lawyer NotificationGmailService
- 12Build Payment Link InfoSetLogic
- 13Telegram Lawyer NotificationTelegramService
- 14Email Payment Link to ClientGmailService
- 15Append Booking to SheetsGoogle SheetsService
- 16Telegram Payment LinkTelegramService
- 17Wait 23 HoursWaitLogic
- 18Email 24hr Reminder to ClientGmailService
How it's built
- Starts on
- Another system calling it
- Steps
- 18, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Google Calendar, Google Sheets, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Google Calendar, Google Sheets and Telegram accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 18 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 18 steps before you point it at anything that matters.