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)

User opens another channel while an assistant thread is open

Identified by event.type field in the body Resource agent

slack-assistant-thread-context-changed.json
{
  "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

Send example to Inspect → View as JSON

assistant_thread_started

documented from Slack docs (example)

User starts a new assistant thread

Identified by event.type field in the body Resource agent

slack-assistant-thread-started.json
{
  "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

Send example to Inspect → View as JSON

agent_session_stopped

documented official schema

User presses stop on a running agent session

Identified by event.type field in the body Resource agent

slack-agent-session-stopped.json
{
  "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

Send example to Inspect → View as JSON

agent_session_title_changed

documented official schema

User renames an agent session

Identified by event.type field in the body Resource agent

slack-agent-session-title-changed.json
{
  "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

Send example to Inspect → View as JSON

app

app_home_opened

documented official schema

User opens a tab in your App Home

Identified by event.type field in the body Resource app

slack-app-home-opened.json
{
  "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

Send example to Inspect → View as JSON

app_context_changed

documented from Slack docs (example)

User's view changes while your app is open

Identified by event.type field in the body Resource app

slack-app-context-changed.json
{
  "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

Send example to Inspect → View as JSON

app_deleted

documented from Slack docs (example)

App is deleted from a team or organization

Identified by event.type field in the body Resource app

slack-app-deleted.json
{
  "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

Send example to Inspect → View as JSON

app_installed

documented from Slack docs (example)

App gets installed on a team or organization

Identified by event.type field in the body Resource app

slack-app-installed.json
{
  "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

Send example to Inspect → View as JSON

app_rate_limited

documented from Slack docs (example)

Slack caps your app's event deliveries for a workspace

Identified by event.type field in the body Resource app

slack-app-rate-limited.json
{
  "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

Send example to Inspect → View as JSON

app_requested

documented from Slack docs (example)

Team member asks to install an app

Identified by event.type field in the body Resource app

slack-app-requested.json
{
  "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

Send example to Inspect → View as JSON

app_uninstalled_team

documented from Slack docs (example)

App gets uninstalled from a team or organization

Identified by event.type field in the body Resource app

slack-app-uninstalled-team.json
{
  "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

Send example to Inspect → View as JSON

app_uninstalled

documented from Slack docs (example)

Your app is fully removed from a workspace

Identified by event.type field in the body Resource app

slack-app-uninstalled.json
{
  "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

Send example to Inspect → View as JSON

function_executed

documented from Slack docs (example)

Workflow runs your app's custom function as a step

Identified by event.type field in the body Resource app

slack-function-executed.json
{
  "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

Send example to Inspect → View as JSON

team_access_granted

documented from Slack docs (example)

Org app's token gains access to a workspace

Identified by event.type field in the body Resource app

slack-team-access-granted.json
{
  "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

Send example to Inspect → View as JSON

team_access_revoked

documented from Slack docs (example)

Org app's token loses access to a workspace

Identified by event.type field in the body Resource app

slack-team-access-revoked.json
{
  "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

Send example to Inspect → View as JSON

tokens_revoked

documented from Slack docs (example)

Your app's API tokens are revoked

Identified by event.type field in the body Resource app

slack-tokens-revoked.json
{
  "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

Send example to Inspect → View as JSON

url_verification

documented from Slack docs (example)

Slack checks you control a new Request URL

Identified by event.type field in the body Resource app

slack-url-verification.json
{
  "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

Send example to Inspect → View as JSON

channel

member_joined_channel

documented from Slack docs (example)

User joins a channel, private channel or group DM

Identified by event.type field in the body Resource channel

slack-member-joined-channel.json
{
  "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

Send example to Inspect → View as JSON

channel_archive

documented from Slack docs (example)

Public channel gets archived

Identified by event.type field in the body Resource channel

slack-channel-archive.json
{
  "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

Send example to Inspect → View as JSON

channel_created

documented from Slack docs (example)

New channel appears in the workspace

Identified by event.type field in the body Resource channel

slack-channel-created.json
{
  "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

Send example to Inspect → View as JSON

channel_deleted

documented from Slack docs (example)

Channel is removed from the workspace

Identified by event.type field in the body Resource channel

slack-channel-deleted.json
{
  "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

Send example to Inspect → View as JSON

channel_history_changed

documented from Slack docs (example)

Channel history changes in bulk, so reload it

Identified by event.type field in the body Resource channel

slack-channel-history-changed.json
{
  "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

Send example to Inspect → View as JSON

channel_id_changed

documented from Slack docs (example)

Private channel gets a new ID when shared through Slack Connect

Identified by event.type field in the body Resource channel

slack-channel-id-changed.json
{
  "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

Send example to Inspect → View as JSON

channel_left

documented from Slack docs (example)

User leaves a public channel; Slack sometimes withholds this

Identified by event.type field in the body Resource channel

slack-channel-left.json
{
  "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

Send example to Inspect → View as JSON

channel_rename

documented from Slack docs (example)

Channel gets a new name

Identified by event.type field in the body Resource channel

slack-channel-rename.json
{
  "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

Send example to Inspect → View as JSON

channel_shared

documented from Slack docs (example)

Channel starts being shared with an external workspace

Identified by event.type field in the body Resource channel

slack-channel-shared.json
{
  "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

Send example to Inspect → View as JSON

channel_unshared

documented from Slack docs (example)

External workspace is removed from a shared channel

Identified by event.type field in the body Resource channel

slack-channel-unshared.json
{
  "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

Send example to Inspect → View as JSON

member_left_channel

documented from Slack docs (example)

User leaves a public or private channel

Identified by event.type field in the body Resource channel

slack-member-left-channel.json
{
  "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

Send example to Inspect → View as JSON

direct_message

im_close

documented from Slack docs (example)

User closes a direct message channel

Identified by event.type field in the body Resource direct_message

slack-im-close.json
{
  "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

Send example to Inspect → View as JSON

im_created

documented from Slack docs (example)

New direct message channel includes this user

Identified by event.type field in the body Resource direct_message

slack-im-created.json
{
  "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

Send example to Inspect → View as JSON

im_history_changed

documented from Slack docs (example)

Direct message history changes in bulk, so reload it

Identified by event.type field in the body Resource direct_message

slack-im-history-changed.json
{
  "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

Send example to Inspect → View as JSON

im_open

documented from Slack docs (example)

User opens a direct message channel

Identified by event.type field in the body Resource direct_message

slack-im-open.json
{
  "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

Send example to Inspect → View as JSON

file

file_change

documented from Slack docs (example)

Any property of a file changes

Identified by event.type field in the body Resource file

slack-file-change.json
{
  "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

Send example to Inspect → View as JSON

file_comment_deleted

documented from Slack docs (example)

No longer sent: a file comment was removed

Identified by event.type field in the body Resource file

slack-file-comment-deleted.json
{
  "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

Send example to Inspect → View as JSON

file_created

documented from Slack docs (example)

User uploads a file to Slack

Identified by event.type field in the body Resource file

slack-file-created.json
{
  "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

Send example to Inspect → View as JSON

file_deleted

documented from Slack docs (example)

File is removed from the workspace

Identified by event.type field in the body Resource file

slack-file-deleted.json
{
  "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

Send example to Inspect → View as JSON

file_public

documented from Slack docs (example)

File becomes public

Identified by event.type field in the body Resource file

slack-file-public.json
{
  "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

Send example to Inspect → View as JSON

file_shared

documented from Slack docs (example)

File gets shared

Identified by event.type field in the body Resource file

slack-file-shared.json
{
  "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

Send example to Inspect → View as JSON

file_unshared

documented from Slack docs (example)

File stops being shared

Identified by event.type field in the body Resource file

slack-file-unshared.json
{
  "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

Send example to Inspect → View as JSON

message

app_mention

documented from Slack docs (example)

Message in a conversation mentions your bot user

Identified by event.type field in the body Resource message

slack-app-mention.json
{
  "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

Send example to Inspect → View as JSON

message

documented from Slack docs (example)

Message is posted; every message.* subscription delivers this type

Identified by event.type field in the body Resource message

slack-message.json
{
  "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

Send example to Inspect → View as JSON

message_metadata_deleted

documented from Slack docs (example)

Metadata is removed from a message

Identified by event.type field in the body Resource message

slack-message-metadata-deleted.json
{
  "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

Send example to Inspect → View as JSON

message_metadata_posted

documented from Slack docs (example)

Message carrying metadata is sent

Identified by event.type field in the body Resource message

slack-message-metadata-posted.json
{
  "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

Send example to Inspect → View as JSON

message_metadata_updated

documented from Slack docs (example)

Message's metadata changes

Identified by event.type field in the body Resource message

slack-message-metadata-updated.json
{
  "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

Send example to Inspect → View as JSON

message.app_home

documented from Slack docs (example)

Subscription for App Home messages in the defunct workspace apps

Identified by event.type field in the body Resource message

slack-message-app-home.json
{
  "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

Send example to Inspect → View as JSON

message.channels

documented from Slack docs (example)

Subscription for public channel messages; `event.type` is `message`

Identified by event.type field in the body Resource message

slack-message-channels.json
{
  "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

Send example to Inspect → View as JSON

message.groups

documented from Slack docs (example)

Subscription for private channel messages; `event.type` is `message`

Identified by event.type field in the body Resource message

slack-message-groups.json
{
  "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

Send example to Inspect → View as JSON

message.im

documented from Slack docs (example)

Subscription for direct messages; `event.type` is `message`

Identified by event.type field in the body Resource message

slack-message-im.json
{
  "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

Send example to Inspect → View as JSON

message.mpim

documented from Slack docs (example)

Subscription for group DM messages; `event.type` is `message`

Identified by event.type field in the body Resource message

slack-message-mpim.json
{
  "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

Send example to Inspect → View as JSON

private_channel

group_close

documented from Slack docs (example)

User closes a private channel

Identified by event.type field in the body Resource private_channel

slack-group-close.json
{
  "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

Send example to Inspect → View as JSON

group_deleted

documented from Slack docs (example)

Private channel is removed

Identified by event.type field in the body Resource private_channel

slack-group-deleted.json
{
  "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

Send example to Inspect → View as JSON

group_history_changed

documented from Slack docs (example)

Private channel history changes in bulk, so reload it

Identified by event.type field in the body Resource private_channel

slack-group-history-changed.json
{
  "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

Send example to Inspect → View as JSON

group_left

documented from Slack docs (example)

User leaves a private channel

Identified by event.type field in the body Resource private_channel

slack-group-left.json
{
  "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

Send example to Inspect → View as JSON

group_open

documented from Slack docs (example)

User opens a group DM

Identified by event.type field in the body Resource private_channel

slack-group-open.json
{
  "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

Send example to Inspect → View as JSON

group_rename

documented from Slack docs (example)

Private channel gets a new name

Identified by event.type field in the body Resource private_channel

slack-group-rename.json
{
  "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

Send example to Inspect → View as JSON

reaction

reaction_added

documented from Slack docs (example)

User adds an emoji reaction to an item

Identified by event.type field in the body Resource reaction

slack-reaction-added.json
{
  "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

Send example to Inspect → View as JSON

reaction_removed

documented from Slack docs (example)

User removes an emoji reaction from an item

Identified by event.type field in the body Resource reaction

slack-reaction-removed.json
{
  "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

Send example to Inspect → View as JSON

pin_added

documented No payload yet

Item gets pinned in a channel

Identified by event.type field in the body Resource reaction

No payload yet.

Help fill this in → View as JSON

pin_removed

documented No payload yet

Item gets unpinned from a channel

Identified by event.type field in the body Resource reaction

No payload yet.

Help fill this in → View as JSON

star_added

documented No payload yet

User saves or stars an item

Identified by event.type field in the body Resource reaction

No payload yet.

Help fill this in → View as JSON

star_removed

documented No payload yet

User unsaves or unstars an item

Identified by event.type field in the body Resource reaction

No payload yet.

Help fill this in → View as JSON

shared_channel

shared_channel_invite_accepted

documented official schema

Recipient accepts a Slack Connect channel invitation

Identified by event.type field in the body Resource shared_channel

slack-shared-channel-invite-accepted.json
{
  "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: 84 fields.

From Slack docs

  • Content type application/json

Send example to Inspect → View as JSON

shared_channel_invite_approved

documented official schema

Slack Connect channel invitation gets approved

Identified by event.type field in the body Resource shared_channel

slack-shared-channel-invite-approved.json
{
  "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: 84 fields.

From Slack docs

  • Content type application/json

Send example to Inspect → View as JSON

shared_channel_invite_declined

documented official schema

Slack Connect channel invitation is turned down

Identified by event.type field in the body Resource shared_channel

slack-shared-channel-invite-declined.json
{
  "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

Send example to Inspect → View as JSON

shared_channel_invite_received

documented official schema

Bot or app is invited to a Slack Connect channel

Identified by event.type field in the body Resource shared_channel

slack-shared-channel-invite-received.json
{
  "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: 53 fields.

From Slack docs

  • Content type application/json

Send example to Inspect → View as JSON

shared_channel_invite_requested

documented from Slack docs (example)

External invitation awaits approval, for customers who opted in

Identified by event.type field in the body Resource shared_channel

slack-shared-channel-invite-requested.json
{
  "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: 52 fields.

From Slack docs

  • Content type application/json

Send example to Inspect → View as JSON

user

team_join

documented official schema

New member joins the workspace

Identified by event.type field in the body Resource user

slack-team-join.json
{
  "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

Send example to Inspect → View as JSON

dnd_updated_user

documented from Slack docs (example)

Workspace member's Do Not Disturb settings change

Identified by event.type field in the body Resource user

slack-dnd-updated-user.json
{
  "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

Send example to Inspect → View as JSON

dnd_updated

documented from Slack docs (example)

User's own Do Not Disturb settings change

Identified by event.type field in the body Resource user

slack-dnd-updated.json
{
  "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

Send example to Inspect → View as JSON

user_change

documented from Slack docs (example)

Member updates their profile or data

Identified by event.type field in the body Resource user

slack-user-change.json
{
  "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

Send example to Inspect → View as JSON

user_connection

documented from Slack docs (example)

User asks to connect to or disconnect from your app

Identified by event.type field in the body Resource user

slack-user-connection.json
{
  "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

Send example to Inspect → View as JSON

user_huddle_changed

documented from Slack docs (example)

User's huddle status changes

Identified by event.type field in the body Resource user

slack-user-huddle-changed.json
{
  "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

Send example to Inspect → View as JSON

user_profile_changed

documented from Slack docs (example)

User's profile changes

Identified by event.type field in the body Resource user

slack-user-profile-changed.json
{
  "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

Send example to Inspect → View as JSON

user_status_changed

documented from Slack docs (example)

User's status changes

Identified by event.type field in the body Resource user

slack-user-status-changed.json
{
  "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

Send example to Inspect → View as JSON

user_guest_status_changed

documented from Slack docs (example)

User moves between member and guest roles

Identified by event.type field in the body Resource user

slack-user-guest-status-changed.json
{
  "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

Send example to Inspect → View as JSON

user_group

subteam_created

documented from Slack docs (example)

New User Group is created

Identified by event.type field in the body Resource user_group

slack-subteam-created.json
{
  "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

Send example to Inspect → View as JSON

subteam_members_changed

documented from Slack docs (example)

Users are added to or removed from a User Group

Identified by event.type field in the body Resource user_group

slack-subteam-members-changed.json
{
  "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

Send example to Inspect → View as JSON

subteam_self_added

documented from Slack docs (example)

You are added to a User Group

Identified by event.type field in the body Resource user_group

slack-subteam-self-added.json
{
  "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

Send example to Inspect → View as JSON

subteam_self_removed

documented from Slack docs (example)

You are removed from a User Group

Identified by event.type field in the body Resource user_group

slack-subteam-self-removed.json
{
  "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

Send example to Inspect → View as JSON

subteam_updated

documented from Slack docs (example)

User Group's details or members change

Identified by event.type field in the body Resource user_group

slack-subteam-updated.json
{
  "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

Send example to Inspect → View as JSON

workspace

email_domain_changed

documented from Slack docs (example)

Workspace email domain settings change

Identified by event.type field in the body Resource workspace

slack-email-domain-changed.json
{
  "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

Send example to Inspect → View as JSON

emoji_changed

documented from Slack docs (example)

Workspace custom emoji is added or updated

Identified by event.type field in the body Resource workspace

slack-emoji-changed.json
{
  "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

Send example to Inspect → View as JSON

grid_migration_finished

documented from Slack docs (example)

Workspace completes its move to an Enterprise organization

Identified by event.type field in the body Resource workspace

slack-grid-migration-finished.json
{
  "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

Send example to Inspect → View as JSON

grid_migration_started

documented from Slack docs (example)

Workspace begins moving to an Enterprise organization

Identified by event.type field in the body Resource workspace

slack-grid-migration-started.json
{
  "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

Send example to Inspect → View as JSON

invite_requested

documented from Slack docs (example)

Someone asks for a workspace invitation

Identified by event.type field in the body Resource workspace

slack-invite-requested.json
{
  "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

Send example to Inspect → View as JSON

team_domain_change

documented from Slack docs (example)

Workspace domain changes

Identified by event.type field in the body Resource workspace

slack-team-domain-change.json
{
  "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

Send example to Inspect → View as JSON

team_rename

documented from Slack docs (example)

Admin changes the workspace name

Identified by event.type field in the body Resource workspace

slack-team-rename.json
{
  "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

Send example to Inspect → View as JSON

Other Slack events

call_rejected

documented from Slack docs (example)

User turns down a call shared in a DM

Identified by event.type field in the body

slack-call-rejected.json
{
  "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

Send example to Inspect → View as JSON

entity_comments_requested

documented from Slack docs (example)

User opens or pages a Work Objects comments tab

Identified by event.type field in the body

slack-entity-comments-requested.json
{
  "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

Send example to Inspect → View as JSON

entity_details_requested

documented from Slack docs (example)

User clicks a Work Objects unfurl or refreshes its flexpane

Identified by event.type field in the body

slack-entity-details-requested.json
{
  "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

Send example to Inspect → View as 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.

Not affiliated with Slack. Facts are compiled from public sources and linked inline.