Specify the workflow key, recipients, and message data so AI can request the notification run you intend.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Send a run request to a configured workflow using specified recipients and data.
/oo Knock: 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.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a Knock Secret API Key from the dashboard API keys page.
Connect Knock →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
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.
List and read users, create or update their identity and preferences, delete users, and trigger workflows.
List Knock users with cursor pagination.
Leina 
Wanta 
knock.list_users Retrieve a Knock user by user ID.
knock.get_user Create or update a Knock user with identification data.
knock.identify_user Permanently delete a Knock user and associated data.
knock.delete_user Trigger a Knock workflow for one or more recipients and return the workflow run request ID.
knock.trigger_workflow No matching tools.
Recipients can be existing user IDs or inline identification details. User identification is also available as a separate operation.
Reuse the same idempotency key for the same intended workflow request.
No. It identifies the accepted workflow request. These actions do not inspect subsequent delivery status.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.