Skip to main content

​
What It Does

  • Quickly post richly formatted messages to Slack channels or users without writing code.
  • Automate status alerts, campaign reports, or deal updates with custom Block Kit layouts.
  • Schedule posts or reply in threads so your team stays informed at the right time.
  • Keep your GTM or RevOps workflow in sync with actionable Slack messages.

​
🏁 Getting Started

Slack Node config screenshot
1

Select Account

Choose your connected Slack workspace.
2

Configure Inputs

Pick the channel or user, then set up your blocks and message preferences.

​
Inputs

​
🛠️ Required Fields

  • Slack Connection (✅)
    Choose the Slack workspace where this message will be sent.
    Why it matters: Ensures your workflow can post messages to the correct team.
  • Channel (✅)
    Select a public or private channel, user, or group to receive the message.
    Why it matters: Targets the right audience so alerts and updates land where your team collaborates.

​
🎯 Optional Fields

  • Notification Text (⚪️)
    Provide a plain-text summary that appears as the Slack notification.
    Why it matters: Gives recipients context at a glance, even before they open the Block Kit content.
  • Send as User (⚪️)
    Toggle to post the message as the authenticated user instead of a bot (defaults to false).
    Why it matters: Makes messages feel more personal when they come from a teammate.
  • Schedule Message (⚪️)
    Use ISO 8601 datetime to schedule up to 120 days ahead (e.g., 2014-01-01T00:00:00Z).
    Why it matters: Plan updates or campaign reports to post at optimal times without manual effort.
  • Include link to Pipedream (⚪️)
    Toggle whether to append a Pipedream link at the end of your message (defaults to true).
    Why it matters: Easily trace back to the workflow that generated the message.
  • Customize Bot Settings (⚪️)
    Enable custom username and icon options for your bot.
    Why it matters: Aligns alerts with your team’s branding or specific use cases.
  • Reply to Thread (⚪️)
    Toggle to reply to an existing thread instead of posting a new message.
    Why it matters: Keeps related conversations organized in one place.
  • Add Message Metadata (⚪️)
    Attach custom metadata event type and payload for downstream processing.
    Why it matters: Supports advanced integrations by labeling messages programmatically.
  • Configure Unfurl Settings (⚪️)
    Enable or disable link and media previews in your message.
    Why it matters: Controls clutter and ensures previews appear only when needed.
  • Add Blocks - Reference Existing Blocks Array or Configure Manually? (⚪️)
    Choose to pull a pre-built array of blocks from a previous step or define up to 5 blocks here.
    Why it matters: Reuse templates or build custom messages on the fly.

​
Output

When this action runs, it returns the Slack API response including ts, channel, and the full message object. Use these values in downstream steps to log activity, update dashboards, or trigger follow-ups.
Slack Node output screenshot
If a thread timestamp already exists, the node will post replies accordingly and return the parent ts for consistency.

​
How It Works

  1. Takes your configured inputs and Block Kit array (either referenced or built here).
  2. Optionally schedules or sets thread context based on your settings.
  3. Sends the message via the Slack workspace connection.
  4. Emits the full Slack response for any downstream logging or automation.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Campaign Report”Send a daily deal summary to #sales-team at 9 AM PST.”
Deal Hygiene Alert”Post to my DMs when an opportunity hits Stage Closed Won.”
Threaded Feedback Request”Reply in thread when a new lead is added to pipeline.”

​
✨ Pro Tips

  • Use Add Blocks to reuse message templates across workflows.
  • Reference dynamic values with @ColumnName or the Insert Input button.
  • Schedule end-of-day reports to land in Slack when your team checks in.

​
⚠️ Important Considerations

  • Scheduled messages can’t be set for the past or beyond 120 days.
  • Bot customization options are ignored if you choose Send as User.
  • Ensure your Slack connection has permission to post to private channels or DMs.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
No message appears in channelWrong channel ID or permissionsVerify the channel exists and reauthorize the app
Blocks not renderingInvalid Block Kit JSON or missing keysUse the Block Kit Builder link to validate layout
Scheduled message failsDate out of rangeEnsure post_at is within the next 120 days

​
📝 FAQ

✅ Yes — toggle Send as User to true and the message will appear from you.
You can configure up to 5 blocks here, or reference a larger array from a previous step.
Yes — action nodes like this do not cost credits.

​
💰 Pricing

ActionCredit Cost
Post Block Kit MessageFree
Action nodes run as part of your workflow at no extra credit cost.

Drop this Slack action into your flow to automate rich notifications and keep your GTM team aligned — effortlessly. 🚀

🎯 Ready to elevate your Slack alerts? Add this node and watch your team stay in sync—fast! 🚀