We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the moment this task uses "Legacy tokens" (https://api.slack.com/custom-integrations/legacy-tokens) to communicate with Slack. It would be nice if support could be added for "Incoming webhooks" (https://slack.com/apps/A0F7XDUAZ-incoming-webhooks). Some examples of how this works can be found here: https://api.slack.com/incoming-webhooks#sending_messages. One of the benefits is that we no longer need to share an API key that is linked to a user account. I am even wondering if support for legacy tokens should be dropped.
The text was updated successfully, but these errors were encountered:
Is this on roadmap ?
Sorry, something went wrong.
kasunkv
No branches or pull requests
At the moment this task uses "Legacy tokens" (https://api.slack.com/custom-integrations/legacy-tokens) to communicate with Slack. It would be nice if support could be added for "Incoming webhooks" (https://slack.com/apps/A0F7XDUAZ-incoming-webhooks). Some examples of how this works can be found here: https://api.slack.com/incoming-webhooks#sending_messages. One of the benefits is that we no longer need to share an API key that is linked to a user account. I am even wondering if support for legacy tokens should be dropped.
The text was updated successfully, but these errors were encountered: