1. Confirm the fault
Send the current field paths and at least two synthetic examples with different values and the expected outputs.
NEW · AUTOMATION RESCUE
Your webhook receives an order, but the next step reads the wrong fields. Get the corrected field mapping, n8n expressions and a portable test kit you can keep in your project and run in CI.
$19 USD service price · one mapping · 2–5 examples · up to 12 fields
Start free eligibility checkOne-Time Payment. No charge for unsupported cases. Payment options follow the existing regional checkout policy.
Send the current field paths and at least two synthetic examples with different values and the expected outputs.
Only a uniquely identifiable repair receives a quote. Review the fixed scope, then choose an eligible payment method.
After payment verification, download your mapping, expressions, before/after evidence and Replay Kit ZIP. Run its tests locally or add them to your existing CI job.
A field moved under a wrapper such as body or data, while a later workflow step still reads the old path. The service identifies a unique path that reproduces every expected value in your examples.
Outside this scope: live deployment, arbitrary workflow repair, credentials, signatures, missing events, retries, scheduling and server access. Passing the supplied examples is not proof that every future event will work. Use synthetic data only; never include customer details, passwords or tokens.
Read the troubleshooting guide · Agent integration & input example
SYNTHETIC BEFORE / AFTER
In these two fixtures, the values moved inside body. The old mapping reads from the root.
{"orderId":"order_id","quantity":"quantity"}Both fixtures fail to produce their expected fields.
{"orderId":"body.order_id","quantity":"body.quantity"}Both synthetic fixtures match their expected outputs.
{"orderId":"DEMO_A","quantity":2}The second fixture uses DEMO_B and quantity 3. Different values help distinguish a matching path.
Locally checked synthetic example, not a customer result. No live webhook or n8n workflow was executed. The eligibility check below determines whether your supplied examples identify a supported repair.
Check my mapping firstUse this service only after confirming that the webhook arrived and the later step reads the wrong field path. If the event never arrived, start with free technical triage. If signature verification fails, read the signature troubleshooting guide first. For a correct but nested payload, follow the field-mapping guide and try synthetic fixtures below.
A browser agent can discover read-only service-search tools when WebMCP is supported. No WebMCP tool starts payment, modifies an n8n workflow or accesses credentials.
FREE · NO ACCOUNT NEEDED
Use two synthetic events with different values and the outputs you expect. This builder prepares JSON in your browser; only “Run free eligibility check” sends the prepared examples to NAIF.
جهّز مثالين ببيانات وهمية. لن يُرسل النموذج حتى تضغط زر الفحص المجاني.
Use plain objects and dotted paths. Up to 12 scalar output fields. Unrelated arrays may remain in synthetic inputs (64 items per array); array indexing, scripts, customer details and credentials are not supported. Every output field needs different values across the two examples. For 3–5 examples, use Advanced JSON below.
Synthetic demo loaded. Edit the examples, then prepare your check.
A prepared test case is not an eligibility decision or a verified repair.
The example below is synthetic. Replace it with a sanitized reproduction. If the original mapping already works, or several paths could match, we will not create a paid quote.
Plain dotted paths only, for example body.order_id. Unrelated synthetic array context is accepted; no array indexing, array outputs, scripts or expressions.
No quote or payment was created. Review the examples yourself before retrying; the guidance does not change your input.
INCLUDED WITH NEW REPAIR DELIVERIES
Your repair now includes a portable Replay Kit at the existing service price. It runs without npm packages, API keys or a NAIF connection.
A JavaScript mapper, original and corrected paths, your synthetic fixtures, and a command that reports pass or failure.
node naif-repair/verify.mjs
An n8n Code snippet with required-field checks and item linking, plus a step you can add to an existing GitHub Actions job.
Add new synthetic cases and test your current mapping file. Missing fields, changed types and wrong values fail the check.
New deliveries also include a local workflow-export check. It catches a stale or changed NAIF Code snippet even when a separate mapping file still passes its examples. The receipt identifies the exact files checked.
node naif-repair/verify-workflow.mjs --workflow current-workflow.json --node-id NODE_ID --mapping current-mapping.json --fixtures current-fixtures.json
Supports one NAIF-generated JavaScript Code v2 node. Export the intended current workflow yourself and keep it local. This checks exported code and supplied examples; it does not run n8n, verify deployment, or inspect the rest of your workflow. Existing deliveries keep their original files.
Requires Node.js 22 or later. You add the files to your project and CI. Tests cover only the mapping and fixtures supplied to the runner; an unchanged copy cannot detect changes elsewhere in a live workflow. Review the n8n snippet in your own environment before use. Previously cached deliveries keep their original contents.
NAIF Gravity also documented an experimental Holocron PEM parser diagnosis: 10 original parser tests and 3 additional regression tests passed in isolation. This is separate research, not a supported repair in this $19 webhook mapping product, and not an upstream-approved fix.
Send supported mapping failures to this dedicated product and keep your client relationship. Delivery is automated; your team or agent applies the repair. Referral partners can earn 25% of eligible net verified sales under the existing program terms.
الحزمة تنشئ محليًا نسخة جديدة من ملف n8n، مع تغيير كود عقدة NAIF المحددة فقط بعد فحص أمثلة قبل/بعد. يبقى الأصل كما هو.
After checking both mappings and supplied fixtures, create a new local export copy changing one recognized NAIF Code node. Other bytes are preserved. Existing or customized node code that does not match the declared original template is refused.
No import, activation or deployment. Keep exports private: the new copy retains all original fields, including credential references and any embedded sensitive data. Read WORKFLOW-PATCH-README.md in the downloaded kit.