[ Communication ]
Knock integration for your workflows.
Connect Knock to Collabase once and use 7 actions in your workflows. No code needed, hosted in Switzerland.
Knock in Collabase
Connect Knock to Collabase once and use 7 actions in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Notification infrastructure for developers. Manage users, trigger workflows, and track messages.
How to connect it
- Open the integrations in the workspace settings.
- Choose Knock and connect your account.
- Add a trigger or an action to the workflow.
Knock triggers
Knock does not start a workflow on its own. You use its actions after any other trigger.
Knock actions
| Name | Description | Fields |
|---|---|---|
| Trigger Workflow | Trigger a Knock notification workflow for one or more recipients. |
|
| Identify User | Create or update a user in Knock. |
|
| Get User | Retrieve a user from Knock by their ID. |
|
| Delete User | Delete a user from Knock by their ID. |
|
| Get Message | Retrieve a Knock message by its ID. |
|
| List Messages | List Knock messages with optional filters and pagination. |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ Communication ]
Related integrations
Tools that often share a workflow.
Questions about Knock
What can I automate with Knock in Collabase?
Knock brings 7 actions and 0 triggers, for example Trigger Workflow, Identify User, Get User, Delete User and 3 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect Knock to Collabase?
You open the integrations in the workspace settings, choose Knock and connect your account once, using an API key. After that all triggers and actions are available in the workflow.
Does the Knock integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.