Slack events

This reference lists Slack events that Shipfox delivers to a Slack integration connection. See the Slack overview for authentication and setup.

Payload

For Events API deliveries, Shipfox keeps the Slack event fields and adds team_id, api_app_id, event_id, and event_time from the event envelope. Slack owns the remaining provider fields.

Shipfox discards events authored by the installed bot. This prevents an agent's Slack actions from triggering the same workflow again.

For slash_command, Shipfox exposes the command, text, workspace, channel, user, response URL, and trigger ID. It omits Slack's deprecated verification token.

Use Slack's provider references for the full Events API payloads and slash-command payload.

Trigger fragment

Replace slack_acme with the slug of your Slack integration connection:

triggers:
  on_mention:
    source: slack_acme
    event: app_mention

For trigger field rules, see the workflow schema reference.

Event catalog

app_mention

A Slack message mentions the installed app.

Emitted when: Slack sends an app_mention event to the installed app.

Payload: Shipfox-normalized payload.

Provider payload documentation

message

A message event arrives from a subscribed Slack conversation.

Emitted when: Slack sends a message event to the installed app.

Payload: Shipfox-normalized payload.

Provider payload documentation

reaction_added

A member adds an emoji reaction to a Slack item.

Emitted when: Slack sends a reaction_added event to the installed app.

Payload: Shipfox-normalized payload.

Provider payload documentation

slash_command

A user invokes a slash command for the installed app.

Emitted when: Slack sends a slash-command request to the installed app.

Payload: Shipfox-normalized payload.

Provider payload documentation