LoginSign Up
← Back to all sparks
K

Knock

INFRA · APIS
Velocity6.3

Knock is pushing its agent into more surfaces while making notification config a no-engineering job.

notificationsagentic-toolingno-code-configintegrationsdeveloper-platformaudiences
◆Current state
Knock, a notifications-infrastructure platform, is building two parallel tracks: an agent that can create and manage messaging resources from inside tools like Slack, and a steady stream of dashboard-driven features that move configuration work off engineers. Recent releases span a hosted preference center, dynamic audiences, new data sources, and template tooling. The product is widening from a developer API toward a self-serve control surface.
◆Where it's heading
The direction is toward less engineering involvement per change — agents, dashboard-built audiences, and hosted end-user UI all shorten the code path. Integrations like the Shopify data source extend Knock's triggers into commerce events, broadening what notifications can be driven by. The agent and the dashboard keep absorbing tasks that previously required custom code.
◆Prediction
The next moves likely deepen the agent (more surfaces or skills) and add further data sources, continuing the shift toward dashboard- and agent-driven configuration over hand-written integration code.

◆Recent moves

  1. 15d ago

    Preference center

    A hosted preference center extends Knock's no-engineering push: teams configure end-user notification preferences from the dashboard rather than building and hosting that UI themselves. It fits the broader move toward self-serve control surfaces.

  2. 23d ago

    New partial input types

    Color picker, number, and list inputs give finer control over partial styling and repeatable content. Incremental tooling that supports the template and design-system work rather than changing direction.

  3. 25d ago

    Knock agent for Slack

    ⚡ SPARK

    Bringing the agent into Slack is the clearest expression of Knock's agentic direction — engagement resources can be created, updated, and scheduled without opening the app. It extends the agent from a Knock-native tool to where teams already work.

  4. 1mo ago

    Shopify data source

    A Shopify connector lets real-time commerce events drive notifications, extending Knock's triggers into the ecommerce stack. A meaningful integration that broadens input sources without reshaping the platform.

  5. 1mo ago

    Reusable request input schemas

    Defining the data each reusable step expects reduces guesswork when mapping workflow payloads. A developer-experience refinement that supports the reusable-step model.

    View source ↗
  6. 1mo ago

    Dynamic audiences

    ⚡ SPARK

    Dynamic audiences add a targeting primitive that's versioned, previewable, and promotable across environments — and buildable from the dashboard, CLI, or agent. It pushes Knock past pure delivery toward audience management, reinforcing both the multi-surface and no-code themes.