Slack webhook events
91 Slack event types in 12 resources, plus Other Slack events. 87 have sample payloads.
These pages cover the Events API, which Slack uses to send events to your app. To post messages into a channel, see incoming webhook limits or how to send external webhooks to Slack.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
agent
assistant_thread_context_changed
documented from Slack docs (example)
assistant_thread_context_changed User opens another channel while an assistant thread is open
Identified by event.type field in the body
Resource agent
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 23 fields.
From Slack docs
-
Content type
application/json
assistant_thread_started
documented from Slack docs (example)
assistant_thread_started User starts a new assistant thread
Identified by event.type field in the body
Resource agent
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 23 fields.
From Slack docs
-
Content type
application/json
agent_session_stopped
documented official schema
agent_session_stopped User presses stop on a running agent session
Identified by event.type field in the body
Resource agent
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "AXXXXXXXXX",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev08MFMKH6",
"event_time": 1234567890
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
agent_session_title_changed
documented official schema
agent_session_title_changed User renames an agent session
Identified by event.type field in the body
Resource agent
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "AXXXXXXXXX",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev08MFMKH6",
"event_time": 1234567890
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 21 fields.
From Slack docs
-
Content type
application/json
app
app_home_opened
documented official schema
app_home_opened User opens a tab in your App Home
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 40 fields.
From Slack docs
-
Content type
application/json
app_context_changed
documented from Slack docs (example)
app_context_changed User's view changes while your app is open
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
app_deleted
documented from Slack docs (example)
app_deleted App is deleted from a team or organization
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
app_installed
documented from Slack docs (example)
app_installed App gets installed on a team or organization
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 21 fields.
From Slack docs
-
Content type
application/json
app_rate_limited
documented from Slack docs (example)
app_rate_limited Slack caps your app's event deliveries for a workspace
Identified by event.type field in the body
Resource app
{
"token": "Jhj5dZrVaK7ZwHHjRyZWjbDl",
"type": "app_rate_limited",
"team_id": "T123456",
"minute_rate_limited": 1518467820,
"api_app_id": "A123456"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | app_rate_limited |
Full schema: 5 fields.
From Slack docs
-
Content type
application/json
app_requested
documented from Slack docs (example)
app_requested Team member asks to install an app
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 57 fields.
From Slack docs
-
Content type
application/json
app_uninstalled_team
documented from Slack docs (example)
app_uninstalled_team App gets uninstalled from a team or organization
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 21 fields.
From Slack docs
-
Content type
application/json
app_uninstalled
documented from Slack docs (example)
app_uninstalled Your app is fully removed from a workspace
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 14 fields.
From Slack docs
-
Content type
application/json
function_executed
documented from Slack docs (example)
function_executed Workflow runs your app's custom function as a step
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 44 fields.
From Slack docs
-
Content type
application/json
team_access_granted
documented from Slack docs (example)
team_access_granted Org app's token gains access to a workspace
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
team_access_revoked
documented from Slack docs (example)
team_access_revoked Org app's token loses access to a workspace
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
tokens_revoked
documented from Slack docs (example)
tokens_revoked Your app's API tokens are revoked
Identified by event.type field in the body
Resource app
{
"token": "XXYYZZ",
"team_id": "TXXXXXXXX",
"api_app_id": "AXXXXXXXXX",
"event": { … },
"type": "event_callback",
"event_id": "EvXXXXXXXX",
"event_time": 1234567890
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 13 fields.
From Slack docs
-
Content type
application/json
url_verification
documented from Slack docs (example)
url_verification Slack checks you control a new Request URL
Identified by event.type field in the body
Resource app
{
"token": "Jhj5dZrVaK7ZwHHjRyZWjbDl",
"challenge": "3eZbrw1aBm2rZgRNFdxV2595E9CY3gmdALWMmHkvFXO7tYXAYM8P",
"type": "url_verification"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | url_verification |
Full schema: 3 fields.
From Slack docs
-
Content type
application/json
channel
member_joined_channel
documented from Slack docs (example)
member_joined_channel User joins a channel, private channel or group DM
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
channel_archive
documented from Slack docs (example)
channel_archive Public channel gets archived
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
channel_created
documented from Slack docs (example)
channel_created New channel appears in the workspace
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 19 fields.
From Slack docs
-
Content type
application/json
channel_deleted
documented from Slack docs (example)
channel_deleted Channel is removed from the workspace
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 15 fields.
From Slack docs
-
Content type
application/json
channel_history_changed
documented from Slack docs (example)
channel_history_changed Channel history changes in bulk, so reload it
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 17 fields.
From Slack docs
-
Content type
application/json
channel_id_changed
documented from Slack docs (example)
channel_id_changed Private channel gets a new ID when shared through Slack Connect
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
channel_left
documented from Slack docs (example)
channel_left User leaves a public channel; Slack sometimes withholds this
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 15 fields.
From Slack docs
-
Content type
application/json
channel_rename
documented from Slack docs (example)
channel_rename Channel gets a new name
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 18 fields.
From Slack docs
-
Content type
application/json
member_left_channel
documented from Slack docs (example)
member_left_channel User leaves a public or private channel
Identified by event.type field in the body
Resource channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 18 fields.
From Slack docs
-
Content type
application/json
direct_message
im_close
documented from Slack docs (example)
im_close User closes a direct message channel
Identified by event.type field in the body
Resource direct_message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
im_created
documented from Slack docs (example)
im_created New direct message channel includes this user
Identified by event.type field in the body
Resource direct_message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 21 fields.
From Slack docs
-
Content type
application/json
im_history_changed
documented from Slack docs (example)
im_history_changed Direct message history changes in bulk, so reload it
Identified by event.type field in the body
Resource direct_message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 17 fields.
From Slack docs
-
Content type
application/json
im_open
documented from Slack docs (example)
im_open User opens a direct message channel
Identified by event.type field in the body
Resource direct_message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
file
file_change
documented from Slack docs (example)
file_change Any property of a file changes
Identified by event.type field in the body
Resource file
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 17 fields.
From Slack docs
-
Content type
application/json
file_comment_deleted
documented from Slack docs (example)
file_comment_deleted No longer sent: a file comment was removed
Identified by event.type field in the body
Resource file
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 18 fields.
From Slack docs
-
Content type
application/json
file_created
documented from Slack docs (example)
file_created User uploads a file to Slack
Identified by event.type field in the body
Resource file
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 17 fields.
From Slack docs
-
Content type
application/json
file_deleted
documented from Slack docs (example)
file_deleted File is removed from the workspace
Identified by event.type field in the body
Resource file
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
file_public
documented from Slack docs (example)
file_public File becomes public
Identified by event.type field in the body
Resource file
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 17 fields.
From Slack docs
-
Content type
application/json
message
app_mention
documented from Slack docs (example)
app_mention Message in a conversation mentions your bot user
Identified by event.type field in the body
Resource message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 19 fields.
From Slack docs
-
Content type
application/json
message
documented from Slack docs (example)
message Message is posted; every message.* subscription delivers this type
Identified by event.type field in the body
Resource message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 19 fields.
From Slack docs
-
Content type
application/json
message_metadata_deleted
documented from Slack docs (example)
message_metadata_deleted Metadata is removed from a message
Identified by event.type field in the body
Resource message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 30 fields.
From Slack docs
-
Content type
application/json
message_metadata_posted
documented from Slack docs (example)
message_metadata_posted Message carrying metadata is sent
Identified by event.type field in the body
Resource message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 29 fields.
From Slack docs
-
Content type
application/json
message_metadata_updated
documented from Slack docs (example)
message_metadata_updated Message's metadata changes
Identified by event.type field in the body
Resource message
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 37 fields.
From Slack docs
-
Content type
application/json
message.app_home
documented from Slack docs (example)
message.app_home Subscription for App Home messages in the defunct workspace apps
Identified by event.type field in the body
Resource message
{
"token": "one-long-verification-token",
"team_id": "T012345678",
"api_app_id": "A0PNCHHK2",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev0PV52K25",
"event_time": 1525215129
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 21 fields.
From Slack docs
-
Content type
application/json
message.channels
documented from Slack docs (example)
message.channels Subscription for public channel messages; `event.type` is `message`
Identified by event.type field in the body
Resource message
{
"token": "one-long-verification-token",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 1355517523
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
message.groups
documented from Slack docs (example)
message.groups Subscription for private channel messages; `event.type` is `message`
Identified by event.type field in the body
Resource message
{
"token": "one-long-verification-token",
"team_id": "T061EG9R6",
"api_app_id": "A0PNCHHK2",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev0PV52K21",
"event_time": 1355517523
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
message.im
documented from Slack docs (example)
message.im Subscription for direct messages; `event.type` is `message`
Identified by event.type field in the body
Resource message
{
"token": "one-long-verification-token",
"team_id": "T123ABC456",
"api_app_id": "A0PNCHHK2",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev0PV52K21",
"event_time": 1355517523
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
message.mpim
documented from Slack docs (example)
message.mpim Subscription for group DM messages; `event.type` is `message`
Identified by event.type field in the body
Resource message
{
"token": "one-long-verification-token",
"team_id": "T061EG9R6",
"api_app_id": "A0PNCHHK2",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev0PV52K21",
"event_time": 1355517523
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 20 fields.
From Slack docs
-
Content type
application/json
private_channel
group_close
documented from Slack docs (example)
group_close User closes a private channel
Identified by event.type field in the body
Resource private_channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
group_deleted
documented from Slack docs (example)
group_deleted Private channel is removed
Identified by event.type field in the body
Resource private_channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 15 fields.
From Slack docs
-
Content type
application/json
group_history_changed
documented from Slack docs (example)
group_history_changed Private channel history changes in bulk, so reload it
Identified by event.type field in the body
Resource private_channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 17 fields.
From Slack docs
-
Content type
application/json
group_left
documented from Slack docs (example)
group_left User leaves a private channel
Identified by event.type field in the body
Resource private_channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 15 fields.
From Slack docs
-
Content type
application/json
group_open
documented from Slack docs (example)
group_open User opens a group DM
Identified by event.type field in the body
Resource private_channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
group_rename
documented from Slack docs (example)
group_rename Private channel gets a new name
Identified by event.type field in the body
Resource private_channel
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 18 fields.
From Slack docs
-
Content type
application/json
reaction
reaction_added
documented from Slack docs (example)
reaction_added User adds an emoji reaction to an item
Identified by event.type field in the body
Resource reaction
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 23 fields.
From Slack docs
-
Content type
application/json
reaction_removed
documented from Slack docs (example)
reaction_removed User removes an emoji reaction from an item
Identified by event.type field in the body
Resource reaction
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 23 fields.
From Slack docs
-
Content type
application/json
pin_added
documented No payload yet
pin_added Item gets pinned in a channel
Identified by event.type field in the body
Resource reaction
No payload yet.
pin_removed
documented No payload yet
pin_removed Item gets unpinned from a channel
Identified by event.type field in the body
Resource reaction
No payload yet.
star_added
documented No payload yet
star_added User saves or stars an item
Identified by event.type field in the body
Resource reaction
No payload yet.
star_removed
documented No payload yet
star_removed User unsaves or unstars an item
Identified by event.type field in the body
Resource reaction
No payload yet.
shared_channel
user
team_join
documented official schema
team_join New member joins the workspace
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 83 fields.
From Slack docs
-
Content type
application/json
dnd_updated_user
documented from Slack docs (example)
dnd_updated_user Workspace member's Do Not Disturb settings change
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 19 fields.
From Slack docs
-
Content type
application/json
dnd_updated
documented from Slack docs (example)
dnd_updated User's own Do Not Disturb settings change
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 21 fields.
From Slack docs
-
Content type
application/json
user_change
documented from Slack docs (example)
user_change Member updates their profile or data
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 61 fields.
From Slack docs
-
Content type
application/json
user_connection
documented from Slack docs (example)
user_connection User asks to connect to or disconnect from your app
Identified by event.type field in the body
Resource user
{
"token": "P1GEyKehpM8yI998PLwq0P66",
"team_id": "E012A3BC4DE",
"api_app_id": "A012ABC34DE",
"event": { … },
"type": "event_callback",
"event_id": "Ev012A3BCDEF",
"event_time": 1764264284
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 12 fields.
From Slack docs
-
Content type
application/json
user_huddle_changed
documented from Slack docs (example)
user_huddle_changed User's huddle status changes
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 64 fields.
From Slack docs
-
Content type
application/json
user_profile_changed
documented from Slack docs (example)
user_profile_changed User's profile changes
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"event_id": "Ev0123ABC456",
"event_time": 1734567890
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 24 fields.
From Slack docs
-
Content type
application/json
user_status_changed
documented from Slack docs (example)
user_status_changed User's status changes
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"event_id": "Ev0123ABC456",
"event_time": 1734567890
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 25 fields.
From Slack docs
-
Content type
application/json
user_guest_status_changed
documented from Slack docs (example)
user_guest_status_changed User moves between member and guest roles
Identified by event.type field in the body
Resource user
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 1758000000
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 61 fields.
From Slack docs
-
Content type
application/json
user_group
subteam_created
documented from Slack docs (example)
subteam_created New User Group is created
Identified by event.type field in the body
Resource user_group
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 32 fields.
From Slack docs
-
Content type
application/json
subteam_members_changed
documented from Slack docs (example)
subteam_members_changed Users are added to or removed from a User Group
Identified by event.type field in the body
Resource user_group
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 23 fields.
From Slack docs
-
Content type
application/json
subteam_self_added
documented from Slack docs (example)
subteam_self_added You are added to a User Group
Identified by event.type field in the body
Resource user_group
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 15 fields.
From Slack docs
-
Content type
application/json
subteam_self_removed
documented from Slack docs (example)
subteam_self_removed You are removed from a User Group
Identified by event.type field in the body
Resource user_group
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 15 fields.
From Slack docs
-
Content type
application/json
subteam_updated
documented from Slack docs (example)
subteam_updated User Group's details or members change
Identified by event.type field in the body
Resource user_group
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 40 fields.
From Slack docs
-
Content type
application/json
workspace
email_domain_changed
documented from Slack docs (example)
email_domain_changed Workspace email domain settings change
Identified by event.type field in the body
Resource workspace
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
emoji_changed
documented from Slack docs (example)
emoji_changed Workspace custom emoji is added or updated
Identified by event.type field in the body
Resource workspace
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 18 fields.
From Slack docs
-
Content type
application/json
grid_migration_finished
documented from Slack docs (example)
grid_migration_finished Workspace completes its move to an Enterprise organization
Identified by event.type field in the body
Resource workspace
{
"token": "XXYYZZ",
"team_id": "TXXXXXXXX",
"api_app_id": "AXXXXXXXXX",
"event": { … },
"type": "event_callback",
"event_id": "EvXXXXXXXX",
"event_time": 1234567890
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 9 fields.
From Slack docs
-
Content type
application/json
grid_migration_started
documented from Slack docs (example)
grid_migration_started Workspace begins moving to an Enterprise organization
Identified by event.type field in the body
Resource workspace
{
"token": "XXYYZZ",
"team_id": "TXXXXXXXX",
"api_app_id": "AXXXXXXXXX",
"event": { … },
"type": "event_callback",
"event_id": "EvXXXXXXXX",
"event_time": 1234567890
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 9 fields.
From Slack docs
-
Content type
application/json
invite_requested
documented from Slack docs (example)
invite_requested Someone asks for a workspace invitation
Identified by event.type field in the body
Resource workspace
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 30 fields.
From Slack docs
-
Content type
application/json
team_domain_change
documented from Slack docs (example)
team_domain_change Workspace domain changes
Identified by event.type field in the body
Resource workspace
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 16 fields.
From Slack docs
-
Content type
application/json
team_rename
documented from Slack docs (example)
team_rename Admin changes the workspace name
Identified by event.type field in the body
Resource workspace
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 15 fields.
From Slack docs
-
Content type
application/json
Other Slack events
call_rejected
documented from Slack docs (example)
call_rejected User turns down a call shared in a DM
Identified by event.type field in the body
{
"token": "12345FVmRUzNDOAu12345h",
"team_id": "T123ABC456",
"api_app_id": "BBBU04BB4",
"event": { … },
"type": "event_callback",
"event_id": "Ev123ABC456",
"event_time": 1563448153,
"authorizations": [ … ]
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 18 fields.
From Slack docs
-
Content type
application/json
entity_comments_requested
documented from Slack docs (example)
entity_comments_requested User opens or pages a Work Objects comments tab
Identified by event.type field in the body
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 27 fields.
From Slack docs
-
Content type
application/json
entity_details_requested
documented from Slack docs (example)
entity_details_requested User clicks a Work Objects unfurl or refreshes its flexpane
Identified by event.type field in the body
{
"token": "XXYYZZ",
"team_id": "T123ABC456",
"api_app_id": "A123ABC456",
"event": { … },
"type": "event_callback",
"authorizations": [ … ],
"event_id": "Ev123ABC456",
"event_time": 123456789
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | event_callback |
Full schema: 29 fields.
From Slack docs
-
Content type
application/json
Route Slack events by type.
Event Gateway receives every Slack delivery and filters and routes it by event type, so each service gets only the events it handles.