Verify employee offboarding and access revocation via webhook and HTTP APIs

Description

Quick overview
This workflow receives an employee offboarding request via webhook, calls external IAM, SaaS, and IT/HR HTTP endpoints to revoke and verify access removal, then returns a final compliance report with per-step statuses to the requester.

How it works
Receives an offboarding payload via a POST webhook.
Validates required fields (such as employeeId, email, and lastDay) and prepares request data, target URLs, and a request ID.
Calls an IAM revoke API over HTTP to disable/delete the identity, then calls an IAM verify API to confirm the account is revoked.
Calls a SaaS revoke API over HTTP with an apps list (for example Slack, Google Workspace, and GitHub), then calls a SaaS verify API to confirm access is removed.
Calls an IT/HR finalize API over HTTP to complete offboarding actions such as disabling email and updating HR status.
Aggregates all results into a compliance status (fully_revoked/partial/failed) and returns the report to the webhook caller with an appropriate HTTP status code.

Setup
Configure the system that initiates offboarding to send a POST request to this workflow’s webhook URL with fields like employeeId, email, and lastDay.
Replace the placeholder httpbin.org URLs with your real IAM, SaaS, and IT/HR API endpoints and ensure they accept the JSON bodies this workflow sends.
If your endpoints require authentication, add the necessary HTTP headers or credentials to the HTTP Request steps.
Review the SaaS application list (slack, google_workspace, github, notion, jira) and adjust it to match the services you need to revoke and verify.