Connecting Slack to action builder
Before you can include external actions in your action flows, you must connect the action builder to the external system.
- All external actions performed by an action flow are attributed to the user who connected the external system. Therefore, it is a best practice to use a dedicated service account rather than personal credentials when connecting to each external system.
- All integrations request access to necessary scopes. However, it's important that you review and validate the scopes before authorizing the connection to the external system.
- When managing credentials for API key-based tools, such as OpenAI, it's best to store keys in a secure vault or credential manager.
- In Admin Center, click
Apps and integrations in the sidebar, then select Actions > Action flows. - Create or edit an action flow.
- Open the step sidebar.
- Under External actions, click Slack.
- Click Connect.
- Use Slack to authenticate the account.
To complete authentication, you must invite the Zendesk connector app:
/invite @Zendesk Connector.Note: All external actions performed by an action flow are attributed to the user who connected the external system. Therefore, it is a best practice to use a dedicated service account rather than personal credentials when connecting to each external system.
After you've connected to the system, you'll see an indicator that it's connected and details about the instance you're connected to, as well as the actions available for Slack.
Using Slack actions in action flows
Slack action steps can be used in action flows to streamline communication and make sure users know about other things being performed by action flows. For example, you can send messages to channels and individual users alerting them of new tickets or Jira issue assignments, post AI-generated summaries of tickets into a Slack thread, escalate direct messages to public channels for broader visibility, add reactions to automatically acknowledge messages, or extract message details for analysis and reply with AI-generated content.
Posting a message to a channel
Use the Post message to channel action to send a message to a public or private channel.
This action has the following inputs and outputs:
| Variables | |
|---|---|
| Inputs |
channel,
message
|
| Output |
channel, ts,
ok
|
Sending a direct message
Use the Send direct message action to send a direct message to a specific user.
| Variables | |
|---|---|
| Inputs |
email, message
|
| Output | Full message data |
Replying to a message in a thread
Use the Reply to message thread action to post a reply to a message in a thread. This step can create a thread or reply within an existing thread.
This action has the following inputs and outputs:
| Variables | |
|---|---|
| Inputs |
email, message
|
| Output | None |
Fetching all messages in a thread
Use the Fetch thread messages action to retrieve all messages in a thread.
This action has the following inputs and outputs:
| Variables | |
|---|---|
| Inputs |
channel, thread_ts,
reply_ts
|
| Output | messages |
Adding a reaction to a message
Use the Add reaction action to add an emoji reaction to a message.
This action has the following inputs and outputs:
| Variables | |
|---|---|
| Inputs |
channel, name,
timestamp
|
| Output | success |
Fetching a message
Use the Fetch message action to retrieve the content and metadata of a message.
This action has the following inputs and outputs:
| Variables | |
|---|---|
| Inputs |
channel,
timestamp
|
| Output |
text, user
|
Finding a user
use the Find user action to retrieve a Slack user so they can be referenced later in the action flow.
This action has the following inputs and outputs:
| Variables | |
|---|---|
| Inputs | user_id |
| Output |
display_name, email,
real_name,
user_id
|