Resilient Agent Ops Automation Pack for Make.com — Retry Router, Dedupe Guard & Approval Gate Bots

Inspired by conductor-oss/conductor, a workflow orchestration engine trending on GitHub this week (32k+ stars) for giving AI agents and applications durable, resilient execution — every step persisted, retried, and recoverable, with built-in human-in-the-loop approval. Make.com scenarios don't have any of that natively: a failed HTTP call just fails, a re-delivered webhook just re-runs twice, and there's no built-in "pause for a human" primitive. This pack translates three of those resilience patterns into scenarios you build in Make with tools you already have.

Included templates
- Retry & Dead-Letter Router — wraps any fragile API/HTTP call (AI provider, CRM, payment webhook) in an exponential-backoff retry loop using a Data Store to track attempt count per job; on final failure the full payload, error, and attempt history get logged to an Airtable "Dead Letter Queue" for one-click manual replay, with a Slack alert to your ops channel
- Dedupe Guard — computes an idempotency key from every inbound webhook (event ID or payload hash), checks it against a Data Store before your automation logic runs, and silently drops exact re-deliveries — the #1 cause of double-charged customers and duplicate Slack pings from services like Stripe and GitHub that retry on timeout
- Approval Gate — pauses a scenario after an AI drafting step and before any risky action (send, publish, purchase, modify), logs a pending-approval record with a unique token, and sends an Approve/Reject Slack message or email; a second linked scenario listens for the approval webhook and only continues the real action once a human signs off, with an auto-expire check for approvals left untouched too long

Every scenario is built to fail loud and safe: nothing silently retries forever, and nothing sends without an audit trail.

Common use cases
- Stop losing leads, orders, or AI-agent output when a downstream API has a bad five minutes
- Eliminate duplicate records and double-sent notifications from webhook redelivery
- Add a real human checkpoint in front of any AI agent step that emails, posts, or spends money on your behalf

Requirements
- A Make.com account (Core plan or higher, for Data Store access)
- Airtable (free tier works) for the Dead Letter Queue and Approval log
- Slack and/or Gmail for alerts and approval requests
- Any HTTP-callable service you want to protect (AI provider, CRM, payment processor, etc.)

What you receive
You get a detailed, module-by-module build guide plus a scenario map for each of the three bots — trigger, Data Store keys, retry/backoff logic, filters, router branches, and error-handling paths all specified. Make.com blueprint exports are account-specific (they embed your own connection IDs), so rather than shipping a blueprint file that would need reconnecting anyway, this pack gives you the exact scenario map to rebuild each bot in your own account in under 30 minutes per template — no guesswork required.