Bug Description

Hi Team,

Anna from the PhantomBuster, Customer Care team here.

I wanted to share a bug we noticed when dealing with users who automate their actions via n8n.

We discovered that when the optional fields in PhantomBuster node aren't filled in by the user - the argument which we receive is empty {}.

The users are only able to solve it when contacting PhantomBuster Support where we advise them to use HTTP Request node instead to make things work smoothly.

Main issue on our end "Missing cookie" which mean that the cookie value, which is mandatory for most of our Phantoms isn't passed from n8n to the Phantom.

To Reproduce

1. Use PhantomBuster account (create a free trial account if needed).

2. Connect with n8n via API Key (generated under Workspace settings).
3. Create a Phantom on your dashboard (.e.g. LinkedIn Profile Scraper).
4. Use the PhantomBuster node in n8n and fill in only required fields.
5. Leave optional fields empty.
6. Check Phantom to see if there's an error.

Expected behavior

Empty fields should not be passed as part of a payload at all OR n8n eventually, it would be great if the user could a response about missing field from PhantomBuster (harder to achieve tho I think).

Debug Info

Debug info

core

• n8nVersion: 1.100.1
• platform: docker (cloud)
• nodeJsVersion: 22.16.0
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: community
• consumerId: 00000000-0000-0000-0000-000000000000

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 2500 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/138.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-08-07T11:50:16.464Z

Operating System

Windows 10

n8n Version

1.100.1

Node.js Version

Phantombuster node version 1 (Latest)

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud