Skip to content
This repository has been archived by the owner on Jul 3, 2020. It is now read-only.

Add support for using response_url when making posts #91

Open
raveious opened this issue Dec 2, 2016 · 3 comments
Open

Add support for using response_url when making posts #91

raveious opened this issue Dec 2, 2016 · 3 comments

Comments

@raveious
Copy link

raveious commented Dec 2, 2016

For using slash commands and other interactive buttons, you're given the option to respond using the response_url field value instead of just a normal return within the 3 second limit.

@os
Copy link
Owner

os commented Jan 28, 2017

Hi, @raveious. I'm not sure if I'm following. Could you provide more details on this?

@raveious
Copy link
Author

Sure,

When receiving a message from Slack, it will often include a response_url field.
https://api.slack.com/slash-commands#responding_to_a_command

If you post to this URL instread of the generic one, slack will handling this differently and renders this differently. This is particularlly useful for when hosting on a server that is particularly slow cough cough free Heroku instance cough

@rdkr
Copy link

rdkr commented Jul 11, 2017

A workaround is to use Slacker.incomingwebhook:

slack = Slacker('<token>', incoming_webhook_url='<response_url>')
slack.incomingwebhook.post({"text": "It's 80 degrees right now."})

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants