OTHER
Repeat Sensor Breach Detector to Linear Bug
On a schedule, scans Honeycomb for assets that breached their threshold three or more times in a week and files a Linear issue for root-cause investigation.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers scan
- ActionQuery Honeycomb for 7-day breach events by assetHoneycomb
- LogicKeep 3+ breaches, dedupe open Linear issues
- ActionFile Linear issue for root-cause investigationLinear
- OutputPost new investigations summary to SlackSlack
What it does
Catches chronic problems that single alerts miss. Rather than reacting to one breach, it finds assets that keep breaching and turns the pattern into an engineering investigation ticket, so a failing compressor gets a root-cause fix instead of repeated band-aid resets.
When to use it
Use this when your team already handles individual alerts but recurring failures slip through because no single event looks alarming. Run it weekly to surface the worst repeat offenders.
How it works
- 1A weekly schedule triggers the scan.
- 2An action queries Honeycomb for sensor breach events grouped by asset over the past seven days.
- 3A logic step keeps only assets with three or more breaches and filters out ones with an already-open Linear issue.
- 4An action files a Linear issue per qualifying asset with the breach count, timestamps, and metric trend for root-cause investigation.
- 5A final Slack summary lists the new investigations opened so the team has visibility.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 Other workflows
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Build a daily expected-visitor roster and send it to the front desk
Every morning this pulls the day's pre-registered visitors from Airtable, builds a sorted arrival roster with hosts and times.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
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.