As a developer I've seen a lot of webhooks, we use them every day. And I've seen all the ways they can go wrong. Sometimes the data is in the wrong format, other times theres a retry leading to bad behaviour, or it could just not be getting sent. Previously, I would be be scratching my head, cobbling together logging, re-deploying, waiting for it to happen again. Now with WebhookWizard, I can see whats... Source: about 1 year ago

Theres webhookwizard.com its very focused on webhooks though, unlike Zap and Make, which could be a good thing depending on your use case. Source: over 1 year ago

It might help to put a webhook logging router in the middle like webhookwizard.com so you can see the response. Source: over 1 year ago

Our public API uses Notion.com: https://developers.notion.com/ Switching the product and marketing sites would take a lot of work for unclear/low benefit since at this point we’ve learned the .so lessons and have a good reputation. Given the choice of projects like “scale infra so we stay online and fast-ish”, “improve search”, or “notion dot com”, Notion dot com ends up below the cut line. - Source: Hacker News / 5 months ago

You can learn more about Notion API from here. Source: 11 months ago

Https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0 Https://developers.notion.com/. Source: about 1 year ago

Do you have basic programming skills? I don't know if this would work, but you could try converting the HTML backup into JSON objects Notion understands (use ChatGPT, don't do it yourself) and restore it using Notion's API. Source: about 1 year ago

On https://developers.notion.com/ I found information how to use filters to query databases. But I can't find anything about creating or updating filters of (linked) databases that may exist on a page. Source: over 1 year ago