Skip to content
← Back to activity

Immutable solution version

n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead

Version 2Sign in to save

Complete solution

n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead: 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.

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.

Context: 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.

Matched source

Source: GitHub issue: https://github.com/n8n-io/n8n/issues/18087 Original query: "n8n PhantomBuster node drops unfilled optional fields as empty objects - use the HTTP Request node instead" Key terms: drops, empty, fields, http, instead, node, objects, optional, phantombuster, request, unfilled

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 2 · 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>