LoginSign Up
← Back to all sparks
K

Knock

INFRA · APIS
Velocity6.3

Knock is hardening for enterprise buyers while its agent takes over the analysis work.

notificationsdeveloper-infrastructurerbacworkflow-automationai-agentsintegrations
◆Current state
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
◆Where it's heading
Two arcs run in parallel. The infrastructure lane is buying enterprise credibility — roles, passkeys, audit-grade permissions — the checklist items that decide procurement rather than daily use. The data lane keeps widening what can trigger a workflow: product analytics from Amplitude, enriched rows from Clay, internal Slack channels as a destination. Together they push Knock from a notification API toward the messaging control plane, with the agent as the layer that explains what the plane did.
◆Prediction
Expect the roles work to continue into audit logs or scoped API keys, since granular permissions without an activity trail is an incomplete enterprise story. More data sources are likely on the same cadence, with the CRM and warehouse categories the obvious remaining gaps.

◆Recent moves

  1. 1d ago

    Custom roles and permissions

    Custom roles with per-permission granularity, replacing fixed membership tiers. It completes the enterprise access-control lane that passkeys opened a month earlier, and it is the kind of item that unblocks a procurement review rather than changing what the product does.

  2. 6d ago

    Power internal Slack alerts

    Slack workspaces become an internal destination, not just a customer-facing channel. It extends Knock's reach from notifying end users to notifying the team operating the product.

  3. 7d ago

    Category + tag management

    Tags and preference categories get dedicated dashboard pages instead of being managed inline. Housekeeping that matters at the scale where an account has enough workflows for taxonomy to become a problem.

  4. 13d ago

    Amplitude data source

    Amplitude joins Clay as a first-class data source, streaming product events, user updates, and cohort membership into Knock. Each addition moves triggering further upstream, away from the customer's own event pipeline.

  5. 20d ago

    Analytics in the Knock agent

    ⚡ SPARK

    The agent stops being an authoring aid and starts answering questions about messaging performance directly. In a feed otherwise full of infrastructure increments, this is the entry that changes what the product is for.

  6. 21d ago

    Wait for event function

    A wait-for-event step lets a workflow pause on a product or Knock event and then continue, branch, or stop. It is a real primitive rather than a convenience — it makes multi-day sequences expressible without external orchestration.