ENGINEERING
Engineer-Reported Flaky Test to ClickUp from Slack
Lets an engineer report a flaky test from a Slack shortcut, enriches the report with the test's recent failure history from GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack shortcut with test nameSlack
- ActionLook up recent failures on GitHubGitHub
- LogicDedupe against open ClickUp items
- ActionCreate assigned ClickUp tech-debt taskClickUp
- OutputReply in Slack thread with task linkSlack
What it does
It turns the common Slack moment of "this test is flaky again" into a tracked item. An engineer triggers a Slack shortcut and names the test; the workflow looks up the test's recent CI failure history on GitHub, then creates a ClickUp tech-debt task pre-filled with that evidence and routed to the right team.
When to use it
Use it when flaky tests get complained about in chat but rarely make it into the backlog. It captures human knowledge instantly and attaches hard data so triage is fast.
How it works
- 1An engineer invokes the Slack shortcut and submits the test name.
- 2The workflow searches GitHub Actions history for that test's recent failures.
- 3A logic step checks ClickUp for an existing open item to prevent duplicates.
- 4If new, it creates a ClickUp tech-debt task with the failure count, last-seen date, and reporter.
- 5It maps the test path to an owning team and assigns the task.
- 6It replies in the Slack thread with the created task link.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 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 Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
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.