Trigger Communications

Triggers when a user clicks a button or interacts with a Block Kit element in a Slack message. Useful for building approval workflows, interactive forms, and action-based automations.

At a Glance

FieldValue
Trigger IDslack-new-interaction-event
CategoryCommunications
Tagsslack, communication, interaction, button, approval, block-kit

Trigger Configuration

FieldTypeRequiredDescription
conversationsarrayNoOnly listen for interactions in these channels. Leave empty for all channels.
action_idsarrayNoOnly listen for these specific action IDs (button identifiers). Leave empty for all actions.

Trigger Result

FieldTypeRequiredDescription
triggeredAtstringYesTimestamp when the event was received (UTC, RFC3339 format)
action_idstringNoThe action_id of the clicked button or interactive element
valuestringNoThe value attached to the button (can be JSON-encoded data)
userstringNoUser ID who performed the interaction
channelstringNoChannel ID where the interaction occurred
message_tsstringNoTimestamp of the message that was interacted with
response_urlstringNoURL to send follow-up messages or update the original message

Workflow Root Example

json
{ "nodes": { "root": { "type": "slack-new-interaction-event", "payload": { "conversations": [], "action_ids": [] }, "children": [ "log_event" ] }, "log_event": { "type": "log", "payload": { "message": "Triggered at {{$trigger.triggeredAt}}" }, "children": [] } }}

Downstream nodes can use {{$trigger.triggeredAt}} and any result fields listed above. Event triggers usually expose the raw source payload under a field such as event, body, trade, or raw.

Ask a question... ⌘I