CHATBOTS
Slack Access Bot: Offboarding Revocation Sweep with Confirmation
When an offboarding event fires, the workflow gathers all of a departing employee's entitlements from the matrix, revokes the GitHub-backed ones.
How it runs
The automated pipeline, trigger to output.
- TriggerOffboarding webhook received with employee idHTTP webhook
- ActionCollect all active grants for the person from matrixCoda
- LogicSplit auto-revocable vs. manual-only systems
- ActionRemove GitHub org/team membershipsGitHub
- ActionMark handled rows revoked in the matrixCoda
- OutputPost revocation summary to security channelSlack
What it does
Closes every door when someone leaves. Triggered by an offboarding webhook (HRIS or a manual form), it collects all entitlements tied to the person in the matrix, revokes the access it can act on directly — like GitHub org/team membership — marks each row revoked, and drops a tidy summary into your security channel so nothing is assumed.
When to use it
Use it the moment an employee or contractor is terminated, to eliminate the lag between HR's last-day notice and IT actually pulling access. Critical for reducing orphaned-account risk during audits.
How it works
- 1An offboarding webhook arrives with the person's identifier.
- 2The matrix is queried for all active grants belonging to them.
- 3A branch separates auto-revocable systems from manual-only ones.
- 4GitHub memberships are removed via the org API.
- 5Each handled row is marked revoked in the matrix.
- 6A completion report listing revoked vs. manual-followup items posts to the Slack security channel.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect CodaDocs, packs, automations.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Chatbots workflows
Discord WAF False-Positive Triage from Ray ID
When a user posts a Cloudflare ray ID in a Discord support channel, the bot looks up the blocked request's WAF event, classifies whether it looks like a genuine false positive.
Agentic WAF Investigator with Discord Approval Gate
An autonomous agent investigates a Discord-reported WAF block end to end: pulls Cloudflare logs, correlates with PagerDuty incidents, decides if an allowlist is safe.
Discord Onboarding Completion to CRM Sync
The moment a member finishes Discord onboarding, captures their submitted profile answers, creates or updates a contact in HubSpot.
Draft WAF Allowlist Proposal to Linear from Discord Report
Lets a support engineer confirm a Discord WAF report is a false positive, then auto-drafts a scoped Cloudflare allowlist rule proposal and files it as a Linear ticket…
Discord FAQ Free-Text Answer Grader
When a member submits a free-text answer in their onboarding thread, an agent grades it against the canonical FAQ knowledge base, replies with targeted feedback.
Discord FAQ-Gated Role Concierge
Greets each new Discord member in a private onboarding thread, walks them through required FAQ steps one at a time.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.