Missing leads between web form and CRM: reconcile, don’t guess

Diagram: enquiries traced by ID across form entries, the partner sheet and the partner CRM, showing matched, hand-keyed and missing records.

A partner told a South America travel company its leads were going missing daily. Reconciling every enquiry across form, partner sheet and CRM showed their own team had been hand-keying most of what the old integration dropped, and caught a live bug in the new engine.

Changing a live n8n workflow without testing on real partners

Diagram: a workflow JSON file in git passing five checks before going live: simulator, n8n parser, failing on the old version, a live-versus-git diff and a smoke test.

A gate in a newly live n8n lead router would have held back any enquiry with a blank last name. The fix shipped the same morning, through a local simulator, n8n’s own parser, a mutation check, a diff against the live copy and a smoke test that reached no partner.

Writing Leads into a Salesforce org you don’t own

Diagram: a routing engine creating a Lead inside a partner's Salesforce org it cannot see into; create and read back allowed, delete blocked.

Delivering leads from an n8n routing engine into a partner’s Salesforce org: client_credentials on My Domain, a dependent picklist decoded from validFor, picklists that accept anything, and test records that can never be deleted.

Every test green, every Salesforce write failing: scope parameter not supported

Diagram: six passing test checks beside a live token request whose scope parameter Salesforce rejects with HTTP 400, above a cutover-day timeline.

The day an n8n lead router went live, Salesforce answered its token request with “scope parameter not supported” and every write failed, while every test stayed green. The cause, why no offline test could see it, how the fix was proven with a write that reached nothing but Salesforce, and why I called off the replay.

From 51 Pabbly Connect workflows to three in n8n

Diagram: 51 tangled lead-routing workflows, ten marked amber where they contradicted the rule, converging into one system with three output lanes for web forms, phone calls and live chat.

A South America travel company’s lead routing had grown into 51 active Pabbly Connect workflows that no longer matched the rule they were meant to follow. It now runs as one tested rule in n8n, proven in shadow on real leads, with every lead logged.

Eight Undocumented Traps in the Shepherd Veterinary Open API

Image representing a Raven (Ryzodus AI) flying over a farm with sheep

Eight undocumented behaviours in Shepherd Veterinary Software’s Open API, found while building a two-way sync for a veterinary practice client — including a full-replace update endpoint that silently deletes any collection you leave out of the body. All verified against the live production API, including writes.