When you try to fully integrate nolt in your workflow, at some point you will have to access information, because you don’t want to store every post and comment on a separate database in order to match id’s with posts. Currently there is a problem with the
post.status.updated webhook, where if you don’t store every post somewhere with all of their information, you will not be able to properly announce a post status update, since you don’t know what the post updated was actually about.
If there would be some sort of API, you could link your webhook integration with the API, so whenever you receive a
post.status.update, you could just (for example) GET
https://nolt.io/api/v0/<board_id>/posts/?id<post_id>. You could add similar functions for
/fields/. You could also add some kind of key & token system, so not every user can just crawl through the api and randomly collect data.
An API is pretty important, especially when webhooks do not share all the information necessairy to keep track of posts. An API could also be useful in the future, because it could also make it possible to automate the creation of comments or ideas, and allow integrations made in both directions.