The image above shows the three different style options.Ī confirm object that defines an optional confirmation dialog after the button is clicked.Ī label for longer descriptive text about a button element. If you don't include this field, the default button style will be used. Use danger even more sparingly than primary. primary should only be used for one button within a set.ĭanger gives buttons a red outline and text, and should be used when the action is destructive. Primary gives buttons a green outline and text, ideal for affirmation or confirmation actions. Maximum length for this field is 2000 characters.ĭecorates buttons with alternative visual color schemes. The value to send along with the interaction payload. If you're using url, you'll still receive an interaction payload and will need to send an acknowledgement response. Maximum length for this field is 3000 characters. Maximum length for this field is 255 characters.Ī URL to load in the user's browser when the button is clicked. Should be unique among all other action_ids in the containing block. You can use this when you receive an interaction payload to identify the source of the action. Maximum length for the text in this field is 75 characters.Īn identifier for this action. In this case type is always button.Ī text object that defines the button's text.
Read our guide to enabling interactivity. To use interactive components, you will need to make some changes to prepare your app. The button can be a trigger for anything from opening a simple link to starting a complex workflow. The lists of fields and values below describe the JSON that apps can use to generate each element:Īn interactive component that inserts a button.
Our overview of app surfaces that support Block Kit shows you where add blocks.įinally, our handling user interactivity guide will help you prepare your app to allow for the use of the interactive components listed below. Block elements can be used inside of section, context, input and actions layout blocks.
0 kommentar(er)
