MARKETING
Spam-Complaint Feedback Loop: Quarantine Segment and Open a Diagnosis Ticket
On each inbound spam-complaint webhook it tallies complaints per campaign and domain, and once a campaign crosses the complaint-rate limit it quarantines the affected segment.
How it runs
The automated pipeline, trigger to output.
- TriggerSpam-complaint (FBL) webhook receivedHTTP webhook
- ActionUpdate complaint + send counts per campaignPostgres
- LogicComplaint rate over limit?
- ActionQuarantine remaining campaign segmentPostgres
- ActionOpen Linear diagnosis ticketLinear
- OutputNotify team in SlackSlack
What it does
This sentinel consumes Feedback Loop (FBL) complaint events as they arrive by webhook. It updates a running complaint count per campaign and recipient domain, then evaluates whether the campaign's complaint rate has exceeded the safe ceiling (default 0.1%). When it has, the workflow tags the campaign's remaining audience as quarantined, opens a Linear ticket pre-filled with the campaign, domain, and complaint trend, and posts a heads-up to Slack so a human can investigate creative or list-source problems.
When to use it
Use this when complaints, not bounces, are your early-warning signal. Mailbox providers throttle senders on complaint rate long before bounces spike, so catching a single campaign's complaint surge in real time protects inbox placement for everything else.
How it works
- 1An inbound webhook delivers a spam-complaint (FBL) event.
- 2Postgres increments complaint and send counts for the campaign and domain, returning the current rate.
- 3A logic step checks whether the complaint rate is over the limit.
- 4Postgres marks the remaining campaign segment as quarantined.
- 5Linear opens a diagnosis ticket with the campaign, domain, and complaint figures.
- 6Slack notifies the marketing team with a link to the ticket.
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 LinearIssues, projects, cycles, triage.
- 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.