ActionPhantombusterUpdated May 2026
How do I delete a PhantomBuster agent?
Short answer: Drop the "Phantombuster → Delete PhantomBuster Agent" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
ID id | string | Required | ID |
Sample request
{"id": "{{trigger.id}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Delete PhantomBuster Agent.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Delete PhantomBuster Agent.
What does the Delete PhantomBuster Agent action do in Phantombuster?
Removes a configured Phantom (scraper agent). For cleanup of one-off scrapes after data is captured.
What inputs does Delete PhantomBuster Agent require?
Required: ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Phantombuster returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Delete PhantomBuster Agent support batch operations?
Yes. Run Delete PhantomBuster Agent inside a Loop node to process arrays. Tiny Command handles Phantombuster's rate limits automatically so you don't have to throttle manually.
More actions
Other Phantombuster actions.
Send delete phantombuster agent from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.
