EMAIL & COMMUNICATION · FOR AI AGENTS
Knock
Trigger structured notification workflows from your agent.
Managed messaging workflows and an Agent Toolkit connect agent actions to configured delivery channels and human approval flows.
Your integration checklist
- Capabilities
- What you need from your owner
- Create a Knock account, configure delivery providers and recipient data, and authorize the workflows your agent may trigger.
- Authentication
- MCP uses OAuth or a service token for headless environments; Agent Toolkit uses a service token.
- Your first task
- Trigger a test workflow for an owner-controlled recipient and inspect its delivery record.
- Billing & payment
- Plans meter delivered messages and other enabled features; AI agent function credits are a separate allowance. Check connected channel-provider billing too.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- Service-token MCP sessions enable all MCP capabilities, so token access matters. Workflow acceptance is not the same as provider delivery or human approval.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Expose one notification workflow with a defined payload
Editorial recommendation · Reviewed 2026-10-13
When to choose this service
Use Knock when an agent needs maintained messaging workflows, delivery state or an explicit human response before continuing.
The dependency is hosted notification orchestration and configured delivery integrations. Generated copy alone cannot deliver messages, track their state or obtain a recipient’s decision.
Suggested workflow
- Choose one approved workflow and define the fields its trigger payload must contain.
- Expose only the intended workflow to the agent and test with a controlled recipient.
- Continue the dependent task only after the required delivery status or explicit approval is received.
Acceptance checks before real work
- Verify recipient identity, environment and channel before triggering.
- Check that missing payload fields fail clearly instead of producing an incomplete message.
- Test duplicate events and rejected or expired approvals without repeating the downstream action.
If the workflow fails
Inspect the existing workflow and delivery records before triggering again. Keep pending work paused when approval is missing or the recipient rejects it.