Hey @joaquincoitino so you’re having trouble with receiving an interactivity webhook from Slack? Let’s take a closer look.
The error message “Cannot read properties of undefined reading ‘type’ may mean that the Slack trigger node is expecting a ‘type’ property in the incoming data, but it’s not finding it. Have you checked the Slack API docs to see if the ‘type’ property is supposed to be sent in the webhook data?
Also, can you double check your node configuration to make sure everything is set up correctly? Maybe there’s a small tweak that needs to be made.
From what I see @joaquincoitino your Slack Trigger node is set up to trigger on “any_event”, which is a good start. But when you’re working with interactivity webhooks, Slack usually sends specific types of events, like “block_actions” or “interactive_message”.
you need to tweak the node configuration to listen for those specific event types? Or you add a Switch node after the Slack Trigger node to handle different event types.
Thanks @Brighto but I only have that node on the workflow and it fails already. Also, it should not fail even if I am using “any_event”. The problem seems to be with the node, or am I missing anything?
I am getting the same error with very similar circumstances on 1.110.1 self hosted. The standard webhook works (albeit without auth hence me trying to improve it). This one returns 500 to slack when responding to a block action, and the slack hook node shows the same error mentioned above. Note I’m not actually using events per se, rather block actions with responsive buttons etc.