Slack Action Block

The Slack Action Block enables seamless integration with Slack workspaces, allowing you to automate messaging, retrieve channel and user information, and enhance team communication within your workflows. With support for rich formatting and interactive elements, this block streamlines real-time collaboration.

Tip: Use the Slack Action Block to automate notifications, approvals, or data sharing, keeping your team aligned and informed.

Key Features

Message Sending: Send messages to channels, groups, or direct messages.
Channel Management: Retrieve and interact with workspace channels.
User Integration: Access user details and send personalized messages.
OAuth Authentication: Securely connect to Slack workspaces.
Rich Formatting: Support for Slack’s markdown, attachments, and blocks.
Real-Time Delivery: Instant notifications and updates.

✅ Perfect for:

Sending alerts when something goes wrong
Notifying teams when workflows complete
Sharing reports and updates automatically
Creating automated status updates
Building approval workflows through Slack
Keeping remote teams in sync

❌ Not ideal for:

Personal email notifications (use Email block)
Long-form documentation (use file sharing)
External customer communications (use Email or other channels)

To integrate the Slack Action Block, create and configure a Slack app:

Create a Slack App:
- Visit Slack API (opens in a new tab).
- Click Create New App, select From scratch, and enter app details.
- Choose your target workspace.
Configure OAuth Scopes: Ensure the following bot token scopes are enabled:
```
- chat:write
- channels:read
- users:read
- im:write
- groups:read
```
Install the App:
- Install the app to your workspace.
- Copy the Bot User OAuth Token.
- Note the App ID and Client Secret for reference.

🚨 System Alerts

Error Detected → Check Severity → Send Slack Alert to #tech-alerts → Log Issue

When your website goes down, instantly alert the tech team

The block uses OAuth 2.0 for secure authentication:

Client ID: Found in your Slack app’s settings.
Client Secret: Generated during app creation.
Redirect URI: Configured in the Slack app for OAuth redirects.
Bot Token: Obtained after installing the app to your workspace.

⚠️

Caution: Store OAuth tokens and secrets securely using environment variables to prevent unauthorized access.

🔔 Approval Requests

Expense Submitted → Send to #approvals → Manager Approves → Update Database → Notify Employee

Route expense approvals through Slack for quick decisions

Easy Setup Guide

Send messages to channels, direct messages, or groups with rich formatting.

Configuration Options:

Channel: Specify the target (channel, user, or group).
Message: Craft text with Slack’s markdown formatting.
Attachments: Include rich attachments or blocks.
Thread: Reply to existing messages in a thread.

Channel Selection:

// Supported channel formats
"#general"           // Public channel
"@username"          // Direct message
"C1234567890"       // Channel ID
"D1234567890"       // Direct message ID
"G1234567890"       // Private group ID

Lists and Structure:

Here's what happened:
• New customer signed up
• Payment processed successfully  
• Welcome email sent

// Code blocks
"`inline code`"
"```\ncode block\n```"

// Lists
"• Bullet point\n• Another point"
"1. Numbered list\n2. Second item"

Get Channels

Retrieve a list of channels in the workspace.

Response Structure:

{
  "channels": [
    {
      "id": "C1234567890",
      "name": "general",
      "is_channel": true,
      "is_group": false,
      "is_im": false,
      "is_member": true,
      "is_private": false,
      "is_archived": false,
      "topic": {
        "value": "Company-wide announcements",
        "creator": "U1234567890",
        "last_set": 1234567890
      },
      "purpose": {
        "value": "General discussion",
        "creator": "U1234567890",
        "last_set": 1234567890
      },
      "num_members": 150
    }
  ]
}

Common Message Types

Fetch user details from the workspace.

Response Structure:

{
  "users": [
    {
      "id": "U1234567890",
      "name": "john.doe",
      "real_name": "John Doe",
      "display_name": "John",
      "email": "john.doe@company.com",
      "is_admin": false,
      "is_owner": false,
      "is_bot": false,
      "is_app_user": false,
      "deleted": false,
      "profile": {
        "title": "Software Engineer",
        "phone": "+1-555-0123",
        "image_24": "https://avatar.url",
        "image_32": "https://avatar.url",
        "status_text": "Working remotely",
        "status_emoji": ":house_with_garden:"
      }
    }
  ]
}

📊 Report Messages

� Daily Sales Report - {{date}}

### Basic Notifications

```javascript
// Simple alert
{
  "channel": "#alerts",
  "message": "🚨 System maintenance scheduled for tonight at 10 PM"
}

// Status update
{
  "channel": "#dev-team",
  "message": "✅ Production deployment completed successfully"
}

Rich Content Messages

{
  "channel": "#general",
  "message": `
📢 *New Feature Launch*
 
We're thrilled to announce our latest feature!
 
*Key Benefits:*
• Improved performance
• Enhanced user experience
• Stronger security
 
Learn more: <https://docs.company.com|Documentation>
 
Questions? Contact <@U1234567890> or join <#C5678901234|support>
  `
}

Alert Messages

{
  "channel": "@john.doe",
  "message": `
🔴 *Critical Alert: System Issue*
 
*Service:* Authentication
*Error:* Database timeout
*Time:* ${new Date().toISOString()}
*Severity:* High
 
Assigned to: {{assigned_agent}}

Data Reports

{
  "channel": "#metrics",
  "message": `
📊 *Daily Metrics Report*
 
*Key Stats:*
• New Users: 1,247 (+12%)
• Revenue: $15,890 (+8%)
• Support Tickets: 23 (-15%)
• Uptime: 99.98%
 
*Top Features:*
1. User Dashboard (94% engagement)
2. Mobile App (87% retention)
3. API Integration (99.5% success rate)
 
Great job, team! 🎉
  `
}

🔄 Conditional Messages

Message Attachments

Include rich attachments for structured content:

{
  "channel": "#updates",
  "message": "New release available",
  "attachments": [
    {
      "color": "#36a64f",
      "title": "Production Release v2.1.0",
      "title_link": "https://github.com/company/app/releases/v2.1.0",
      "text": "Latest features and bug fixes",
      "fields": [
        {
          "title": "Version",
          "value": "2.1.0",
          "short": true
        },
        {
          "title": "Environment",
          "value": "Production",
          "short": true
        }
      ],
      "footer": "GitHub",
      "footer_icon": "https://github.com/favicon.ico",
      "ts": 1234567890
    }
  ]
}

Interactive Elements

Add buttons or selections for interactive messages:

{
  "channel": "#approvals",
  "message": "Deployment approval needed",
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "*Deployment Request*\nVersion 2.1.0 ready for production"
      }
    },
    {
      "type": "actions",
      "elements": [
        {
          "type": "button",
          "text": {
            "type": "plain_text",
            "text": "Approve"
          },
          "style": "primary",
          "action_id": "approve_deployment"
        },
        {
          "type": "button",
          "text": {
            "type": "plain_text",
            "text": "Reject"
          },
          "style": "danger",
          "action_id": "reject_deployment"
        }
      ]
    }
  ]
}

Thread Replies

Reply to existing threads:

{
  "channel": "#support",
  "message": "Issue resolved! ✅",
  "thread_ts": "1234567890.123456"
}

Integration Patterns

Alert System

Monitor: Detect system issues.
Evaluate: Assess issue severity.
Notify: Send Slack alerts to the team.
Escalate: Notify managers for critical issues.
Resolve: Share resolution updates.

Approval Workflow

Request: User submits a request.
Notify: Alert approvers via Slack.
Interact: Approve or reject using buttons.
Update: Reflect status in the workflow.
Confirm: Send confirmation message.

Daily Reports

Collect: Gather metrics or data.
Format: Generate a structured report.
Deliver: Send to team channels.
Archive: Store for future reference.
Analyze: Compare with historical trends.

Error Handling

Authentication Errors

"Invalid token"

Verify the bot token is valid and current.
Ensure the app is installed in the workspace.
Confirm required OAuth scopes are granted.

Channel Access Errors

"Channel not found"

Check channel name or ID accuracy.
Ensure the bot has access to the channel.
Verify the channel exists and isn’t archived.

Message Formatting Errors

"Message too long"

Keep messages under Slack’s 4,000-character limit.
Split long messages into multiple parts.
Use attachments for extended content.

Rate Limiting

"Rate limit exceeded"

Implement exponential backoff for retries.
Reduce message frequency.
Batch messages when possible.

⚠️

Caution: Monitor Slack API rate limits to avoid disruptions, especially in high-volume workflows.

Best Practices

Clear Messaging: Use concise, actionable language.
Consistent Formatting: Maintain uniform message styles.
Channel Relevance: Send messages to appropriate channels.
Secure Tokens: Store tokens securely in environment variables.
Monitor Delivery: Track message success and handle failures gracefully.

Response Mapping

Map Slack responses to workflow variables:

Message Responses

{
  "ok": true,
  "channel": "C1234567890",
  "ts": "1234567890.123456",
  "message": {
    "text": "Hello world",
    "user": "B123456 Bromek7890",
    "ts": "1234567890.123456"
  }
}
// Mapping
ok → {{messageSuccess}}
ts → {{messageTimestamp}}
channel → {{targetChannel}}

Channel Data

channels[0].name → {{firstChannelName}}
channels[*].name → {{allChannelNames}}
channels[is_member=true].name → {{memberChannels}}

User Data

users[0].real_name → {{firstUserName}}
users[*].email → {{allUserEmails}}
users[is_admin=true].name → {{adminUsers}}

Troubleshooting

Setup Issues

"App not found"

Confirm the app is created in the correct workspace.
Check app configuration and permissions.
Ensure the app is installed.

"Insufficient permissions"

Add missing OAuth scopes.
Reinstall the app with updated permissions.
Verify workspace admin policies.

Runtime Issues

"Message delivery failed"

Validate channel or user ID.
Check message format and length.
Ensure the bot is a channel member.

"Slow response times"

Check Slack API status (opens in a new tab).
Optimize message content.
Implement retry logic for failures.

Need Help? Contact support via the in-tool chat for assistance with setup or errors.

Node Display

The Slack Action Block displays:

Connection Status: Indicates setup and authentication state.
Target: Shows the selected channel or user.
Message Preview: Displays a truncated view of the message.
Status Indicators: Reflects delivery and error states.

Example Workflows

Incident Response

Detect: Identify a system issue.
Assess: Evaluate severity.
Alert: Notify the on-call team via Slack.
Update: Share progress updates.
Resolve: Confirm resolution.

Team Notifications

Trigger: Workflow completion or failure.
Format: Build a structured message.
Deliver: Send to team channels.
Track: Monitor team responses.

Customer Support

Receive: Log a customer ticket.
Assign: Route to the support team.
Notify: Alert the team via Slack.
Update: Share status updates.
Close: Confirm resolution with the customer.

Hunter.io Telegram