Skip to content
Solución de problemas Slack Member Admin

Channel links in Slack messages aren't working

Channel links in Slack messages aren’t working

Dailybot posts a message that mentions a channel or includes a link, but clicking it errors, goes nowhere, or says you do not have access. Slack resolves channel links using IDs and membership. If the channel is private, renamed, archived, or from another workspace, the link behaves differently than a public channel URL in a browser.

Quick check

  • Membership — Join the channel manually first, then click the link again. Private channels hide from people who are not members.
  • Workspace — Confirm the link targets a channel in the same Slack workspace where Dailybot is installed for your org.
  • Channel still exists — Archived or deleted channels break old links even if Dailybot cached a name.
  • Invite Dailybot — For private channels, /invite @Dailybot so the bot can resolve and post consistently.
  • Client vs web — Try both Slack desktop and web; rare client bugs affect link parsing.

Common causes and fixes

Private channels

Slack will not open a private channel you have never joined. Ask a member to invite you, or ask an admin to post an invite link through normal Slack means. After you join, Dailybot-generated references should work the same as native Slack mentions. If Dailybot should post into that private channel, add the bot before relying on deep links in automated messages.

Channel ID changes after migration

Enterprise Grid moves, exports, or workspace merges sometimes remap channel IDs. Old messages from Dailybot may embed stale IDs. Ask an admin whether a migration happened recently. New posts after reconnecting the Slack integration usually pick up fresh IDs. For critical runbooks, edit the template to re-select the channel from the picker instead of pasting a manual link.

Workspace permissions

Org-wide Slack policies can block jumping from app-generated links or restrict unfurling. Compare behavior for a plain human-posted #channel link vs Dailybot’s link. If both fail, the limitation is workspace policy, not Dailybot. If only Dailybot fails, reconnect Slack under Integrations and regenerate the message template.

If someone edited a message or a macro truncated a URL, Slack receives an invalid deep link. Copy the full URL from the message source or rebuild the link using Slack’s channel right-click Copy link feature, then update the Dailybot template to use the canonical form.

If none of this worked

Before contacting support, gather:

  • Slack workspace name (non-secret) and whether you use Grid
  • Public vs private channel affected
  • Example message (screenshot) showing the broken link
  • Whether native #channel links from humans work in the same context
  • Whether the channel moved or was archived recently
  • Steps you already tried from this article

Then contact Dailybot support from the Help or Contact options in the product or on the website.