The "Your Phantom argument isn't valid" or "Invalid argument" error means the input provided to your Phantom doesn't match what the automation expects. To fix it, open the Input step and verify the input format matches what's required (for example, a Sales Navigator search URL instead of a regular LinkedIn URL). If you're launching via API or n8n, double-check field names (e.g. profileUrl not profileUrls), include all required fields like sessionCookie and spreadsheetUrl, and confirm the JSON body is correctly formatted. Switch to JSON view from the Input step's three-dot menu to debug directly.
Why you're seeing this
This error means the input provided to a Phantom or Workflow doesn't match what the automation expects. It can happen whether you launch the automation manually or through an automation tool like the API or n8n.
You might see messages like:
- "Invalid argument."
- "Your Phantom argument isn't valid."
Typical causes include:
- Entering the wrong type of URL or value in the Input step (e.g. pasting a LinkedIn profile URL where a search URL is required).
- Missing, misspelled, or incorrectly formatted fields.
- For API or n8n setups:
- Using incorrect field names (e.g. profileUrls instead of profileUrl).
- Omitting required fields like sessionCookie or spreadsheetUrl.
- Submitting misformatted JSON or the wrong structure.
Examples:
- LinkedIn Search Export: A profile URL was submitted instead of a LinkedIn search URL.
- Sales Navigator Search Export: A regular LinkedIn URL or list URL was submitted instead of a Sales Navigator search URL.
How to fix it
-
Check the expected input format:
- Go to the Input step in your automation setup.
- Or look at the "What you give" section on the Automation Overview page.
- Make sure the input matches exactly what's required (e.g. Sales Nav search URL, LinkedIn search URL).
-
(API/n8n only) Verify argument names and required fields:
- Double-check spelling of field names (e.g. profileUrl not profileUrls).
- Include all required fields (sessionCookie, spreadsheetUrl, or headers).
- Confirm the JSON body is correctly formatted.
-
(API/n8n only) Debug in JSON view:
- In the Phantom Input step, click the three-dot menu on the top right.
- Select "Switch to JSON view."
- Review and correct the input structure directly.
-
Save and relaunch:
- After making corrections, click Save and Launch to rerun the automation with valid input.
Frequently asked questions
What does "Your Phantom argument isn't valid" mean?
The input provided to your Phantom or Workflow doesn't match what the automation expects. Common causes include the wrong type of URL, missing required fields, or for API and n8n setups, misspelled field names or malformed JSON.
How do I check what input format my Phantom requires?
Open the Input step in your automation setup, or check the "What you give" section on the Phantom's Automation Overview page. This shows the exact format expected, such as a LinkedIn search URL or Sales Navigator search URL.
What are the most common API and n8n field name mistakes?
Using plurals when singular is required (profileUrls instead of profileUrl), omitting required fields like sessionCookie or spreadsheetUrl, or submitting incorrectly structured JSON. Each Phantom has its own expected field names.
How do I debug my Phantom input in JSON view?
In the Phantom's Input step, click the three-dot menu in the top right corner and select Switch to JSON view. You can then review and correct the input structure directly.
If the error keeps showing up
If you still see the error after correcting your input:
- Take a screenshot of your Phantom or Workflow Input step.
- Copy the exact URL or payload you're using.
- Get in touch with our Customer Care Team.