Slack workflows generate a different type of webhook URL

[foundinblank]

📣 Notification Service(s) Impacted
Slack

🐞 Describe the bug
If you use Slack's Workflow Builder tool, there's a Webhook option. However, if you do this, it generates a webhook URL that is completely different than what apprise expects:

https://hooks.slack.com/workflows/{token_1}/{token_2/{token_3}/{token_4}

Seems to me that the Slack service in apprise needs to be updated to handle this new format...

[caronc]

I didn't know this, thanks for sharing. I wonder if the payload changed as well?

[foundinblank]

I don't know if the payload's shape changed, but the workflow gives you an option to define incoming variables in the payload to be used in other workflow steps.

[caronc]

I don't think workflows is where you want to be. I've had time to play around. You just need to generate a straight webhook; see wiki docs here. Workflows are for triggers to take in effect after something happens in the channel. someone says hi... your account just automatically says hi back (whether you're there or not).

In summary:

1. You want to create a bot or app

Apprise can then ingest this data and send notifications for you.

[foundinblank]

The webhook functionality in Slack Workflows functions like any regular webhook; the webhook is meant to trigger the workflow. I can set up a workflow with a webhook triggering it, and trigger that by curl $webhook_url.

[glsdown]

Just to add that workflows are built so they can be triggered by a webhook. You can see more in the Slack documentation on it. So I think the main point here is that the webhook format used to trigger workflows is different to what apprise is expecting. I believe it's a relatively new thing for Slack to support webhooks to trigger workflows, but it's something we are very keen to make use of.