I’ve tried recreating this workflow and creating my own Todoist app and have n8n listen for a webhook URL, and yet I can’t seem to get these to fire off either. I also tested webhook.site, and no dice They may require a very specific path, so you might need to contact Todoist support and reach out to them.
@EmeraldHerald : I tried to use it test it with webhook.site yesterday and it worked (this “half-success” led to the second point of my first post). This Todoist issue you saw on Twitter should be the reason of webhook.site not showing anything. I guess we have to wait before trying again
@Jon : Thank you for your suggestion. I followed the Todoist API docs but I may have forgot to do something. I’ll try to redo the steps, just in case.
@EmeraldHerald It seems Todoist webhooks are back again
However, after a try, it still didn’t work on my n8n instance. It works on webhook.site, (using the test token Todoist provides, I believe).
I removed my Todoist OAuth credential on n8n and also removed the app on Todoist to start a fresh install of webhooks. But I encounter this error when I try to connect my account (in n8n’s credentials page):
@jon I also followed the Todoist docs, especially the “Webhook Activation & Personal Use” part but it asked me for a param named “state” when calling https://todoist.com/oauth/authorize url. Where can I find this param?
That scope error could be down to a bug found yesterday while looking into this, If you open your browser dev console (normally F12), Click on the network tab then click on the sign in button. The network tab will update and you will see something like this…
If you copy that data value from the right and pop it into a text editor find the below