Find the outcome you need.
Start with a symptom, a platform or the thing you want working.
With JavaScript, search filters the whole collection in your browser. Without it, use the linked pages and section navigation below; query filters need JavaScript.
Showing entries 121–160 of 222 in this first collection.
Job
Make new Facebook leads appear in Salesforce again
A new synthetic lead submitted to the agreed Facebook form starts one Zap and creates one Salesforce test lead with the agreed fields.
£165 · untested offer price
Job
Send every mapped Google Sheets invoice field to Xero
One disposable row with the agreed columns makes one draft Xero invoice containing every agreed line item and amount.
£145 · untested offer price
Buyer collection
For a finance manager: make an invoice integration complete and safe to repeat
Define authoritative fields, duplicate rules and reconciliation before repairing a spreadsheet-to-accounting automation.
Troubleshooting guide
A Zap runs, but fields are missing: trace the value from trigger to destination
Inspect one synthetic record through each step and separate missing input, transformation, permissions and destination validation.
Troubleshooting guide
One Sheets row becomes one Xero invoice line: check the line-item shape
Distinguish missing spreadsheet headers from multiple products mapped into one invoice line, using a disposable two-product acceptance case.
Free tool
Workflow time-value calculator: show the assumptions behind automation payback
Use your own time, volume, cost and running-cost inputs to calculate simple monthly value and payback; not a quote or guaranteed saving.
Buyer collection
For an operations manager who inherited automations: find out what runs, who owns it and who is told
Inventory first, then overlaps, alerts and a keep, merge or retire decision for each automation, before anyone rebuilds anything.
Buyer collection
For a marketing manager: make every web lead arrive once, reach an owner and be noticed if the form breaks
Write the lead's path, then check matching, ownership, the Salesforce sync and an alert, using invented leads rather than real ones.
Collection
Automation failure diagnosis in order: from did it run to who was told
A seven-step order for finding out why an automation misbehaved, stopping at the first step that explains it, with a guide for each step.
Collection
Web lead to owner: six checks in order, with synthetic leads
An ordered review of capture, matching, ownership, sync, alert and weekly check for leads that arrive through web forms into HubSpot.
Inspectable example
Synthetic webhook signature test vectors: six deliveries, one accepted
Invented secret, invented body and real HMAC-SHA256 digests show exactly which small changes make a signature check fail, with a verifier you can run.
Inspectable example
Synthetic delivery ledger: the same event arrives three times and the action runs once
A made-up sender delivers six requests, including retries, a tampered copy and an unsigned one; the ledger shows which are accepted and how many actions run.
Inspectable example
Synthetic polling trace: five strategies over the same five records
One invented record is slow to appear and one run crashes; five ways of remembering your place give five different results, from a lost record to nine actions for five records.
Inspectable example
Synthetic lead-routing rule table: eight leads, four rules and a fallback
A written rule order, a named fallback and eight invented leads with expected owners show what a routing acceptance test looks like.
Troubleshooting guide
An Airtable automation failed or did not run: read the history, then check five causes
Find the failing step in the run history, understand why records already matching never trigger, and check inputs, scripts, limits and who gets told.
Troubleshooting guide
Splitting a repetitive Airtable table into linked tables: how the matching works and where it goes wrong
Why exact text matching, commas and formula primary fields matter, and the order that keeps counts reconcilable when one table becomes two.
Troubleshooting guide
A scheduled job that asks for records since its last run: why it loses some and repeats others
Four small pieces make polling reliable: a checkpoint, an overlap, a key for every record and complete paging. See why each exists.
Troubleshooting guide
Who is told when an automation fails? What each tool really does, and how to test it
Zapier, Make, n8n and Airtable each alert in different ways, with delays, gaps and side effects. Find out where yours goes, then test it by breaking a copy.
Troubleshooting guide
Verify a webhook signature on the exact bytes you received, not the data you parsed
Why a correct secret can still fail, how to compare signatures safely, which identifier to trust against replays, and how to test a receiver with known inputs.
Troubleshooting guide
The sender says webhook delivery failed: timeouts, retries, deleted subscriptions and missed events
Answer quickly, expect repeats, and know how to find and replay events that arrived while your endpoint was down.
Troubleshooting guide
Duplicate HubSpot contacts or companies after a web form: which route created them
HubSpot matches contacts by email and companies by domain, but the route a lead takes decides what happens. Learn the four routes and the risks of merging.
Troubleshooting guide
New HubSpot leads with no owner: how rotation, away users and fallbacks really behave
Write the routing rules first, then learn what the rotate action counts for contact records, how HubSpot's Leads tool differs, and where a lead ends up when nobody is available.
Troubleshooting guide
A HubSpot field keeps changing back from Salesforce: sync rules, baselines and picklist errors
Read the sync rule on the field, understand the first-sync baseline, then check types, picklists and where HubSpot lists sync errors.
Troubleshooting guide
A Zap created the record twice: find which of five causes it was
Count the runs, then check for a second Zap on the same trigger, a self-trigger, a replay and a plain create step before you change anything.
Troubleshooting guide
A Zap stopped or shows Errored or Halted: what each status means and what to replay
Read the run status first, understand why a Zap turns itself off, and know what a replay repeats and why error emails can arrive hours late.
Troubleshooting guide
A Make scenario stopped on one record: error handlers and incomplete executions explained
What Make does by default when a module fails, what the five error handlers do, why a route that only sends a message skips the error, and why a stored incomplete execution can hold back the next run.
Troubleshooting guide
A scheduled report arrived at the wrong time or covered the wrong days
Find out which clock your automation tool uses, fix the reporting period in one place, and test across a clock change instead of assuming.
Troubleshooting guide
An n8n webhook works while you watch but not afterwards: test and production URLs
The Webhook node has two addresses with different rules. See which one your sender uses, how to read production runs, and how to be told when one fails.
Platform
Zapier automations: what repeats, what stops and who is told
The documented behaviours behind duplicate records, switched-off Zaps, late alerts and scheduled runs, and which outcome fits each problem.
Platform
Make scenarios: default failure behaviour, error routes and who is told
What Make does when a module fails, how error handlers and incomplete executions change it, and which outcomes cover one bad record or missing alerts.
Platform
Airtable bases: automations that fail or skip records, and tables that repeat themselves
Documented causes of failed and skipped automation runs, limits that count failed runs, and how linked records match, with the outcomes that fit each.
Platform
HubSpot lead flow: duplicates, owners and the Salesforce sync
How HubSpot matches contacts and companies, assigns owners, and syncs mapped fields with Salesforce, and which outcomes fix duplicates, routing and field reverts.
Troubleshooting guide
Converting an ERP export for a store import: decimal commas, day-first dates, codes and rejects
Why hand-editing an ERP export produces different files on different days, and how explicit number, date and code rules, exact decimal arithmetic and a reject file make the conversion repeatable.
Inspectable example
Synthetic price list: a page-by-page row count that finds two mistakes a matching total hides
An invented three-page price list shows why rows are counted per page. A first extraction matches on the total, 14 of 14, while page 1 is a row short and page 2 has an extra row.
Inspectable example
Synthetic merged-cell report flattened: nine rows in, five records out, every total reconciled
An invented printed-style sales report with merged region labels, subtotal rows and a spacer becomes a flat five-record table, with a reconciliation showing 9 original rows = 5 records + 4 removed.
Inspectable example
Synthetic quotation: why the same three lines total 4.38 or 4.39 depending on the rounding rule
Three invented lines of 1.30 plus a 12.5 per cent add-on give 4.38 if the add-on is rounded per line and 4.39 if it is rounded on the total. The rule must be written down.
Inspectable example
Synthetic rename manifest: three clean renames with matching checksums and four held names
An invented seven-file folder shows a dry run and a manifest with a row for every file, with three renamed files whose checksums match, and four held, a pair of names that differ only in letter case, a reserved device name and a name ending in a period, all listed, not guessed.
Inspectable example
Synthetic date column: which rows a rule can settle, and which must stay on the ambiguity list
Nine invented entries show day-first and month-first typing, a two-digit year, a row where only one reading is possible, an impossible date and a four-year shift, with the decision and reason for each.
Platform
PDF documents: getting data, forms and searchable text out of office files
For office managers and administrators with PDF price lists, filled forms and scans: how to tell which kind of PDF you have, how to check what is extracted and where a paid, checked job fits.
Platform
Microsoft Excel workbooks: repair, tidy and make them reliable
For administrators and small businesses who rely on Excel: where workbooks go wrong, the order to diagnose them in, and the checked, fixed-scope jobs that repair formulas, flatten layouts and clean dates and duplicates.