MARKETING
Spam-Complaint Surge Quarantine
Ingests spam-complaint (FBL) webhooks from your ESP, tallies complaints per campaign in a rolling window.
How it runs
The automated pipeline, trigger to output.
- TriggerESP posts spam-complaint webhookHTTP webhook
- ActionRecord complaint and recompute ratePostgres
- LogicCheck complaint rate vs 0.1% line
- ActionQuarantine the campaignPostgres
- ActionLog incident to AirtableAirtable
- OutputPage on-call marketer in SlackSlack
What it does
Mailbox providers treat spam complaints as the single most damaging reputation signal. This workflow reacts to feedback-loop complaint events in real time, rolls them up per campaign, and quarantines any campaign whose complaint rate crosses the 0.1% danger line before the provider starts throttling your whole domain.
When to use it
Use it when your ESP can post FBL or complaint webhooks and you run multiple concurrent campaigns. It contains the blast radius of one bad creative or one mismatched audience without a human watching the dashboard.
How it works
- 1An incoming complaint webhook from the ESP triggers the run.
- 2A Postgres write records the complaint and recomputes the trailing complaint rate for that campaign.
- 3A logic step checks the rate against the 0.1% threshold.
- 4If breached, a Postgres update flags the campaign as quarantined to halt further sends.
- 5An Airtable record captures the incident: campaign, rate, complaint sample, and timestamp for the postmortem log.
- 6A Slack direct alert pages the on-call marketer with the campaign and the numbers.
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 AirtableBases, tables, views, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Marketing workflows
UTM Link Linter: Block Malformed Tracking URLs Before Launch
Validates every campaign tracking link queued in an Airtable launch table against your UTM naming rules.
Spin up a rush localization handoff from a Slack chat request
A marketer asks the CEO agent in chat to rush-translate a piece of approved copy into specific languages; the agent files the source in Google Drive.
Slack UTM Check: Paste a Link, Get an Instant Verdict
Lets marketers drop a tracking URL into a Slack channel and get an immediate threaded reply that says whether the UTMs are valid, what is wrong, and a corrected suggestion.
UTM Audit for Campaign Spreadsheets in Google Drive
Watches a Google Drive folder for new or updated campaign link spreadsheets, lints every URL inside.
Real-Time UTM Validator API for Link-Building Forms
Exposes a webhook that validates a tracking URL on the fly and returns a structured pass/fail JSON response.
Agentic UTM Taxonomy Steward: Detect, Explain, and Propose Fixes
An agent reviews the full backlog of campaign links in Airtable, reasons about taxonomy drift beyond rigid rules, drafts standardized replacements for malformed UTMs.
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.