G2

Om M.

Founding Engineer

Computer Software

Small-Business (50 or fewer emp.)

10/13/2026

"Effortless, Code-First Notification Workflows"

5/5

What do you like best about Knock?

I like that Knock keeps my notification workflows alongside my code and helps me manage them across development, staging, and production, so I don’t have to version notifications separately or keep going back to a dashboard. I especially like the Knock CLI and its integration with AI agents. I can keep workflows in a shared repository, have agents draft and push notifications for a feature, test them in development or staging, and promote them to production with the CLI. That means less manual effort and helps avoid wrong notifications or agents using the wrong context. Setup was pretty easy with the Knock skill and AI agents: I could use one prompt, create an API key, and create workflows with the CLI. Knock also solved the chaos of managing notifications manually and the delivery hurdles we had. I don’t have to think much about notification-related things because Knock handles them simply and easily. I find it a very polished product and a great tool for developers who manage things with code or infrastructure as code. Review collected by and hosted on G2.com.

What do you dislike about Knock?

I had some difficulty finding things in the dashboard at first, like where the channels and settings were, since settings are under the profile section. I think the basic dashboard navigation could be improved for users. Other than that, everything is fine. Review collected by and hosted on G2.com.

What problems is Knock solving and how is that benefiting you?

I use Knock to manage notifications alongside my code, with versioning across development, staging, and production, instead of manually managing them in a dashboard. Its CLI keeps workflows in my repo so agents can draft and test notifications before I promote them, helping avoid wrong notifications or context. Review collected by and hosted on G2.com.