Creator OS
automationbotscreatorosslack

Slack chat.postMessage Custom Bot Name in 2026

You cannot set a bot name in chat.postMessage itself; you pass the identity with a bot token or per-message username override. Here is the working setup for branded

Creator OS · November 20, 2026 · 10 min read

Slack’s chat.postMessage has no bot name field. The name on a message comes from the token you post with, or from a username override. There is no bot_name parameter, and a bot token usually wins over any name you try to set in the payload. The three working paths are a properly named bot user, a per message username plus icon_emoji, or a tool that binds one branded Slack bot to each connected channel. This post walks through all three.

slack chat.postMessage: where the name comes from

  token          payload            what Slack shows
  -------------  -----------------  ---------------------
  bot token      (nothing)          the app's bot user name
  bot token      username, icon     custom name, if allowed
  user token     username, icon     the name you pass
  chat:write.
  customize        (nothing)        the app name on the token

Rule of thumb: the identity lives on the token.
The payload only overrides it, and only sometimes.
chat.postMessage has no bot name field. Identity comes from the token, then the payload.

What chat.postMessage Can and Cannot Rename in Slack

chat.postMessage can change the displayed name and avatar of one message, but it cannot rename the bot behind the token.

Here is the split, plainly:

What you want Possible with chat.postMessage? How
Set the bot’s permanent name No Rename the bot user in the Slack app settings instead
Show a different name on one message Sometimes username plus icon_emoji or icon_url
Set a permanent avatar No Upload it on the app’s bot user page
Choose the name per channel No Not a message level setting at all
Keep thread replies under the parent Yes thread_ts, same token and name

The parameter that trips people up is the one that does not exist. There is no bot_name in chat.postMessage. If you have been searching for it, that is why nothing came back. The identity is bound to the authentication token. The payload only offers an override, and whether Slack honors that override depends on the scopes and the app configuration behind the token.

So the real question is never “what do I put in the payload.” It is “which token am I posting with, and what is that token’s app called.”

This is the same shape of problem on every network: a post is only as branded as the account it leaves from. Creator OS handles it one level up, by giving each connected Slack channel its own account entry. We will get to that in method three.

Get started for $0

How to Post as a Custom Bot Name in Slack: 3 Methods

Pick the method that matches how often the name needs to change: once, per message, or per channel.

  1. Bot token, named once. Rename the bot user in the app settings. Every message the token sends carries that name. Best when the brand is stable and one app represents one team.
  2. username and icon_emoji per message. Pass the display name in the payload. Best when one integration posts on behalf of several teams or product lines and Slack lets the override through.
  3. A tool that binds one branded Slack bot per connected channel. Each connected Slack channel becomes its own account with its own connection. Best when you run several client channels and want the name tied to the connection rather than the code.

If you are still choosing a platform to sit behind these announcements, the post on Discord webhook versus bot for scheduled announcements covers the same identity question on the Discord side. The post on posting to Discord and Slack automatically is the broader workflow.

Method 1: Use a Bot Token So Messages Carry the App Identity

The bot token is the identity. Rename the bot user once and every message from that token is branded correctly.

Steps in the Slack app settings:

  1. Open your app at the Slack API dashboard and go to Features > App Home.
  2. Set Display Name (Bot Name) to what you want readers to see, for example “Acme Ops”.
  3. Set the Default Username under the same section. This is the fallback name used on plain messages.
  4. Upload the bot’s default icon on the same page.
  5. Reinstall the app to the workspace so the new identity is picked up by the existing token.

After that, a plain call with only a channel and text shows the bot name you set. The name is now a property of the credential, not of the request. That is the mental model worth keeping: a Slack bot’s name is a property of its token.

One caveat. If your app has the chat:write.customize scope, Slack may let you override the name at send time, and some configurations ignore overrides entirely. Test with one message in a private channel before you point an announcement workflow at a client facing one.

Method 2: Override username and icon_emoji Per Message

When one integration speaks for several brands, put the display name and icon in the payload on every call.

POST https://slack.com/api/chat.postMessage
Authorization: Bearer xoxb-your-bot-token
Content-Type: application/json

{
  "channel": "C0123456789",
  "text": "Deploy finished on staging. Build 4821 is live.",
  "username": "Acme Deploys",
  "icon_emoji": ":rocket:"
}

Swap icon_emoji for icon_url if you have a hosted image. Keep the field names exact: Slack reads username, not bot_name or display_name.

Two limits to keep in mind:

  • The override is per message. There is no way to say “this name for every message in this channel” in the payload.
  • The override can be refused. If the app lacks the customize scope, or the workspace enforces a fixed identity, Slack shows the app’s bot name and silently ignores your username.

The practical pattern is a small map in your code: product name to display name and emoji. One function fills the payload, and the name stops being a copy paste job in every template.

The same per message naming idea shows up outside Slack. If you post to Discord and Slack from one pipeline, the post on Discord webhook versus bot explains why the webhook name and the bot name behave differently.

Method 3: Post Through Creator OS With a Branded Bot Per Channel

Creator OS treats each connected Slack channel as its own account, so the bot identity is bound to the connection rather than to code you maintain.

How it works in practice:

  • Each Slack channel you connect becomes a separate account. A post goes to every connected channel unless you narrow it to specific accounts with account_ids.
  • There is no channel field to fill in. You target accounts, not channel IDs, which removes a whole class of copy paste errors.
  • A slack object on the post controls thread replies, link previews, and per message name and avatar.

That last point is the direct answer to the search. When you want one message to carry a different name or avatar, the slack object accepts username and iconUrl for that single message:

{
  "content": "Week one numbers are in. Replies open in thread.",
  "platforms": ["slack"],
  "account_ids": ["acc_slack_ops"],
  "slack": {
    "username": "Acme Weekly",
    "iconUrl": "https://yoursite.com/acme-icon.png"
  }
}

From the command line the same idea runs through posts:create, with the account chosen by id:

creatoros posts:create \
  --text "Week one numbers are in. Replies open in thread." \
  --accounts acc_slack_ops \
  --scheduledAt 2026-03-02T09:00:00Z \
  --timezone America/Toronto

Because the account is per channel, an Agency plan can keep one client’s channel and another client’s channel as separate accounts, each reached with its own scoped API key. That is the multi team case method one and two handle awkwardly.

If you want the agent to do this from a chat window, the MCP server exposes the same post tools, and read only connections cannot write. The post on running your social posting from a Slack bot covers the reply side, where a DM to the bot or an @mention lands in one inbox.

How to Post a Thread as a Custom Bot Name

Thread replies inherit the parent’s identity, so set the name on the first message and keep the same token for the rest.

The rules are short:

  • Every reply in the thread must use the same token as the parent message. A different token means a different name.
  • Pass thread_ts set to the parent message’s timestamp. That is what makes it a reply rather than a new post.
  • If you are overriding username, repeat the override on every reply. Do not assume the thread remembers it.
  • In Creator OS, use threadTs inside the slack object to make a thread reply. The account you target determines the name.

The failure people hit is a reply that shows the app name while the parent shows the custom name. That almost always means the reply went out through a different integration or a different token. Check the sending code path before you check the payload.

What Bot Name Shows Up When You Post to Discord and Slack at Once

There is no shared name across networks. Each platform uses its own connected account identity, so the same message can appear under two different names and that is expected.

The cross posting picture:

Network Where the name comes from Per message override
Slack The connected channel’s account username and iconUrl
Discord The bot installed in that server, one channel per account webhookUsername and webhookAvatarUrl

Note that Discord video posts are not listed, while Slack accepts images, up to 10 file attachments, and video. If you are choosing between a webhook and a bot for the Discord half, the webhook versus bot post is the one to read.

The practical takeaway: name your Discord account and your Slack accounts separately, on purpose, and write down which name belongs to which audience. The missing_platforms field tells you when a network in a post is not connected, so a half branded announcement does not go out unnoticed.

FAQ

How do I change the bot name when using chat.postMessage?

You cannot rename the bot from chat.postMessage. The permanent name lives on the bot user in the Slack app settings, so rename it there and reinstall the app. For a single message you can pass username and icon_emoji or icon_url, but Slack only honors that override in some app configurations.

Why does my Slack bot post show as the app name instead of a custom name?

Slack falls back to the app’s identity when the token is not allowed to customize, or when no username was sent at all. It also happens when the reply goes out through a different integration than the parent message. Check the scope and the sending code path before you change the payload.

Can I set a different bot name for each Slack channel?

Not inside chat.postMessage. The name belongs to the token, and there is no channel level name setting. The clean way to do it is one connection per channel, which is how Creator OS models Slack, where each connected channel is its own account.

Does the username override work with a bot token in Slack?

It depends on the app. With the customize scope and a workspace that allows it, username and icon_emoji override the displayed identity for that message. Without it, Slack shows the app’s bot name and ignores the field. Test one message in a private channel before relying on it for client facing announcements.

How do I post a threaded reply as a custom bot name in Slack?

Send every reply with the same token as the parent message and set thread_ts to the parent’s timestamp. If you are overriding the name, repeat username on each reply rather than assuming the thread keeps it. In Creator OS, the equivalent is threadTs inside the slack object on the post.

Get started with Creator OS

If you would rather not maintain the token, the scopes and the per message overrides yourself, Creator OS can hold the Slack connection for you. Each connected channel is its own account, posts go to every connected channel unless you narrow them with account_ids, and a DM to the bot or a message that @mentions it arrives in the same inbox as your comments and DMs from the other networks.

Sign up at https://www.creatoros.ca/sign-up. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included.

To watch the setup rather than read it, the walkthroughs are on the KevBuildsApps YouTube channel, and the launch video is at https://www.youtube.com/watch?v=-QBJH_PK3pY. The full Slack reference, including the slack object fields, is at the Slack API docs, and a complete posting example sits in publish everywhere.

Get started for $0
Free trial for new subscribers. Cancel anytime.

Keep reading