Slack Message Sender

This document outlines the functionality of the Slack Message Sender node, which enables sending simple text messages and formatted content to Slack channels or direct messages to users. For complex layouts and interactive elements, consider using Slack Block Kit Sender.

​

Channel Access Guide

​

Private Channels

To send 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 to Users

• You can send direct messages to any user in your Slack organization
• You can toggle between channel and user under Show more options
• The message will be sent from the Gumloop bot to the user
• Note:
  • These messages will not appear in your personal DM history with the user
  • You can only send direct messages to users within your Slack organization, not to external users

​

When to Use

The Slack Message Sender node is ideal when you need to:

• Send quick text updates to channels
• Send direct messages to team members
• Share file attachments
• Reply in threads
• Post basic formatted messages
• Set up automated notifications
• Create simple alerts

​

Node Inputs

• Send Type: Choose between “Channel” (default) or “User”
  • This option is available under “More options”
  • Channel: Send to a public or private channel
  • User: Send a direct message to a specific user
• Channel/User: The destination for your message
  • When Send Type is “Channel”: Select a channel (e.g., “#general”, “#team-updates”)
  • When Send Type is “User”: Select a user to receive the direct message
• Message: The text content of your message, supports basic formatting
• Thread ID (Optional): For replying to existing messages
  • You can fetch this from the Slack Message Reader node dynamically
• Attachments (Optional): Files to attach to your message

  To attach multiple files, you can separate them with a comma using the Join List Items node. Example Workflow

​

Node Output

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

​

Message Formatting

The node supports basic Slack formatting:

​

Text Formatting

*bold text*              → bold text
_italic text_            → italic text
~strikethrough~         → strikethrough
`inline code`           → monospace text

​

Block Formatting

> Block quote           → Indented quote
>>> Multi-line quote    → Multi-line indented quote

​

Code Blocks

```
Code block
Multiple lines
```

​

Lists

• Use regular hyphens for bullets
1. Numbers for ordered lists

​

Example Messages

​

1. Simple Status Update

🎯 Sprint Goals Update:
*Completed Tasks:*
• User authentication fixed
• API performance improved
• Documentation updated

_Next up:_ Dashboard optimization

Preview:

🎯 Sprint Goals Update:

Completed Tasks:

• User authentication fixed

• API performance improved

• Documentation updated

Next up: Dashboard optimization

​

2. System Alert

⚠️ *System Alert*
`Database CPU Usage: 85%`
> Action required: Scale up database instances

Preview:

⚠️ System Alert Database CPU Usage: 85%

Action required: Scale up database instances

​

3. Code Sharing

*New API Endpoint Added:*
```javascript
GET /api/v1/users/:id
Authorization: Bearer {token}

_Please update your clients accordingly._

Preview:

New API Endpoint Added:

GET /api/v1/users/:id
Authorization: Bearer {token}

Please update your clients accordingly.

​

Common Use Cases

1. Automated Notifications

   • Build status alerts
   • Monitoring alerts
   • Scheduled reminders
   • System health updates

2. Team Communication

   • Daily standups
   • Meeting reminders
   • Quick updates
   • Task assignments

3. Development Workflows

   • Deployment notifications
   • Error alerts
   • PR notifications
   • Build status updates

4. Support Operations

   • Ticket updates
   • Service status
   • Customer inquiries
   • Response tracking

5. User Notifications

   • Personal task reminders
   • Approval requests
   • 1:1 communication
   • Personalized updates

​

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
4. DM Behavior: Messages to users come from the Gumloop bot, not your account
5. Available Users: Only users in your Slack organization can receive direct messages
6. Loop Mode: Available for sending multiple messages to different channels or users