Apify in BeKnow
An optional external provider is separate from the core memory.
What this integration does
An optional external provider is separate from the core memory. Saving credentials does not make retired SEO, AI visibility, writing or image workflows available. Use a key only when a currently available function explicitly requires it.
Optional provider
Check the source, collection date and scope before using a result.
Data BeKnow can use
- An optional external provider is separate from the core memory.
Where BeKnow uses it
- An optional external provider is separate from the core memory.
How to connect
- 1
Check the requirement shown by the specific available function before adding a key.
- 2
An optional external provider is separate from the core memory.
What you need
Check the requirement shown by the specific available function before adding a key.
Who pays for usage
Project memory and data imports do not require an AI model key. A compatible external AI client may have its own costs. BYOK applies only to available functions that actually call an external provider.
Frequently asked questions
Current scope?
An optional external provider is separate from the core memory. Saving credentials does not make retired SEO, AI visibility, writing or image workflows available. Use a key only when a currently available function explicitly requires it.
Do I need an AI subscription?
Project memory and data imports do not require an AI model key. A compatible external AI client may have its own costs. BYOK applies only to available functions that actually call an external provider.