This guide explains what integration and API errors mean, which Phantoms they typically affect, and how to identify the correct troubleshooting steps.
What these errors mean and how they appear
Integration and API errors occur when a Phantom interacts with an external system or automation tool and the request fails.
These errors are not caused by:
- Incorrect input formatting
- Session cookie expiration
- Platform rate limits
- Storage limits
- Runtime constraints
They are triggered when:
- An external API request is misconfigured
- A Phantom ID or parameter is incorrect
- A third-party service is temporarily unavailable
- An automation tool (Make, Zapier, n8n) sends incorrect data
- An automation tool triggers multiple launches simultaneously
In some cases, external tools can force several Phantom launches at the same time (for example, when configured to run “once per item” instead of “once per execution”).
These errors typically appear:
- During an API-triggered launch.
- When a Workflow step depends on an external tool.
- After the Phantom attempts to send or retrieve data via API.
Common integration and API errors
The table below maps common runtime messages to their corresponding troubleshooting guides.
| Error message shown in logs | What it means | Phantoms typically impacted | Troubleshooting guide |
|---|---|---|---|
| Phantom runs multiple times when triggered by n8n | The automation tool is configured to trigger once per item instead of once per execution | API-triggered Phantoms (n8n) | How to Fix a Phantom that Runs Multiple Times when Triggered by n8n |
| No contact has been updated in your CRM | The CRM integration didn’t push or update data successfully | CRM-connected Phantoms | How to Fix the “No contact has been updated in your CRM” Error |
| Email Discovery Temporarily Unavailable | The external email provider is temporarily unavailable | Email enrichment Phantoms | How to Fix the “Email Discovery Temporarily Unavailable” Error |
*The examples above are common cases. Any Phantom launched through an external automation tool or dependent on a third-party service may encounter similar integration-related issues.
Operational next steps
If you encounter an integration or API error:
- Verify that the correct Phantom ID is used.
- Double-check field names and required parameters.
- Confirm the JSON structure is valid.
- Ensure the automation tool is configured correctly (for example, “run once for all items” in n8n).
- Avoid triggering multiple launches simultaneously through loops or per-item execution.
- Relaunch only after correcting the integration configuration.
- Test your request directly in the PhantomBuster developer page (API Hub) to confirm your settings and payload are correct before relaunching through your automation tool.
If a third-party service is temporarily unavailable, wait before relaunching as it consumes execution time without resolving the issue.
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.