25. Payload
A JSON payload
sent over POST
POST https://hooks.slack.com/services/T0000000/
B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
Content-type: application/json
{
"text": "New request",
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "I copied this from BKB!"
}
}
...
]
}
30. Things we
had to
consider
â Rich feature set vs ease of use
â How do you discover workïŹows?
â Admin controls:
â Who can build?
â Where does data go?
â What visibility do admins
get?
36. Developers
wanted
more
â They hacked together UI
elements we didnât oïŹer- or fell
back to NLP
â They edited and updated
messages constantly, which
thrashed channels full of people
â Apps just needed more space in
the client to use
45. What we
needed to
build to
enable this
â A more robust set of UI
elements⊠and a lot of front-end
code to make them work
seamlessly across clients
â A way to publish modal views
contingent on user action
(trigger_id)
â New events in our API:
app_home_opened,
view_submission
â And lots of educational material
47. Donât go it alone
Tools to help you get started
Community
Find others building apps
and integrations for their
teams: slackcommunity.com
SDKs
First party tooling for Node,
Python, and Java make it
easier to build
Slack Developer Tools
Install this Slack app to look
up docs, inspect message
structure, and more