-
Notifications
You must be signed in to change notification settings - Fork 844
New issue
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
Slack client response_url usage #270
Comments
@chubz |
I realize that and I did end up using requests to make the call I needed. |
I'll be adding a new class that provides a handy way to use webhooks and response_urls soon. |
Fix #270 by adding a new module for incoming webhook and response_url
@seratch The webhook class is pretty cool |
Description
Using response_url in SlackClient
What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)I cannot find anywhere how to utilize response_url with SlackClient.
I'm trying to queue a message that would replace the currently displayed message to the user if there is no action taken within 30 seconds.
The original initial message I'm sending is of ephemeral type. I've read that you cannot directly delete/update those using api_call("chat.update") or api_call("chat.delete").
However, from slack docs it seems it is possible to modify/replace that message using the specific response_url provided by user click a message button.
Does slack client provide any wrapper for using response_url that I'm missing? If it doesn't have anything utilizing response_url is it plausible to work it in the client api?
So if anyone wants they could call something like:
client.respond_to(response_url, **kwrags)
It seems like something that would provide wider utilization of the standard client.
The text was updated successfully, but these errors were encountered: