What to Ask Leina to Do with Knock
Copy a prompt, add your details, and send it to Leina in your connected team chat.
Send a run request to a configured workflow using specified recipients and data.
Trigger Knock workflow [key] for recipient IDs [IDs] with data [values]. Use idempotency key [unique key] for this request and report the workflow run ID.
Get Started with Knock
-
Connect Your Account
Connect a Knock Secret API Key from the dashboard API keys page.
-
Try a Task
Tell Leina what you need in your team chat. Include the source, destination, and expected result.
Set Up Leina in Your Chat → -
Check the Result
Review the result and any changes in the connected app.
Supported Knock Capabilities
The connection reads, identifies, or deletes Knock users and triggers existing workflows. A workflow run ID confirms the request rather than delivery to every channel.
- Users and notification workflows
-
List and read users, create or update their identity and preferences, delete users, and trigger workflows.
- List Users
- Get User
View All 5 Actions
- List Users
- Get User
- Identify User
- Delete User
- Trigger Workflow
Frequently Asked Questions
Can a trigger identify a new recipient?
Recipients can be existing user IDs or inline identification details. User identification is also available as a separate operation.
How can I avoid duplicate requests when retrying?
Reuse the same idempotency key for the same intended workflow request.
Does a run ID prove the notification was delivered?
No. It identifies the accepted workflow request. These actions do not inspect subsequent delivery status.
Your AI employee for Knock
Tell Leina what you need in your team chat. Include the source, destination, and expected result.