LoginSign Up
← Back to all sparks
K

Knock

INFRA · APIS
Velocity6.3

Knock is rewiring notifications infrastructure to be configured by agents, not just developers.

notifications-infrastructureagent-toolingdeveloper-experienceworkflowsaudiencesagentic-config
◆Current state
Knock is methodically rebuilding its primitives — audiences, layouts, reusable steps, in-app guides — so they're versioned, environment-promotable, and addressable from an agent in addition to the dashboard and CLI. The recent run shows a clear pattern: each new feature ships with at least one agent-accessible path. Underneath, the engineering surface is also tightening, with reusable request input schemas making composability less guesswork.
◆Where it's heading
Knock is positioning its platform as agent-buildable messaging infrastructure rather than just a developer SDK. Skills, dynamic audiences, and schema'd reusable steps are the building blocks of a future where a product team agent (or Knock's own) can spin up an entire notification flow without a developer touching code. The Layouts 2.0 refresh and Guides toolbar work in parallel to harden the human surfaces that remain.
◆Prediction
Expect Knock to publish a more opinionated agent surface — likely an MCP-style server or an in-product agent that orchestrates skills against dynamic audiences. The reusable-input-schemas release is the kind of plumbing that precedes a 'build a workflow from a prompt' demo, so a higher-level natural-language workflow composer is the most probable next move.

◆Recent moves

  1. 7d ago

    Reusable request input schemas

    Reusable request steps now accept declared input schemas, so workflow payloads can be mapped against a known shape instead of guessed at. Quiet but important plumbing for the agent-composable workflow direction Knock has been pushing toward.

    View source ↗
  2. 21d ago

    Dynamic audiences

    Dynamic audiences land as versioned, previewable, environment-promotable resources buildable from the dashboard, CLI, or an agent. Brings audience management into the same governed-config pattern Knock applies to workflows and templates.

  3. 21d ago

    Dynamic audiences

    The canonical changelog entry for dynamic audiences, sibling to the feed pickup published a day later. Same shipment, different surface.

    View source ↗
  4. 28d ago

    Agent skills

    ⚡ SPARK

    Agent skills let teams package repeatable tasks as reusable commands callable from anywhere in the Knock agent. This is the most explicit signal yet that Knock sees its agent as a first-class configuration surface, not a convenience layer on top of the SDK.

  5. 28d ago

    Agent skills

    Canonical changelog publication of the Agent skills launch, sibling to the feed pickup a day later. Same release, written through twice by the changelog pipeline.

    View source ↗
  6. 1mo ago

    Layouts 2.0

    Layouts 2.0 redesigns the email layouts experience around a unified three-pane editor with clearer usage indicators, a more prominent layout selector, and dark mode. UX consolidation around a long-stable surface — fits the cadence of tightening human-facing tooling alongside the agent push.