← Lavori

n8n Expert Needed — Audit a Live Lead-Gen Workflow That's Silently Dropping Data

Budget: $20.0 FIXED / ⭐ 0.00 (0) India

integromat, lead-generation

We're an AI automation agency and we build n8n workflows for clients across lead-gen, CRM sync, and outreach. One of our production workflows has developed a frustrating bug, and we need a second pair of expert eyes before we keep digging ourselves. The situation: The workflow handles inbound leads end-to-end. A webhook receives the lead → an enrichment step pulls extra company/contact data via an external API → the data gets merged → it's pushed into the client's CRM → a notification goes out to their sales team on Telegram and email. On the surface everything "runs" — executions show green, no red error banners. But the leads landing in the CRM are missing fields, and roughly 1 in 4 notifications fire completely empty (no name, no company, no source). The data is clearly making it into the workflow but getting lost or overwritten somewhere in the middle. We suspect it's in how the branches merge back together, or a mapping/expression that silently returns undefined, but we haven't nailed it. What we need from you: • Review the existing n8n workflow and trace where the data actually breaks • Identify the true root cause — not a band-aid • Tell us the exact fix (which node, which setting/expression, and why) • Flag any other fragile spots you notice while you're in there • Optional quick screen-share (Zoom/AnyDesk) to confirm the fix live Our stack / context: • n8n (self-hosted on Docker) • Webhook triggers, HTTP Request nodes, Merge nodes, Set/Edit Fields, IF branching • External enrichment API (Bearer-token auth) • CRM push + Telegram Bot API + email notifications You're a fit if you: • Have real, hands-on n8n experience — not just Make.com or Zapier • Understand n8n's item/data model, merge modes, and how expressions resolve across branches • Can read an execution log and reason from evidence, not guesswork • Communicate clearly in writing This is a small, fast job (30–90 min for the right person), but we ship a high volume of these workflows and are actively looking for one reliable n8n partner to send ongoing debugging and build work to.
Apri su Upwork