DEVOPS
Discord On-Call Incident Recap to Postgres Ledger
When an on-call engineer posts a wrap-up note via a Discord slash command, parses it into a structured incident record and writes it to a Postgres handoff ledger for the next…
How it runs
The automated pipeline, trigger to output.
- TriggerDiscord /handoff slash commandDiscord
- LogicParse and validate recap fields
- LogicBranch on validation result
- ActionInsert recap into Postgres ledgerPostgres
- OutputConfirm entry in Discord threadDiscord
What it does
Captures end-of-shift recaps that the on-call engineer types directly in Discord and turns them into durable records. When the engineer runs a handoff slash command, the flow parses the note into structured fields (services touched, status, follow-up owner) and appends a row to the Postgres handoff ledger, then confirms back in the thread.
When to use it
Use it when handoff context lives in chat history and gets buried. The Postgres ledger becomes the source of truth that the shift-digest workflow can read at the next rotation, closing the handoff loop.
How it works
- 1A Discord slash command (for example /handoff) triggers the flow with the recap text.
- 2A logic step parses the message into structured fields and validates required ones.
- 3If validation fails, it replies in Discord asking for the missing field and stops.
- 4On success it inserts the structured recap into the Postgres handoff ledger.
- 5It posts a confirmation with the ledger entry ID back to the Discord thread.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.