CHATBOTS
New GitHub Repo to Catalog and Teams Welcome
When a new GitHub repository is created, derives its initial owner from the creator and recent commits, writes a service record to the Postgres catalog.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub repository-created event firesGitHub
- ActionRead creator and early commit authorsGitHub
- LogicPick most active contributor if creator is a bot account
- ActionUpsert a draft service record into the catalogPostgres
- OutputPost a confirm-ownership prompt to TeamsMicrosoft Teams
What it does
This workflow keeps the service catalog from going stale by catching new services at birth. When a repository is created in GitHub, it captures the creator and early committers, writes a draft service record into the Postgres catalog with that owner, and posts a confirmation prompt in Teams so the team can verify or fix the assignment.
When to use it
Use it when new services are spun up faster than anyone remembers to register them, leaving the 'who owns this' bot blind to recent work. This closes the gap automatically at creation time.
How it works
- 1A GitHub repository-created event triggers the flow.
- 2The flow reads the creator and the first few commit authors to infer an initial owner.
- 3A logic step picks the most active early contributor when the creator is a service account.
- 4The Postgres step upserts a draft service record with the inferred owner and team.
- 5A Teams message posts to the platform channel asking the owner to confirm or correct the entry.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.