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

Add support for using response_url when making posts #91

Description

@raveious

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.

Activity

  1. os commented on Jan 28, 2017

    @os
    Owner

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

  2. raveious commented on Jan 28, 2017

    @raveious
    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

  3. rdkr commented on Jul 11, 2017

    @rdkr

    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 join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions