The open-source Calendly — same integration, fully self-hostable.
Cal.com is the open-source alternative to Calendly that many of our agency customers prefer for ownership, brandability, and self-hosted privacy. The Inflowave integration mirrors Calendly: outbound booking links from DMs, inbound booking sync to the contact timeline, workflow triggers on booking-confirmed, and team round-robin support. Because Cal.com is open-source you can self-host on your own domain (book.youragency.com), customise the booking page deeply, and avoid the Calendly per-seat pricing past 10+ team members. The integration uses Cal.com's webhook + REST API; works with both cal.com cloud and self-hosted instances.
Open Inflowave → Settings → Connected Accounts → Add Cal.com
Paste your Cal.com API key (or self-hosted endpoint URL + key)
Map Cal.com event types to Inflowave pipeline stages
Configure booking-confirmed workflow
Test: drop your event link in a test DM
Run book.youragency.com fully under your control — Cal.com self-hosted + Inflowave brings everything in-house.
Cal.com supports per-team branding; combined with Inflowave RBAC, each agency client gets a branded booking flow.
Once you have 20+ users, Cal.com self-hosted becomes meaningfully cheaper than Calendly Teams.
For technical teams: customise Cal.com beyond what Calendly allows, then sync everything through Inflowave.
Yes — paste the self-hosted endpoint and API key. Webhooks must be reachable from Inflowave (open the firewall to our webhook IPs, listed in the docs).
Calendly if you want zero setup. Cal.com if you want self-hosting, deeper customisation, or to avoid per-seat costs. Both integrations are first-class.
Yes — same as Calendly. Round-robin assigns to the right team member; Inflowave maps to the agency client they handle.
7-day free trial. Unlimited Instagram accounts. Cancel any time.
The Cal.com integration plugs into the same Inflowave workflow engine that handles DM automation, lead pipelines, and unified inbox. Connect Cal.com to Inflowave. Same one-click DM booking flow, CRM timeline sync, and workflow triggers — but on the open-source scheduling stack. Once connected, every event Cal.com fires can trigger an Inflowave automation — and every Inflowave action can write data back into Cal.com — so the two tools stay in sync without manual exports or copy-paste.
Most teams using Inflowave alongside Cal.com land on a similar setup pattern: connect the account on the integrations page, pick the events you want to react to, and route the data into the Inflowave entity it should live on (lead, contact, conversation, or pipeline stage). Setup takes about 10 minutes for a fresh workspace and is reversible — disconnecting cleanly removes the webhook and stops the data sync.
Inflowave's role is to be the operating layer for Instagram-driven business — which means the Cal.com integration's value lands hardest when there's a real conversation flow to attach data to. Agencies running multiple client Instagram accounts use Cal.com per-client; solo creators tend to wire one Cal.com account to all their connected Instagram profiles. Both shapes are supported by the same integration code path.
If Cal.com isn't the right fit, Inflowave ships native equivalents for many common workflows (built-in scheduling, built-in CRM, built-in unified inbox), so the integration is meant for teams that already standardized on Cal.com and want to keep using it — not as a gating dependency. The integration is included in every paid Inflowave plan with no per-event surcharge.