CHATBOTS
Incident Webhook to Owner Lookup and Teams Page
When an incident webhook fires for a service, looks up the owner in the catalog plus the last committer in GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerIncident webhook arrives with service identifierHTTP webhook
- ActionResolve owner, team, and on-call from PostgresPostgres
- LogicBranch: owner found vs. fallback to platform channel
- ActionFetch most recent committer for the serviceGitHub
- OutputPost incident page to the owning team's Teams channelMicrosoft Teams
What it does
This workflow turns an incoming incident alert into an immediate ownership page. A monitoring webhook sends the affected service identifier; the flow resolves the registered owner from Postgres and the most recent code contributor from GitHub, then drops a high-visibility message into the right Teams channel so responders know who to engage without hunting.
When to use it
Use it when alerts fire faster than humans can figure out who's responsible. It collapses the 'who do we page' delay at the start of every incident into a single automated message.
How it works
- 1An incoming HTTP webhook from your monitoring system triggers the flow with the service identifier.
- 2The Postgres step resolves the owner, team, and on-call rotation for that service.
- 3A branch checks whether an owner was found; if not, it routes to a fallback platform channel.
- 4GitHub returns the most recent committer as a likely subject-matter expert.
- 5The flow posts an incident alert to the owning team's Teams channel, naming the on-call and last committer.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect Microsoft TeamsChannels, chats, files.
- 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 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.