Deactivate user seat in Calendly
Automatically deactivate a departing user’s Calendly seat from a Slack request with Stepwork, so paid seats stay matched to people who still schedule.
- Use case
- Employee offboardingIT
- Best for
- IT Administrator
- Applications used
Calendly
Slack
- Business outcome
- Cost savings
The problem
They left. Their Calendly seat did not.
When someone leaves, Calendly seats often stay assigned until someone remembers to open the org settings. Scheduling seats pile up for people who will never book again.
Finance notices at renewal. IT gets a cleanup scramble, with no record of when each seat was actually freed.
The outcome
Seats stay matched to active schedulers
Stepwork removes the departing user from the Calendly organization and frees their seat. The run records who asked and which seat was reclaimed.
- The user is removed from the Calendly organization.
- Their paid seat is freed.
- If the member cannot be found, the run stops.
The process
From Slack request to a freed Calendly seat
A teammate posts the departing user’s email in Slack. Stepwork removes them from Calendly.
- Step 1
Request it in Slack
A teammate posts the departing user’s work email in the offboarding channel. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Find the member
Stepwork signs in to Calendly and opens the organization members list. If no member matches that email, the run stops instead of guessing.
- Step 3
Remove the seat
Stepwork removes the member from the organization, the same action an admin takes from the members page, freeing the seat.
- Step 4
Confirm and reply in Slack
Stepwork checks that the person no longer appears in the member list, then posts the result back in Slack.
Why Stepwork
Seat cleanup stays on the path you recorded
A deterministic agent runs the Calendly remove path you recorded. Offboarding does not wait on whoever happens to have the org open.
Similar use cases
Similar use cases
Reassign round-robin events on offboard in CalendlyRemoves a departing member from round-robin and collective event types and confirms coverage.
Remove member from organization in GitHubSigns into GitHub org settings, locates the member, and removes them, revoking repo access and freeing the seat.
Deactivate user account in OktaSigns into the Okta admin console, locates the user by email, deactivates the account, and confirms the status change ended all SSO sessions.
FAQ
Common questions
Ask about this use case
Bob answers from this page and the rest of stepwork.com, and links each source.
Bob answers only from what Stepwork has published, and links every source. Questions are saved to improve answers, so leave out anything confidential.

