Immutable solution version
n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead
Complete solution
n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead. PhantomBuster's own support team filed this bug and their workaround is to use n8n's generic HTTP Request node instead of the native PhantomBuster node. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
PhantomBuster's own support team filed this bug and their workaround is to use n8n's generic HTTP Request node instead of the native PhantomBuster node. If your PhantomBuster Phantoms fail with 'Missing cookie' when launched from n8n, the cookie probably never left n8n: their PhantomBuster node sends unfilled optional fields as empty {} arguments, so the session cookie you configured gets dropped.
Fix
PhantomBuster's own support team filed this bug and their workaround is to use n8n's generic HTTP Request node instead of the native PhantomBuster node. Expected: You get the expected result; the problem is gone.
When to use
- You are dealing with this situation.
- The symptom matches: n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead.
When NOT to use
- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported per the linked source. Source: GitHub issue: https://github.com/n8n-io/n8n/issues/18087.
Variant phrasings
n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead
Why it happens
n8n issue 18087, filed by Anna from PhantomBuster's own Customer Care team: when optional fields in n8n's PhantomBuster node are not filled in, n8n sends them to Phantoms as empty {} arguments. On PhantomBuster's end this surfaces as 'Missing cookie' - the mandatory session cookie never makes it from n8n to the Phantom. Their documented workaround: use n8n's generic HTTP Request node instead of the native PhantomBuster node to make things work smoothly.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Source
GitHub issue: https://github.com/n8n-io/n8n/issues/18087
Evidence
Source: n8n issue 18087, filed by Anna from PhantomBuster's own Customer Care team: when optional fields in n8n's PhantomBuster node are not filled in, n8n sends them to Phantoms as empty {} arguments. On PhantomBuster's end this surfaces as 'Missing cookie' - the mandatory session cookie never makes it from n8n to the Phantom. Their documented workaround: use n8n's generic HTTP Request node instead of the native PhantomBuster node to make things work smoothly.
Verified resolution: If your PhantomBuster Phantoms fail with 'Missing cookie' when launched from n8n, the cookie probably never left n8n: their PhantomBuster node sends unfilled optional fields as empty {} arguments, so the session cookie you configured gets dropped. PhantomBuster's own support team filed this bug and their workaround is to use n8n's generic HTTP Request node instead of the native PhantomBuster node. It is a node-level serialization bug, not your credentials.
Source URL: https://github.com/n8n-io/n8n/issues/18087
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_kP_L1MY5EXvVGpUy0v3dPg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead <span>— Vectle</span></a>