Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

PhantomBuster

Automate your web scraping and web automation tasks

CategoryMarketing
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect PhantomBuster with Flows360

Automate your web scraping and web automation tasks

Use the PhantomBuster connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 1 trigger.

Available actions

  • Launch Phantom
  • Custom API Call

Available triggers

  • New Output

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: PhantomBuster
  • Package: @activepieces/piece-phantombuster@0.2.0
  • Exact artifact digest: sha256:3163c8e4e98e79978b4cc836377e36e8559845bb5372db99488950cb559013aa
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Launch Phantom (launchPhantom), Launch a Phantombuster agent and add it to the execution queue Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Output, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects3
Supported actions2
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Launch Phantom Yes No Launch a Phantombuster agent and add it to the execution queue
Custom API Call Yes No Make a custom API call to a specific endpoint
New Output Yes No webhook trigger declared by the pinned package.

Supported actions

Launch Phantom · Read

Launch a Phantombuster agent and add it to the execution queue

launch_phantom · Risk: low · Retry: safe

Inputs

  • agentId · string · Required, Select the Phantombuster agent to use
  • waitForOutput · boolean · Optional, Wait until the agent execution completes and output is available
  • argument · object · Optional, Optional argument to pass to the agent
  • maxRetries · number · Optional, Maximum number of retries if the agent fails
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Output · Webhook

Trigger when a new output is generated by a Phantombuster agent

Inputs

  • agentId · string
  • markdown · string

Setup

Setup

  1. Add the PhantomBuster connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-phantombuster@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required PhantomBuster connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-phantombuster@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com