BPPP/smb-online
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

Booking-sync workflow: Cal.com webhook (self-hosted) + Google Calendar poll #8

New Issue
Closed
opened 2026-07-16 10:37:37 +02:00 by mivanchenko · 1 comment
mivanchenko commented 2026-07-16 10:37:37 +02:00
Owner
Copy Link
Copy Source

Build/finish the booking-sync n8n workflow so bookings from both delivery styles land in the CRM bookings table:

  • self-hosted Cal.com → webhook → POST /crm/api/bookings
  • Google Calendar appointment schedule → scheduled poll → upsert

Depends on the booking upsert fix (idempotent POST) so re-delivered events don't 500.

Build/finish the `booking-sync` n8n workflow so bookings from both delivery styles land in the CRM `bookings` table: - self-hosted **Cal.com** → webhook → POST `/crm/api/bookings` - **Google Calendar** appointment schedule → scheduled poll → upsert Depends on the booking upsert fix (idempotent POST) so re-delivered events don't 500.
mivanchenko added the n8nbookingenhancement labels 2026-07-16 10:37:37 +02:00
mivanchenko commented 2026-07-16 10:41:26 +02:00
Author
Owner
Copy Link
Copy Source

Closing as already done. Booking-sync is implemented via n8n/booking-sync.json — a single shared Easy!Appointments instance (deploy/booking/) syncs bookings into the CRM. The originally-scoped Tier-B-Cal.com-webhook / Tier-A-Google-Calendar-poll split was superseded by the tier-decoupling (see #2). Reopen only if we move to per-client Cal.com/GCal booking.

Closing as already done. Booking-sync is implemented via `n8n/booking-sync.json` — a single shared Easy!Appointments instance (`deploy/booking/`) syncs bookings into the CRM. The originally-scoped Tier-B-Cal.com-webhook / Tier-A-Google-Calendar-poll split was superseded by the tier-decoupling (see #2). Reopen only if we move to per-client Cal.com/GCal booking.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
booking
Booking / Easy!Appointments
 bug
Something is broken
 crm
Back office / CRM
 enhancement
New feature or request
 infra
Infrastructure
 n8n
n8n workflows
 needs-info
Waiting on reporter for more information
 needs-triage
Maintainer needs to evaluate this issue
 ops
Operational / runtime
 ready-for-agent
Fully specified, ready for an AFK agent
 ready-for-human
Requires human implementation
 security
Security / secrets hardening
 tech-debt
Refactor / debt
 wontfix
Will not be actioned
No Label booking enhancement n8n
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Administrator mivanchenko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: BPPP/smb-online#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?