Was it this week or next week? You search for that one-off email containing meeting details, raking through various threads in Microsoft Outlook - until you finally give up and ask your boss to resend the information. Try searching for an existing issue before creating a new one.Has this ever happened to you? You’re smack-dab in the middle of a busy few weeks when suddenly, you get the vague recollection of an important meeting coming up.

Issue Tracker for questions, bug reports, feature requests, and general discussion related to Bolt for JavaScript.

The following are the best ways to get assistance working through your issue: If you otherwise get stuck, we're here to help. The documentation has more information on basic and advanced concepts for Bolt for JavaScript. Replacing the message to remove the interactive elements is a best practice for any action that should only be performed once.Įvents API events do not need an ack() function since they are automatically acknowledged by your app. Legacy message button clicks, menu selections, and slash commands: Either call ack() with no parameters, a string to to update the message with a simple message, or an object to replace it with a complex message. Options requests: Call ack() with an object containing the options for the user to see. View submissions: Call ack() with no parameters or with a response action. In general, the Slack platform expects an acknowledgement within 3 seconds, so listeners should call this function as soon as possible.ĭepending on the type of incoming event a listener is meant for, ack() should be called with a parameter:īlock actions, global shortcuts, and message shortcuts: Call ack() with no parameters.

Listeners for these events need to call the ack() function, which is passed in as an argument. This includes all action, shortcut, view, command, and options requests. Some types of events need to be acknowledged in order to ensure a consistent user experience inside the Slack client (web, mobile, and desktop apps). Unlike the client passed to listeners, the top-level client must be passed a token. In addition to the client property passed to listeners, each app has a top-level client that can be used to call methods.

action ( actionId, fn ) // Listen for dialog submissions app. message ( fn ) // Listen for an action from a Block Kit element (buttons, select menus, date pickers, etc) app. event ( eventType, fn ) // Convenience method to listen to only `message` events using a string or RegExp app. Listen for an event from the Events API app.

Scheduling a message in slack