Why Doesn't My Custom Slack App Identity Appear on Triggered Messages?

Last updated: May 14, 2026

If you've installed a Custom Slack App for your agent, you might notice that its custom branding (name and logo) only appears in certain situations.

The Short Answer

Custom Slack App branding is only applied when an agent is invoked directly via an @mention in a Slack channel or thread. If the agent is invoked via an automated trigger or a workflow, messages will use the generic Gumloop bot identity instead.

Why This Happens

  • @Mentions: When a user explicitly tags the custom agent in Slack, Gumloop uses the specific Slack App's bot token associated with that agent. This applies your custom name and avatar to the response.

  • Slack Triggers: Gumloop's standard Slack Triggers (which automatically listen for messages in a channel without mentions) run on the generic workspace integration, not your Custom Slack App. They do not have access to apply the custom branding.

  • Workflows & Agent Nodes: If a workflow sends a Slack message (even if it uses an Agent Node internally), it uses the standard Slack integration. The workflow does not operate with the Custom Slack App's context, so the message defaults to the generic Gumloop identity.

Workaround

Currently, the only way to ensure your agent uses its custom brand identity is to have users directly @mention the bot (e.g., @SalesAssistant) to invoke it. Automated, trigger-based messages cannot carry the custom app branding.

Note: You cannot use a workflow to automatically @mention your Custom Slack App to trigger it. To trigger an agent, a user's profile is needed to attribute the user's permission, credentials, and credits.

Related Docs