Knock

Knock is notification infrastructure: you trigger a named Knock workflow for one or more recipients and Knock fans it out to email, SMS, push or an in-app feed using the channels that workflow configures.

Authentication

• API key

Actions

Generic API request. Call any Knock API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

• Get messageFetch one Knock message by id to see whether a notification was actually delivered and on which channel.
• Get userFetch one Knock user by id to read the identity Knock notifies, before triggering a workflow or updating their preferences.
• Identify userDestructiveCreate or update (identify) a Knock user, merging the supplied properties (PUT /users/{userId}, application/json).
• List messagesList Knock messages with cursor pagination (GET /messages).
• List usersBrowse the users known to Knock, to resolve a recipient id or to audit who can be notified.
• Trigger workflowDestructiveTrigger a Knock workflow for one or more recipients (POST /workflows/{workflowKey}/trigger, application/json).

Triggers

• New messageStarts when a new message is sent through a Knock notification workflow for the connected account.
• New message sent (webhook)Starts the instant Knock sends a message to a channel provider for the connected account, delivered by a webhook instead of polling the message list.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.