Zapier in BeKnow
Receive events through a configured HTTP request with a dedicated key.
What this integration does
Receive events through a configured HTTP request with a dedicated key. Duplicate events are checked and access can be revoked. This is an inbound endpoint, not a native marketplace app or a two-way automation.
Incoming events
Check the source, collection date and scope before using a result.
Data BeKnow can use
- Receive events through a configured HTTP request with a dedicated key.
Where BeKnow uses it
- Inspect imported records in the connection’s Data view.
- Read records and import history through authorised MCP operations.
How to connect
- 1
A configured HTTP step and the dedicated BeKnow connection key.
- 2
Receive events through a configured HTTP request with a dedicated key.
What you need
A configured HTTP step and the dedicated BeKnow connection key.
Who pays for usage
Memory and these reads do not require a BeKnow model key. Your external account, API access and any AI client follow their own service terms.
Frequently asked questions
Current scope?
Receive events through a configured HTTP request with a dedicated key. Duplicate events are checked and access can be revoked. This is an inbound endpoint, not a native marketplace app or a two-way automation.
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.