Its very easy to use, very little learning curve. Implementation is straightforward just looking at the docs we got started in under 10 mins. Integrations with other platforms like AWS, Mailchimp, etc are there which is very good and the workflow is pretty easy to understand and use Review collected by and hosted on G2.com.

The templates and "general" outline template was not intuitive at first and sometime there are errors in workflow exection i.e. notification node failing due to 3rd party issues which are not there in the logs and not clear. Got it figured out through support but would have been better if its clearer from the start Review collected by and hosted on G2.com.

Knock is an engineering-first platform. Their API is robust, and they ship solid features at a steady pace. Review collected by and hosted on G2.com.

The only major downside to Knock is that the filtering and pagination in some of the observability views in the Knock dashboard can feel a bit limiting. At times, it’s hard to find exactly what I’m looking for. Review collected by and hosted on G2.com.

I like that Knock is easy to use, and I find the dashboard really user-friendly. It has tons of powerful features that I appreciate. Building notifications can be complex, but Knock makes it super easy to create templates and workflows. Review collected by and hosted on G2.com.

The lack of product marketing tools and support. Review collected by and hosted on G2.com.

The SDKs are easy to implement and integrate into my apps, the UI is great to set up workflows and understand how it works and the logs make it really easy to check emails are getting sent correctly and debug who got what email etc, it's really great! Workflows are well thought through for Enterprise use cases, and overall really happy, makes complex email workflows simple (not easy to do!) I also love that everything is version controlled through basically git for email, can sometimes be a bit cumbersome to remember to commit changes and push them to prod, but a really powerful and useful feature Review collected by and hosted on G2.com.

Getting better but still some of the concepts can be a bit fuzzy to me e.g. what's the difference between a workflow and layout and where if I want to change something is that in the layout or the workflow settings, but recent UI changes have made this a lot better. Review collected by and hosted on G2.com.

Knock makes it incredibly simple to manage push, in-app, and email notifications from one place. The workflows are intuitive, flexible, and save our team hours of development time. The API and SDKs are well-documented and easy to implement, which meant we could roll out new notification features quickly. Review collected by and hosted on G2.com.

The platform is very powerful, but with that comes a bit of a learning curve. Setting up advanced workflows can take some trial and error, though once you understand the structure it becomes smooth. Pricing can also feel high for smaller teams, but the value is worth it once you’re fully integrated. Review collected by and hosted on G2.com.

I appreciate how easy it is to get started using Knock. I found the documentation and examples very helpful. Knock provides a good out-of-the-box solution for in-app notifications, but there also seem to be ways to customize it as needed. I've also had a couple of interactions with Knock's customer support and got the answers I needed quickly. Review collected by and hosted on G2.com.

For my use case, I wish Knock had slightly better CI/CD integration. I want finer-tuned control over Knock workflows and default preferences. Although there is a way to push workflow definitions from code to Knock as part of a CI pipeline, it felt a bit clunky to me. It wasn't immediately obvious how to support pushing and committing workflows from code while also supporting workflow changes for specific environments only. If there were more detailed examples and/or more tooling it would be very helpful. Review collected by and hosted on G2.com.

The ease of use to create new emails and notifications. It's really easy to setup new automations and then integrate directly into your app as all you need to do is hit an API. One of my favorite aspects is that you commit changes and can have different environments, development, staging, and production. So you can easily tweak something on development, move it to staging, test it and get reviews if necessary, and only then release any changes. Review collected by and hosted on G2.com.

I can only think of two potential downsides at the moment. 1 is with the commits, there have been times where I make changes without committing and then try and revert those changes. The changes do apparently revert, but it doesn't update in the UI immediately causing extreme confusion and sometimes fear. The other is with editing email templates. It's generally straightforward and they have a nice UI to add different email elements, but it can be very limiting. As soon as I hit something that the UI cannot achieve I need to switch to html editing, which is slightly more cumbersome to deal with and if you go back to the UI you lose your changes. Review collected by and hosted on G2.com.

Knock has been a phenomenal addition for our company, enabling us to empower product managers and designers to own and iterate on the communications we send our customers.

The platform is highly reliable (no downtime in the 9 months that we've been on them), very robust (especially given how new the company is), and was extremely easy for us to integrate with.

Their team is extremely helpful with any questions we have and are extremely hungry for our feedback, which they often take action on within days or weeks of us giving it. Review collected by and hosted on G2.com.

The only downsides we've experienced is around the feature-set for non-transactional comms: we're not yet able to migrate our LCM or two-way communications to it. Review collected by and hosted on G2.com.

Greatly shortens the time it takes to implement notifications into an application, I have used it now in three different applications. I also like the node-based GUI for designing workflows, it means that I often can offload the designing and implementation of new notification flows to a Product Manager once the base Knock integration has been implemented on our backend. Review collected by and hosted on G2.com.

The only downside I'll give is that by integrating with another provider, it makes local development much harder which in turn leads to a scalability problem in terms of the number of developers working on the product. Would be cool if there was some localized, mock version one could use when developing locally. Review collected by and hosted on G2.com.

I appreciate the quick setup process, which made integrating with our existing systems seamless and efficient. The convenience of having an off-the-shelf solution for notifications saves us from reinventing the wheel as developers. I also value the unified API across notification types and the ability to schedule notifications, both of which significantly boost our efficiency. Review collected by and hosted on G2.com.

I dislike that my entire Knock configuration cannot reside in my codebase. If I want to switch Knock instances, I have to redo all the email templates and configurations in the UI. I would prefer everything to live in code in my GitHub repository. This reliance on the UI makes the configuration management challenging and less flexible. Review collected by and hosted on G2.com.