Calendly
Every Calendly booking creates or updates a contact in Strkr, logs the event on the matching deal, and triggers the workflow that follows. Teams keep Calendly for the booking surface and let Strkr own the record.
Everything Calendly does inside Strkr.
- Auto-create contacts from bookings
- Log meetings on deal timelines
- Trigger flows on booking created and cancelled
- Map Calendly event types to pipeline stages
Native code, not a shim.
OAuth where available
Calendly will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Calendly once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Calendly from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Calendly is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Calendly is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.