OTHER
Suppress Duplicate Sensor Alerts and Track Open Faults in Airtable
Deduplicates repeated anomaly webhooks from the same sensor within a cooldown window.
How it runs
The automated pipeline, trigger to output.
- TriggerSensor anomaly arrives via webhookHTTP webhook
- LogicCheck Airtable for matching open fault in cooldown window
- ActionIncrement repeat counter on existing fault rowAirtable
- ActionCreate new fault record when first seenAirtable
- ActionNotify Slack only on first occurrenceSlack
- OutputReturn fault ID and dedupe statusHTTP webhook
What it does
Flapping sensors and re-firing alerts create alert fatigue. This workflow ensures each genuine fault is recorded and escalated exactly once, while still tracking how many times it re-triggered.
When to use it
Use it when a single failing unit (a sticking damper, a noisy vibration sensor) hammers your webhook with the same anomaly every few seconds. You want one clean record per fault and a count of repeats, not 200 Slack pings.
How it works
- 1An HTTP webhook receives each anomaly event keyed by sensor ID and fault type.
- 2A logic step checks Airtable for an open fault matching that key inside the cooldown window.
- 3If it's a duplicate, an action increments the repeat counter and last-seen timestamp on the existing Airtable row, then exits quietly.
- 4If it's new, an action creates a fresh fault record in the Airtable register with status Open.
- 5For new faults only, a Slack message notifies the facilities channel.
- 6The output returns the fault record ID and whether it was deduped.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AirtableBases, tables, views, automations.
- 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.