CHATBOTS
Sync Service Ownership from Confluence to Catalog DB
On a schedule, parses service runbook pages in Confluence and upserts owner, on-call, runbook URL, and SLA into the Postgres service catalog so the ownership bot always answers…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionFetch all service-runbook pages under the Confluence parentConfluence
- ActionParse owner, on-call, runbook URL, and SLA from each pageOpenAI
- LogicSkip pages missing required ownership fields and collect them
- ActionUpsert valid records into the Postgres service_catalogPostgres
- OutputPost sync summary and skipped-page list to SlackSlack
What it does
Keeps your machine-readable service catalog in sync with the human-written source of truth. It reads a designated Confluence space of service runbook pages, extracts the structured ownership fields from each, and upserts them into the Postgres catalog the Slack bot reads from.
When to use it
When teams document ownership in Confluence but your bot or dashboards need it in a queryable table. Run it nightly so answers never go stale and drift between docs and data is caught early.
How it works
- 1A scheduled trigger fires nightly.
- 2It fetches all child pages under the configured Confluence service-runbook parent page.
- 3For each page it parses the owner, on-call rotation, runbook URL, and SLA tier from the page's structured fields.
- 4A logic step skips pages missing required ownership fields and collects them for reporting.
- 5It upserts each valid record into the Postgres `service_catalog`, stamping `last_synced`.
- 6It posts a short summary to Slack listing pages skipped for missing fields.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, 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 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.