Skip to main content

​
What It Does

  • Automatically fires whenever a new Slack channel is created in your workspace.
  • Keeps RevOps and SalesOps teams informed of new collaboration spaces.
  • Powers automated onboarding or notification workflows for new channels.
  • Syncs channel metadata (ID, name, creator) into CRMs or reporting dashboards.
  • Eliminates manual checks so your data stays fresh and actionable.

​
🏁 Getting Started

Slack Node config screenshot
1

Select Account

Choose your connected Slack workspace where you want to detect new channels.
2

Configure Inputs

Verify the workspace connection and set any filters (e.g., public only).

​
Inputs

​
🛠️ Required Fields

  • Select Slack Workspace (✅)
    Pick the Slack account that will emit channel creation events.
    Why it matters: Ensures events come from the right workspace, so downstream workflows trigger on the correct channels.

​
🎯 Optional Fields

This node has no optional inputs.

​
Output

This trigger emits a payload each time a new channel is created, including:
  • channel_id: Unique identifier for the channel.
  • name: The channel’s display name.
  • creator_id: User ID of who created the channel.
  • created_at: Timestamp of creation.
This structured data can flow into downstream nodes for alerts, CRM updates, or analytics.
Slack Node output screenshot
Slack channel names are unique per workspace and each event includes a channel ID to avoid duplicates.

​
How It Works

  1. Listens to your selected Slack workspace.
  2. Watches for the “channel_created” event from Slack.
  3. Emits a structured event with channel details to your workflow.
  4. Triggers downstream actions like automated messaging, CRM syncs, or reporting updates.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Onboard New Channels“When a new Slack channel is created, send a welcome message.”
CRM Channel Tagging“Tag new channels in Salesforce with channel name and creator.”
Channel Hygiene Alerts“Notify ops if private channels are created without approval.”

​
✨ Pro Tips

  • Confirm your Slack bot has the channels:read scope to detect channels.
  • Use @ColumnName or the Insert Input button to pass channel_id downstream.
  • Filter by public or private channels to avoid unnecessary triggers.

​
⚠️ Important Considerations

  • Large workspaces generate many events—use filters to limit noise.
  • Ensure your Slack token stays refreshed to prevent dropped events.
  • Private channel events require explicit bot invitations to each channel.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
No events on new channelsBot missing channel scopesGrant channels:read and reinstall the app
Duplicate channel eventsWorkspace sending retry attemptsAdd debounce or dedupe logic downstream
Missing private channel eventsBot not invited to private channelsInvite the bot to the private channels needed

​
📝 FAQ

Yes — invite the Slack bot to your private channels so it can listen for creations.
You can add multiple Slack connection nodes, one per workspace, to cover all your teams.
This is a trigger node, since it fires automatically when Slack sends a channel_created event.

​
💰 Pricing

ActionCredit Cost
Trigger Run (per event)1 credit
Trigger nodes that start workflows (like “New Channel Created”) cost 1 credit per event. All other enrichment or formatting nodes are free.

Drop this Slack node into your flow to automate channel alerts and keep your communication pipelines clean — automatically. 🚀