How to Fix a Phantom that Runs Multiple Times when Triggered by n8n

Sophie
Sophie This badge shows you’re hearing straight from the source! Team members are here to share insider tips, answer questions, and guide you through PhantomBuster with expert knowledge. They’re dedicated to helping you succeed and making sure your automation journey feels easy and exciting. PhantomBuster Official
  • Updated

A Phantom that runs multiple times when triggered from an n8n workflow is almost always caused by the n8n node being set to execute once per item instead of once for all items. The fix is to open your n8n workflow, find the node that triggers the Phantom, and change its execution mode to once for all items so the Phantom launches a single time per workflow execution.

Why you're seeing this

Your Phantom is launched multiple times instead of running once because n8n is configured to trigger it once per item.

When your workflow contains multiple items, n8n triggers the Phantom one time for each item, which causes several simultaneous Phantom launches.

How to fix it

To ensure your Phantom runs only once per workflow execution, update your n8n configuration:

  1. Open your workflow in n8n.
  2. Locate the node that triggers your Phantom.
  3. Change the execution mode from once per item to once for all items.
  4. Save your workflow.
  5. Run a test to confirm the Phantom is triggered only once.

Frequently asked questions

Why does my Phantom run multiple times when triggered by n8n?

Because the n8n node is set to execute once per item. When the workflow passes multiple items to the node, it triggers a new Phantom launch for each one. Switching to once for all items makes the node trigger the Phantom a single time regardless of how many items are in the workflow.

What's the difference between "once per item" and "once for all items" in n8n?

Once per item runs the node separately for every item in the incoming data, so if 10 items are passed, the Phantom launches 10 times. Once for all items runs the node once with all items batched together, so the Phantom launches a single time per workflow execution.

Will changing the execution mode affect the data passed to my Phantom?

Yes, but in a good way. With once for all items, all items from the previous node are bundled into a single request to the Phantom, so it processes them together instead of as separate launches. Your input data still reaches the Phantom, just in one batch rather than many.

If the error keeps showing up

If the Phantom keeps running multiple times after switching to once for all items, get in touch with our Customer Care Team. Please include:

  • A screenshot or short video of your current n8n workflow setup
  • The moment you run the workflow and how the Phantom is triggered
  • The Phantom name and a link to the duplicate runs
  • Your n8n node configuration, especially the execution mode setting

You can follow this step-by-step guide to record and share a video with our Customer Care Team.

Was this article helpful?

0 out of 0 found this helpful