Hi folks,
Just circling back in here with a quick update to share that the bug report has been closed. In case you missed the email that went out here’s the key details from it:
We're glad to report that a new version of the integration has been released which includes a "Get Message" search action. This action takes the IDs of the message and channel and returns the details of a specific message. This means that the "Find Message" action is still present and useful for "query-based" searching, but when your Zap already knows which message it needs, you can use "Get Message" to fetch it.
From what I can tell there were some recent changes made on Slack’s end to their API that seem to have affected the functionality of their search.messages endpoint, meaning the Find Message action is no longer be able to find messages by a permalink URL. This means that if you don’t have the message ID (Timestamp) already, the workarounds mentioned in this thread previously (extracting the timestamp value from the URL, and reformatting it to add the missing period if needed would be needed to first get the message ID that you could then use in the new Get Message action to find the message.
Not an ideal solution I know, but hopefully it will helps to get your Zaps back on track. Do let us know if you run into any issues with the new Get Message action that was added, want to make sure you’re all set! 🙂