This document outlines the functionality and use cases for the Slack Block Kit Sender node, which enables sending richly formatted, interactive messages using Slack’s Block Kit framework.

​
Channel Access Guide

​
Private Channels

To send Block Kit messages to private channels, both conditions must be met:
  1. You must be a member of the private channel
  2. The Gumloop bot must be in the channel
Important Notes:
  • Private channels won’t appear in the dropdown if you’re not a member, even if the bot is present
  • For sensitive automation, use your Personal workspace instead of shared workspaces
  • To add the bot, you have two options:
    1. Type /invite @Gumloop in the channel, OR
    2. Click the channel name → Add integrations/Add app → Search for “Gumloop”

​
Public Channels

  • All public channels where the Gumloop bot is present will be available
  • Add the bot using either:
    • /invite @Gumloop command in the channel
    • Channel name → Add integrations/Add app → Search for “Gumloop”

​
Direct Messages (DMs)

  • Supports sending messages to Direct Messages
  • Select a user from the dropdown or use their user ID
Alt text

​
When to Use

The Block Kit Sender node is ideal when you need to:
  • Create structured, visually appealing messages
  • Add interactive elements like buttons, hyperlinks, and embedded images
  • Present data in organized layouts with headers, sections, and dividers
  • Share status updates with rich formatting
  • Create consistent message templates
  • Display complex information hierarchies

​
Node Inputs

  • Channel: The Slack channel where the message will be sent (e.g., “#general”, “#team-updates”)
  • Blocks JSON String: JSON-formatted Block Kit content defining your message layout and components
  • Blocks Description (Optional): Text description for accessibility/notifications and mobile push alerts
  • Thread ID (Optional): For replying in specific message threads

​
Show More Options

  • Send as user profile: When enabled, this uses the user’s scope to send messages
    • The message appears as sent by the user, not the bot
    • Requires user authentication rather than bot authentication
    • Useful for personal messaging or when you want messages to appear from your account

​
Node Output

  • Posted Thread ID: The unique identifier of the sent message thread
  • Message Status: Success/failure of message delivery

​
Example Implementations

​
1. Project Update Template

Perfect for regular team updates with clear progress indicators. 
[
  {
    "type": "header",
    "text": {
      "type": "plain_text",
      "text": "🚀 Project Update",
      "emoji": true
    }
  },
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": "Hello <#C05QUSA4CC9>! Here's your weekly project status:"
    }
  },
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": "*Current Progress:*\n• Phase 1: ✅ Complete\n• Phase 2: 🚧 In Progress `(75%)`\n• Phase 3: ⏳ Pending"
    }
  },
  {
    "type": "context",
    "elements": [
      {
        "type": "mrkdwn",
        "text": "📅 Next review: Monday at 10 AM"
      }
    ]
  }
]
Preview:
🚀 Project Update Hello #project-team! Here’s your weekly project status: Current Progress: • Phase 1: ✅ Complete • Phase 2: 🚧 In Progress (75%) • Phase 3: ⏳ Pending 📅 Next review: Monday at 10 AM

​
2. Interactive Support Ticket

Useful for creating actionable support tickets with response options. 
[
 {
   "type": "header",
   "text": {
     "type": "plain_text", 
     "text": "🎫 New Support Ticket",
     "emoji": true
   }
 },
 {
   "type": "section",
   "text": {
     "type": "mrkdwn",
     "text": "*Ticket ID:* #1234\n*Priority:* High\n*Reported by:* <@U07L10GLL80>"
   }
 },
 {
   "type": "section", 
   "text": {
     "type": "mrkdwn",
     "text": "*Issue Description:*\n```Unable to access production database. Error occurs during authentication.```"
   }
 },
 {
   "type": "actions",
   "elements": [
     {
       "type": "button",
       "text": {
         "type": "plain_text",
         "text": "View Details",
         "emoji": true
       },
       "url": "https://www.gumloop.com/",
       "value": "view_1234"
     }
   ]
 },
 {
   "type": "context",
   "elements": [
     {
       "type": "mrkdwn",
       "text": "🕐 Reported: 2024-11-26 14:30 UTC"
     }
   ]
 }
]
Preview:
🎫 New Support Ticket Ticket ID: #1234 Priority: High Reported by: @Sarah Issue Description: Unable to access production database. Error occurs during authentication. [View Details] 🕐 Reported: 2024-11-26 14:30 UTC

​
3. Performance Report Template

Great for sharing metrics and achievements in a structured format. 
[
  {
    "type": "header",
    "text": {
      "type": "plain_text",
      "text": "📊 Q4 Performance Report",
      "emoji": true
    }
  },
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": "*Team Lead:* <@U07L10GLL80> | *Department:* <#C05QUSA4CC9>"
    },
    "accessory": {
      "type": "image",
      "image_url": "https://i.sstatic.net/JOiNx.png",
      "alt_text": "Team performance graph"
    }
  },
  {
    "type": "divider"
  },
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": "*Key Metrics:*\n```• Revenue: $1.2M (+15%)\n• Customer Growth: 2.5k (+30%)\n• Response Time: 2h (-50%)```"
    }
  },
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": "*Team Achievements:*\n• Launched 5 major features\n• Reduced bug backlog by 40%\n• Achieved 99.9% uptime"
    }
  }
]
Preview:
📊 Q4 Performance Report Team Lead: @Sarah | Department: #sales-team [Graph Image] Key Metrics: 
• Revenue: $1.2M (+15%)
• Customer Growth: 2.5k (+30%)
• Response Time: 2h (-50%)
Team Achievements: • Launched 5 major features • Reduced bug backlog by 40% • Achieved 99.9% uptime

​
Common Use Cases

  1. Automated Alerts
    • System status updates
    • Performance monitoring alerts
    • Security notifications
    • Deployment status messages
  2. Team Communication
    • Sprint updates
    • Meeting summaries
    • Project milestones
    • Team announcements
  3. Interactive Workflows
    • Approval requests
    • Incident management
    • Task assignments
  4. Data Visualization
    • Performance metrics via graphs
    • Analytics reports
    • Usage statistics
    • Health checks

​
Important Considerations

  1. Authentication: Set up Slack authentication in Gumloop’s Credentials page
  2. Channel Access: Add Gumloop to channels using /invite @Gumloop
  3. Private Channels: Ensure both you and the bot have access before sending messages
  4. JSON Testing: Validate layouts in Block Kit Builder
  5. Loop Mode: Available for sending multiple messages

​
Learn More