CHATBOTS
Conversational GitHub Repo Access Provisioner
A Teams chatbot that takes a repo-access request, routes it to the repo owner for approval, and on approval adds the user to the GitHub team at the right permission level.
How it runs
The automated pipeline, trigger to output.
- TriggerDeveloper requests repo access in TeamsMicrosoft Teams
- ActionSend approve/deny prompt to repo ownerMicrosoft Teams
- LogicGate: continue only if owner approves
- ActionAdd user to GitHub team at requested permissionGitHub
- ActionLog grant and approver to audit tableAirtable
- OutputConfirm grant to requester in TeamsMicrosoft Teams
What it does
Developers ask the IT bot for access to a GitHub repository in plain language. The bot identifies the repo and the permission level requested, asks the repo's code owner to approve or deny inline, and — only after approval — adds the requester to the matching GitHub team. No more open-ended Slack threads or forgotten access requests.
When to use it
Use this when repo access is granted ad hoc and you need a fast but governed path: self-serve request, owner approval, automatic provisioning, and a record of who approved what.
How it works
- 1A developer messages the bot in Teams asking for access to a repo ("need write on payments-api").
- 2The bot parses the repo name and requested permission (read/write/admin).
- 3It posts an approve/deny prompt to the repo's designated owner in Teams.
- 4Logic gate: proceed only on explicit approval; otherwise notify the requester it was declined.
- 5On approval, it adds the user to the appropriate GitHub team via the API.
- 6The bot confirms back to the requester and logs the grant for audit.
Set it up
What you configure once, before turning it on.
- 1Connect Microsoft TeamsChannels, chats, files.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect AirtableBases, tables, views, automations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Chatbots workflows
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.
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.
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 verify-button onboarding via web form webhook
Receives a completed external verification form by webhook, matches it to the Discord account, grants the verified role, and confirms back to the member in Discord.
Discord intro-gated role granting concierge
Watches your #introductions channel, uses AI to confirm a new member's intro is genuine and complete, then auto-assigns the verified Member role and welcomes them.
Daily Discord Digest of Repeated WAF False-Positive Reports
Each morning, scans logged Discord WAF reports in Postgres, groups them by the Cloudflare rule that keeps firing.
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.