Connect Apify for supported external data-collection workflows
Use your own Apify account when a BeKnow workflow requires a supported actor or external dataset.
What this integration does
Apify is an optional BYOK integration for selected acquisition jobs. Its role must be stated by the workflow that invokes it; connecting a key alone does not trigger crawling or spend.
Run explicitly supported external data jobs from a user-owned account.
Keep external collection modular and under provider-level cost control.
Data BeKnow can use
- Run identifier
- Dataset items
- Job status
- Provider error details
Where BeKnow uses it
- Supported acquisition jobs
- External dataset import
- Workflow-specific enrichment
How to connect
- 1
Create an API token
- 2
Connect it in integrations
- 3
Start a supported workflow
- 4
Monitor provider status and cost
What you need
An Apify account, API token and access to the required actor or dataset.
Who pays for usage
Runs and storage are billed by Apify under the user's plan.
Frequently asked questions
Does BeKnow run any Apify actor?
No. Only actors and datasets explicitly supported by a BeKnow workflow should be invoked.
Does adding the token consume credits?
No. Provider usage starts only when an authorized workflow executes a job.