Skip to main content
Free template

Automation Recovery Cards: what to do when it breaks and you're not there

Tools can tell you what failed. They can't tell whoever covers for you who owns the Airtable base, where the key lives, or that pressing retry on a booking makes a second booking. One card per automation fixes that. Fill it in once, keep it where your team can find it.

The one rule that prevents most damage

Retry from your automation tool, not from the source.In n8n, Retry on a failed run starts again at the step that failed. Re-sending the original form, order or email starts everything over, and that's how customers get two emails and your records get two rows.

The blank card

RECOVERY CARD: [automation name]
What it does: [one line, e.g. "Replies to every new lead within a minute"]

DEPENDS ON
Tool / account        Used for              Owner (who to ask)     How to get in
[e.g. Gemini key]     [drafting replies]    [name, phone]          [where the key lives]
[e.g. Airtable]       [the lead records]    [name]                 [who shares the base]
[the machine n8n      [everything]          [name]                 [server / laptop login]
 runs on]

LAST CONFIRMED ACTION (where to look to see what really happened)
[e.g. Resend > Emails, the "Leads" table, n8n > Executions]

RETRY RULES
Safe to retry:    [steps that only read or think, e.g. the AI step]
Hold, check first: [steps that send or create, e.g. "Send reply": check the email log]
Never:            [e.g. "Don't ask the customer to resubmit the form"]

Two filled-in examples

New order sync

Depends onUsed forHow to get in
Airtable “Orders” tableThe order recordWho shares the base
ResendCustomer confirmation and VIP alertresend.com, API keys
Your storeSends orders inWhoever runs the store admin

Last confirmed action: Search the Orders table for the order ID, then check Resend's email log for the confirmation.

  • • Safe: a failure at the Airtable step that returned a clear error.
  • • Hold: if the Airtable step timed out, search for the order ID first. It may already be there.
  • • Never: re-send the order from the store. You'd get a second row and a second email to the customer.

Voice AI receptionist

Depends onUsed forHow to get in
VapiThe voice on the phonedashboard.vapi.ai
Cal.comOpen times and bookingsSettings, Developer, API keys
Airtable “VoiceCalls”The call logWho shares the base

Last confirmed action: Cal.com bookings for the booking itself; the call log and Vapi's call recordings for what was said.

  • • Don't retry the in-call steps: the caller has already hung up.
  • • Never make a booking by retrying. Check Cal.com, then call the customer back.
  • • Safe: the end-of-call summary. It updates the same record.

Every one of my automation templates ships with its card already written, plus the free Setup Doctor to tell you what broke.