Integration

Knock integration

Knock is a notification infrastructure platform for developers. Build sophisticated notification experiences with workflows, multiple channels (email, push, SMS, in-app, Slack), user preferences, and real-time feeds. Features include batching, throttling, timezone delivery, and rich notification templates. Perfect for SaaS products, marketplaces, and applications requiring complex notification logic.

Connect Knock How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Knock.Built from the 19 Knock tools below, on the connection you add once.

Common Knock use cases

listing teams
GDPR compliance
mark all as read
user registration sync
viewing object details
building preference UIs
displaying user profile
removing deprecated teams
clearing old notifications
team membership management

What you can do with Knock

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Message, 5 operations

batch_mark_messages_archivedBatch mark messages archivedPOSTBatch archives Knock messages. Hides messages from the default feed view.
batch_mark_messages_readBatch mark messages readPOSTBatch marks Knock messages as read. Updates read status for multiple messages at once.
batch_mark_messages_seenBatch mark messages seenPOSTBatch marks Knock messages as seen. Updates seen status for multiple messages at once.
get_messageGet messageGETRetrieves a single Knock message. Returns delivery status, engagement data, and associated metadata.
list_messagesList messagesGETLists Knock messages with filtering and pagination. View notification delivery across all channels.

Notification object, 4 operations

delete_objectDelete objectDELETEPermanently deletes a Knock object from a collection.
get_objectGet objectGETRetrieves a specific Knock object. Returns the object with all properties and metadata.
list_objectsList objectsGETLists all Knock objects in a collection with pagination.
set_objectSet objectPUTCreates or updates a Knock object. Objects represent non-user entities that can receive notifications like teams or projects.

User, 4 operations

delete_userDelete userDELETEPermanently deletes a Knock user. Removes all user data including preferences and notification history.
get_userGet userGETRetrieves a Knock user's profile. Returns contact details, properties, and metadata.
identify_userIdentify userPUTCreates or updates a Knock user. Users receive notifications and have properties used for personalization and routing.
list_usersList usersGETLists all Knock users with cursor-based pagination.

Preference, 2 operations

get_user_preferencesGet user preferencesGETRetrieves a Knock user notification preference set. Returns channel, workflow, and category-level settings.
set_user_preferencesSet user preferencesPUTUpdates Knock user notification preferences. Control channel, workflow, and category-level settings.

Workflow, 2 operations

cancel_workflowCancel workflowPOSTCancels a pending Knock workflow run. Stops notifications that haven't been delivered yet.
trigger_workflowTrigger workflowPOSTTriggers a Knock notification workflow for recipients. Orchestrates multi-channel delivery with batching, delays, and conditions.

Feed, 1 operation

get_user_feedGet user feedGETRetrieves the Knock in-app feed for a user. Returns paginated notifications with read/seen status and metadata.

Subscription, 1 operation

add_subscriptionsAdd subscriptionsPOSTAdds subscribers to a Knock object. Subscribers receive notifications sent to the object.

Use Knock from Claude Code, Cursor or Codex

Connect Knock in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Knock operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Knock

Create your workspace
Sign up free. Nothing to install.
Connect Knock once
Add your Knock connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Knock integration FAQ

What can you do with the Knock integration?

LiveContext exposes 19 operations on Knock, covering message, notification object, user and preference. Common uses include listing teams, GDPR compliance and mark all as read.