Setup and data input errors occur when a Phantom checks your configuration before performing any actions and finds a problem, such as an incorrect URL, empty spreadsheet, missing required field, or wrong column mapping. The Phantom usually stops immediately. Match the exact error message from your logs to the table below to find the right troubleshooting guide. If the issue persists, pause the Phantom, fix or replace the input, and relaunch - avoid relaunching repeatedly with the same invalid data.
What these errors mean and how they appear
Setup and data input errors happen when a Phantom checks your configuration and input before it performs any actions on the target platform.
They're usually triggered by:
- Incorrect URL formats
- Empty or misconfigured spreadsheets
- Missing required fields
- Wrong column mappings
- Workspace validation issues
- Incorrect API arguments
When one of these checks fails, the Phantom often stops immediately, before processing any profiles or items.
Common setup & data input errors
The table below maps common runtime messages to their corresponding troubleshooting guides.
Some log messages may appear even when a launch is successful. They usually mean the automation had nothing new to process.
| Error message shown in logs | What it means | Phantoms commonly impacted | Troubleshooting guide |
|---|---|---|---|
| Invalid input | The provided URL, file, or value does not match what the Phantom expects | LinkedIn Search Export, LinkedIn Profile Scraper, Sales Navigator Search Export, CRM Phantoms | How to Fix Automation Input Errors |
| Empty input | The input source contains no data to process | CRM sync Phantoms, LinkedIn Leads automations | How to Fix Automation Input Errors |
| Input already processed | The Phantom has already processed this input and is skipping duplicates | Most Phantoms using spreadsheets or lists | How to Fix Automation Input Errors |
| We've already retrieved all results from that search | The Phantom ran successfully but didn't find any new results to extract from the search. | Search-based Phantoms (e.g., LinkedIn Search Export, Sales Navigator Search Export) | How to Fix Automation Input Errors |
| We found some invalid LinkedIn profile URLs in your spreadsheet | The Phantom is reading the wrong column or invalid profile URLs | LinkedIn outreach and invitation Phantoms | How to Fix the "We found some invalid LinkedIn profile URLs in your spreadsheet" Error |
| URL isn't a valid LinkedIn article | The post URL format is incorrect or not a direct LinkedIn post link | LinkedIn Auto Commenter and post-based Phantoms | How to Fix the "URL isn't a valid LinkedIn article" Error |
| Could not validate data | Workspace validation failed during setup | Workspace creation | How to Fix the "Could not validate data" Error When Creating a Workspace |
Operational next steps (based on the type of automation)
If you encounter repeated setup or input errors, adjust how you manage your input and relaunches so you don't waste execution time on the same failing setup.
If you're using a standalone Phantom
- Pause the Phantom before modifying input.
- Feed the Phantom with new input (for example, a new search URL or a new list of profiles).
- Avoid relaunching multiple times with the same invalid, empty, or already-processed source.
- If testing outreach or extraction strategies, create a separate Phantom to compare results.
Repeatedly launching with the same incorrect input can consume execution time without producing results.
If you're using a Workflow
Workflows process multiple steps in sequence and are more sensitive to input and launch structure.
- Don't feed new data into a running Workflow.
- Avoid modifying the input mid-run.
- If you need to test new search URLs or outreach messages, create a new Workflow instead of editing the current one.
- For outreach Workflows, duplicate the Workflow and test each variation separately instead of editing and relaunching the same one.
-
Workflows can't be launched directly via the PhantomBuster API. If you attempt to trigger a Workflow via API, it may cause configuration errors and will continue running on its default schedule, not as an on-demand API trigger.
- If you need API-based automation, recreate the Workflow logic by chaining individual Phantoms via API and passing result files between them.
Repeated launches with the same incorrect structure can consume execution time without producing results.
How to resolve them
Use the exact error message shown in your logs and match it to the table above.
Open the linked troubleshooting article for detailed, step-by-step instructions tailored to that message. You can find additional input-related troubleshooting guides in the same section.
If you're unsure how to locate or read the error message:
- Read How to Troubleshoot Phantoms Using Logs
- Or How to Troubleshoot Errors in Workflows if you're using a Workflow.