MARKETING
Inbound Blocklist Bounce Investigator
When a delivery-failure email lands in a monitored Gmail postmaster inbox, it parses the bounce reason, classifies blocklist or reputation rejections with an LLM.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email in postmaster inboxGmail
- ActionRead full bounce body and headersGmail
- ActionClassify rejection with LLMOpenAI
- LogicKeep only blocklist/reputation hits
- ActionOpen Airtable investigation ticketAirtable
- OutputEscalate true blocklist hits to SlackSlack
What it does
Providers bury the real reason a domain is being rejected inside cryptic bounce-back emails. This workflow reads those delivery-failure messages as they arrive, uses an LLM to classify whether the rejection is a true blocklist or reputation block versus a routine bounce, and routes only the reputation-threatening ones to a human.
When to use it
Use it when bounce notifications and postmaster replies land in a dedicated Gmail inbox and you want signal, not a flooded folder. It surfaces the rare but urgent 'you are on a blocklist' message that hides among ordinary mailbox-full bounces.
How it works
- 1A new email in the monitored Gmail postmaster inbox triggers the run.
- 2A Gmail read pulls the full bounce body and headers.
- 3An OpenAI step classifies the rejection type and extracts the provider and any named blocklist.
- 4A logic step keeps only true blocklist or reputation rejections.
- 5An Airtable ticket is created with the parsed provider, reason, and a remediation hint.
- 6A Slack escalation posts the high-severity hits so the team can start delisting immediately.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 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.