
I like how easy it is to just have an endpoint we can call to schedule notifications. It's especially beneficial when dealing with notifications that need to be sent in the future. Within those workflows, it feels pretty easy. Review collected by and hosted on G2.com.
I think that I would like to be able to use codebase interface, maybe through the CLI. Handling a notification engine, we pretty much have to build that part of the infrastructure ourselves. I would like to have more of a condition-based event approach. Let's say that whenever an event happens, then look for other conditions to see if the user met that requirement so that we can build an identification engine. Right now, I don't know if it's possible to do. So that part of the infrastructure we built ourselves. Review collected by and hosted on G2.com.
Hey Andy — thanks for the review! A few features we have today I wanted to direct you to given your notes:
- Our CLI: good for working with our service programmatically. https://docs.knock.app/cli/overview/installation
- Our conditions engine: good for powering condition use cases like one you mentioned. https://docs.knock.app/concepts/conditions
Hope that helps!