DEVOPS
Record Flaky-Test Events to Postgres and Alert Discord on Spikes
Accepts flaky-test events posted by your CI via webhook, appends each occurrence to a Postgres ledger.
How it runs
The automated pipeline, trigger to output.
- TriggerCI posts flaky-test event via webhookHTTP webhook
- ActionInsert occurrence into Postgres ledgerPostgres
- ActionQuery today's count for this testPostgres
- LogicSpike threshold crossed and not yet alerted?
- OutputPost spike alert to DiscordDiscord
What it does
This workflow gives you a durable, queryable history of flaky-test occurrences independent of any CI vendor. Your pipeline posts a small JSON payload whenever a test is detected as flaky; the flow stores it and watches for tests that suddenly spike, alerting the team before a single flaky test tanks the day's builds.
When to use it
Use this when you want to own your flaky-test data in your own database — for custom dashboards or SLAs — and want a fast heads-up when a previously quiet test starts failing repeatedly in a short window.
How it works
- 1An HTTP webhook trigger receives a flaky-test event from CI (test name, SHA, branch, timestamp).
- 2The flow inserts the occurrence as a row into a Postgres flaky-events table.
- 3It queries today's occurrence count for that test.
- 4A logic step checks whether the count crossed the spike threshold and hasn't already alerted today.
- 5If so, it posts a spike alert to the Discord engineering channel with the test name and recent count.
- 6An acknowledgement is returned to the caller.
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 DiscordCommunity channels + voice + bots.
- 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 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.