Schedule social media posts with Muse Code
Muse Code, Meta's terminal agent, can connect to a remote MCP server, so Bolta can be added to its settings file and signed in with one command. Bolta then drafts posts in your brand voice and holds them in review, and nothing is approved, scheduled or published until you say yes.
- Add Bolta to one JSON settings file and sign in with muse mcp login
- Drafts land in Bolta's review queue in your brand voice
- Terminal agent only: the Muse app and WhatsApp are not confirmed
Nothing is approved, scheduled or published until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
This is the Muse Code path. We have not confirmed a way to add Bolta in the Muse app or from WhatsApp.
Set up Bolta for acme.com.
Used Bolta · 3 actions
Bolta now knows Acme: what you sell, who it's for, and how you sound. I'd start with a weekly routine that turns each new blog post into posts.
Connect, then ask
- 01
Add Bolta and sign in
Add a bolta entry under mcp_servers in ~/.config/muse/settings.json, then run muse mcp login bolta and approve the brands in the browser window.
- 02
Ask for a draft
Start muse, type /mcp to see Bolta listed, then ask for a post. It is saved as a draft and waits for your yes.
What is and is not confirmed
Read this before you set up Muse
- Confirmed in Meta's Muse Code docs: remote MCP servers over streamable_http, an mcp_servers block in ~/.config/muse/settings.json, and OAuth sign-in with muse mcp login.
- Not confirmed: that the Muse app (phone, desktop or WhatsApp) accepts a Bolta MCP link. Meta says the app has custom connectors, but we could not read the steps.
- Not tested end to end: nobody has run a full draft, review and schedule round trip through Muse Code with Bolta yet.
- Not confirmed: how to send an API key in the headers field, and whether the optional Bolta skill shows up in muse skills list.
What happens between your terminal and Bolta
Muse Code is the client and Bolta is the server. Here is the path one request takes once the settings entry is in place.
- 01
Muse Code reads the settings file at startup
When you run muse, it loads ~/.config/muse/settings.json, checks schema_version and registers every mcp_servers entry, including bolta.
- 02
OAuth tokens come from muse mcp login
The login command opens bolta.ai in your browser. You tick the brands Muse Code may reach and approve, and Muse Code stores the sign-in. Meta says tokens refresh automatically.
- 03
Muse Code lists Bolta's tools
Over streamable HTTP at https://mcp.bolta.ai/mcp, Muse Code asks Bolta what it offers. /mcp shows the result as a live list.
- 04
Your request becomes a read of your brand
For a post, Muse Code first checks your brand and voice before writing anything.
get-voice-context - 05
The draft is saved, not sent
The post is saved in the brand you named as a draft, with no approval and no time attached.
save-post - 06
You decide in Bolta
Review the exact text in Bolta or tell Muse Code yes. Until then nothing is approved, scheduled or published, and your role and Safe Mode still apply.
list-inbox-items
Set up Muse
Connect once. Everything below works from Muse afterwards.
- 01
Have a Bolta brand with an account connected
Create a Bolta account at bolta.ai and add at least one brand. Connect at least one social account to it, or Muse Code will only be able to draft.
- 02
Install Muse Code
Run curl -fsSL https://dev.meta.ai/install.sh | bash, then muse --version to check it works. This is the terminal agent, not the Muse phone app.
- 03
Open the settings file
Open ~/.config/muse/settings.json and create it if it is missing. It must contain "schema_version": 1, or Muse Code stops at startup.
- 04
Add the Bolta server
Add an mcp_servers entry named bolta with transport streamable_http and url https://mcp.bolta.ai/mcp. Keep any settings already in the file, then save it.
- 05
Sign in to Bolta
Run muse mcp login bolta. A browser opens on bolta.ai. Sign in, tick the brands Muse Code may reach and approve. One connection covers one organization, and there is no key to copy.
- 06
Check the connection
Start muse and type /mcp. You should see bolta listed with its tools. If it is missing, check the url, the transport value and the schema_version line, then restart.
- 07
Optional: add the Bolta skill
Run npx skills add boltaai/bolta-skills --skill bolta, then muse skills list. Muse Code reads ~/.agents/skills and ~/.claude/skills. If Bolta does not appear, skip it, because the connection works without it.
- 08
Run a read-only check first
Ask: List my Bolta brands and the accounts connected to each. Do not change anything. Then ask for one draft and read the exact text back before you approve it in Bolta.
Connect Muse to Bolta
This is the Muse Code path. We have not confirmed a way to add Bolta in the Muse app or from WhatsApp.
Which ways to connect Bolta to Muse actually work
Muse is two products. This table keeps what Meta documents apart from what nobody has confirmed.
| Method | With Muse | How |
|---|---|---|
| Muse Code: mcp_servers entry plus muse mcp login | Not confirmed | Documented by Meta, not run with Bolta (streamable_http, OAuth sign-in). Not yet run as a full draft-to-schedule round trip with Bolta. |
| Muse Code: Bearer bolta_sk_ key in headers | Not confirmed | Meta lists a headers field and Bolta accepts a Bearer key, but the exact format Muse Code expects was not read. |
| Muse Code: the optional Bolta skill | Not confirmed | Meta documents the skill folders. We have not checked that muse skills list shows Bolta after npx skills add. |
| Muse app custom connectors | Not confirmed | Meta says custom connectors exist, but the steps and the auth types could not be read. |
| Muse inside WhatsApp | Not confirmed | We found no Meta statement that Bolta can be added there. Third-party posts say otherwise, and we do not repeat them. |
| Browser extension or plain webhook | Not available | Neither is a route we document for Muse Code. The MCP entry above is the documented path. |
What you can run in Bolta from Muse
Each row is an area of Bolta, with the real tools behind it.
Draft from what is in your repo
Muse Code can read a changelog, README or docs page in your working folder and hand the text to Bolta as a draft in your voice.
get-voice-contextsave-postCheck the rules before drafting
Ask what a network allows, such as length or media limits, so a draft is built to fit and is not rejected later.
get-posting-ruleslist-accountsRead the review queue aloud
Muse Code can list what is waiting and read each item back, so you decide from the exact text.
list-inbox-itemsget-postApprove after your yes
Once you say yes to named drafts, Muse Code passes the content fingerprint back, so a post that changed in between is not approved by mistake.
approve-many-postsreject-postPlan a repeating routine
Describe a rhythm in words. Bolta turns it into a plan you can edit, and the saved routine starts switched off.
planrevise-planconfirm-planactivate-routineLook back at results
Pull account analytics into the terminal before planning the next batch of posts.
get-account-analyticslist-account-insights
A release-day session in the terminal
An invented example of how a developer might use Muse Code with Bolta. The wording and numbers are made up.
- You
Read the v2.0 section of CHANGELOG.md and tell me what Bolta brands I have first.
- Tool call
list-workspacesReturns the brands this connection may reach.
- Tool call
list-accountsLists the social accounts connected to each brand.
- Muse
You ticked two brands, Acme Dev Tools and Acme Labs. Acme Dev Tools has LinkedIn and X connected. Which one is this release for?
- You
Acme Dev Tools. Draft one LinkedIn post and one X post, short, plain tone.
- Tool call
get-posting-rulesChecks length and media limits for LinkedIn and X.
- Tool call
save-postSaves two drafts. Nothing is scheduled.
- Muse
Both are saved as drafts, with the exact text above. Neither is approved, scheduled or published. Want any changes?
- You
Shorten the X one and drop the second sentence.
- Tool call
save-postEdits the X draft. It stays a draft.
- Muse
Updated. Here is the new X text. Still a draft. Tell me yes for either post and I will confirm the exact wording and time first.
- You
Leave them for now. I will look in Bolta after lunch.
- Muse
Understood. Both stay as drafts and will be in your review queue.
Muse Code or the Muse app
Meta ships two different things under one name. Only one has a documented way to add a remote MCP server.
Muse Code
Choose this if you work in a terminal and want Bolta connected today.
Meta documents mcp_servers in the settings file, the streamable_http transport and OAuth sign-in with muse mcp login. That is the path this page walks through.
Muse app
Choose this only if you cannot use a terminal, and expect to wait.
Meta says the app supports custom connectors, but we could not read the steps, so we do not know whether it takes a remote MCP link or which sign-in it uses. We will not tell you it works until it has been tried.
What can Muse do with Bolta?
- Turn a release note or changelog entry into a LinkedIn or X draft without leaving the terminal
- Have Muse Code read a README or docs page in your repo and draft posts that explain it
- Draft a week of posts in your brand voice, then review them in Bolta rather than in the shell
- Ask what is waiting for approval and have each draft read back before you decide
- Pull recent post results into the terminal before you plan the next batch
- Set up a weekly routine that drafts posts for your review, then close the terminal
What is the Bolta MCP?
The server Muse talks to when it works with Bolta.
MCP, the Model Context Protocol, is the open standard that lets an AI app call tools in another product. Bolta runs a hosted MCP server at https://mcp.bolta.ai/mcp. Your AI app discovers its 67 tools and calls them for you: list your brands, save a draft, plan a routine, read results.
One connection is one organization. You tick the brands the app may reach, and every call is checked against your role, so the app can never do more in Bolta than you can. Approving, scheduling and publishing need your yes.
Brands & accounts6 tools
The brands this connection reaches, who works on them and who can approve, their approval settings, connected social accounts, and each platform's posting rules.
list-workspaces, list-workspace-members, set-brand-approval, list-accounts, get-connect-link, get-posting-rules
Posts9 tools
Save a draft or edit a post with save-post, then publish it now or at a time with publish-post after the user says yes.
list-workspace-posts, get-post, save-post, publish-post, delete-post, bulk-create-posts, create-wordpress-blog-post, list-recently-deleted, restore-deleted
Review4 tools
Everything waiting for a yes: submit drafts to the team or send them to a named person for approval, approve one or many, reject with a reason, and work the inbox of routine and campaign drafts.
list-inbox-items, submit-for-review, approve-many-posts, reject-post
Plans6 tools
Have Bolta plan a routine or a campaign the way its own chat does, change it, then save it on the user's yes.
plan, plan-routine, plan-campaign, recommend-routines, revise-plan, confirm-plan
Routines10 tools
Work that repeats and runs in Bolta even with the app closed.
list-routine-templates, list-routines, get-routine, create-routine, update-routine, activate-routine, pause-routine, archive-routine, run-routine-now, list-routine-runs
Campaigns6 tools
One to four weeks of posts about one thing: a launch, an event, a season.
list-content-campaigns, get-content-campaign, create-content-campaign, update-content-campaign, analyze-content-campaign-source, set-content-campaign-status
Team versions4 tools
One idea written as one post per person on the team, each in their own voice.
plan-team-posts, update-team-post-plan, generate-team-post-drafts, get-team-post-plan
Voice & business8 tools
The brand's voice and business facts, and writing in that voice.
get-voice-context, get-voice-profile, create-voice-profile, update-voice-profile, list-business-dna, extract-business-dna, update-business-dna, voice-generate
Suggestions2 tools
What Bolta suggests changing, for a routine or the whole brand, from what people approved, edited and rejected.
list-suggestions, decide-suggestion
Replies10 tools
Find conversations worth joining, draft replies in the brand voice, and send them once the user says yes.
search-engagement-opportunities, list-engagements, get-social-content, draft-engagement-reply, draft-inbound-reply, publish-engagement-reply, reply-to-social-content, react-to-social-content, send-outreach-reply, update-outreach-reply
Results2 tools
How posts and accounts are performing.
list-account-insights, get-account-analytics
What to ask Muse Code
Replies are illustrative. Real wording and numbers come from your own Bolta workspace.
Read CHANGELOG.md and draft a LinkedIn post about the v2.0 release. Save it for my review.
I read the v2.0 entry and saved one LinkedIn draft in Bolta, written in your brand voice. Here is the exact text. It is not approved or scheduled. Tell me yes when you want to go ahead.
save-post
What is waiting for my approval in Bolta? Read each one back to me.
You have three items in review. I read each one back above. I have not approved or rejected anything. Say which ones you want approved and I will confirm the exact text first.
list-inbox-items
Plan a weekly Friday recap post for the engineering blog, drafts only.
Here is the plan: one draft each Friday for your review, with a Bluesky and LinkedIn version. It repeats even when your terminal is closed. Nothing is saved until you confirm, and it starts switched off until you say yes again.
plan, confirm-plan
How did my last five posts do? Suggest what to post next.
Here are the results for your last five posts, with the strongest one first. I suggest a follow-up on that topic. I have not drafted or scheduled anything.
get-account-analytics, list-accounts
What are the length limits for X and LinkedIn on my Acme brand before you draft anything?
I checked the posting rules for both accounts and listed the limits above. I have not written or saved a post yet.
get-posting-rules, list-accounts
Turn the Getting Started page in docs/ into two Bluesky drafts and show me the text.
I read the page and saved two Bluesky drafts in Bolta. Both texts are above. They are not approved or scheduled, and I will wait for your yes.
get-voice-context, save-post
Show me the current text of the draft I asked about earlier, then tell me if it changed.
Here is the draft as it stands now. If it differs from what you saw before, I will say so before you approve it.
list-workspace-posts, get-post
Works with the networks you have connected in Bolta
- X
- Threads
- Bluesky
What keeps running without Muse Code
Muse Code is a terminal session. When you close it, it does nothing for Bolta. Anything that continues runs on Bolta's side.
- A routine you set up through Muse Code lives in Bolta, so it repeats while your terminal is closed.
- A routine saves switched off. Turning it on takes its own yes from you.
- Routines draft for your review. Check your brand's approval settings in Bolta to see what, if anything, can go out without you.
- A draft saved before you closed the terminal stays in the review queue.
We have not seen Meta document a background mode for Muse Code, so we do not claim one.
The Muse Code settings block
Muse Code reads one JSON file. The Bolta entry sits next to anything already there, and the file must declare its schema version.
Meta also lists optional enabled and mode fields (required or optional) for each server. We have not tested what changing them does with Bolta, so the guide leaves them out.
| Field | Value | What it does |
|---|---|---|
| schema_version | 1 | Required at the top of the file. Without it Muse Code stops at startup. |
| mcp_servers.bolta | an object | The name you give the server. Use bolta. |
| transport | streamable_http | Tells Muse Code this is a remote HTTP server. |
| url | https://mcp.bolta.ai/mcp | Bolta's hosted MCP address. |
Muse Code does not sandbox MCP tools
Meta's documentation says MCP tools in Muse Code are not sandboxed. A server you connect can do whatever its tools allow, so connect only servers you trust.
Bolta narrows what it can do from its side. You tick which brands the connection reaches, your role in each brand still applies, and a post cannot be approved, scheduled or published until you say yes to that exact text.
- Pick only the brands you need on the permission screen.
- Ask for drafts only, and give your yes yourself in Bolta after reading the exact text.
- Read the draft text back before you say yes. A preview is not proof it went out.
What we know about the Muse app
Meta says the Muse app works with custom connectors for services it does not list. The Help Center article that explains how could not be read, so we do not know whether the app takes a remote MCP URL, OAuth or a header.
We have not confirmed that Muse can run Bolta from WhatsApp or the phone apps. Some third-party posts describe pasting a link into chat. That is not Meta's statement, so we do not repeat it here.
Meta's launch articles name the United States and Canada for the app, with a later one adding Australia. Check Meta's pages for where you can use it today.
Where Muse Code looks for skills
The connection gives Muse Code access to Bolta. A skill is optional guidance on using it well.
Run npx skills add boltaai/bolta-skills --skill bolta and then muse skills list. We have not run this against Muse Code, so if Bolta does not appear, skip the skill and use the connection alone.
- ~/.agents/skills and ~/.config/muse/skills for your own machine.
- ~/.claude/skills, which Muse Code also looks in by default, so a skill you installed for Claude Code can be seen.
- .agents/skills or .claude/skills inside a repo, for project-level skills.
Signing in on a machine without a browser
Meta's docs say you can sign in in the browser or headless but do not say how headless works. If no browser window opens, run muse mcp login bolta again, or try the Bearer key route, which is also unconfirmed.
Meta lists a headers field for streamable_http servers, and Bolta accepts a Bearer bolta_sk_ API key, so a header may work for a headless machine. We have not confirmed the exact format Muse Code expects, so check Meta's configuration page before you rely on it.
muse mcp login, logout and the mode field
Sign-in has two commands you will use, and a third setting Meta documents that we have left alone.
Meta also lists an OAuth dynamic client registration flag. Whether it works against Bolta's server has not been tested, so if login fails at that step, tell us.
| Item | What Meta documents | What we know with Bolta |
|---|---|---|
| muse mcp login bolta | Signs a server in with OAuth 2.1 | Opens bolta.ai, where you tick brands and approve. One connection covers one organization. |
| muse mcp logout bolta | Signs the server out | Use it before logging in again when Bolta says Invalid or expired. |
| mode | Each server can be required or optional | Not tested. We do not know how a required server behaves when Bolta is unreachable. |
| enabled | Each server has an on or off flag | Not tested. The guide leaves it out. |
When a terminal is the right place to queue posts
Muse Code suits people who already keep a repo open. The release notes, the docs and the commit history are one folder away, so a draft can start from the thing you just shipped instead of a blank box.
It suits less well when the person approving is not technical. Reviewing happens in Bolta, so a marketer or client can read and approve there without opening a shell.
- Good: developer-led posts, launch notes, changelog threads, docs highlights.
- Good: asking what is in review and having it read back.
- Less good: image-heavy campaigns, where the work happens in Bolta's library and calendar.
What to check on your own machine
Meta's pages describe the settings and sign-in. Nobody has run the whole loop with Bolta, so confirm each step yourself.
- /mcp lists bolta and its tools after muse starts.
- A read-only question about your brands answers with the brands you ticked and nothing else.
- A saved draft appears in Bolta's review queue with the text you saw in the terminal.
- A request to publish is refused or held until you give your yes.
What Muse cannot do without you
Muse connects as: mcp_servers entry in the Muse Code settings file (streamable HTTP).
Drafts are free, finals need your yes
Muse can write, edit and save drafts at any time. Approving, scheduling, publishing, sending a reply, activating a routine or campaign and deleting each wait for your yes, shown against the exact text.
One connection, one organization
When you connect Muse you tick the brands it may reach. It reaches only those, and when that is more than one brand, every call names the brand it is for.
Your role is the ceiling
Each call Muse makes is checked like a normal request from you. Owners and admins can act on any post, creators on Bolta's drafts and on posts they are a named reviewer on, and viewers never approve or publish.
Where Muse can publish through Bolta
11 social networks, plus WordPress for articles. Bolta holds the connected accounts. Each card opens the Muse guide for that network.
- Threadstext posts, image posts, polls
- LinkedIntext posts, articles, carousels
- X (Twitter)tweets, threads, polls
- Instagramposts, stories, reels
- Facebookposts, stories, reels
- Blueskyposts, threads, quote posts
- Mastodontoots, polls, threads
- Reddittext posts, link posts, image posts
- TikTokvideos, stories, photo posts
- YouTubevideos, Shorts, community postsTeam plan, beta
- Pinterestpins, idea pins, video pinsTeam plan, beta
The words behind Muse and Bolta
For Muse: mcp_servers entry in the Muse Code settings file (streamable HTTP), signing in with Sign in (OAuth) with muse mcp login.
- MCP
- The Model Context Protocol, an open standard that lets an AI app call tools in another product. Bolta's hosted server is at https://mcp.bolta.ai/mcp, and Muse reaches Bolta through a connection like it.
- Skill
- A folder of instructions an AI app reads so it knows how to use Bolta well. It does not connect by itself: install it with
npx skills add boltaai/bolta-skills --skill boltanext to the connection. - Plugin
- A bundle that brings the connection and the skill in one install, where the app supports plugins. Claude Code has one, added with its plugin marketplace commands.
- API key
- A
bolta_sk_key you create in Settings, sent as a Bearer header. It carries the permissions you choose, which suits apps you configure by hand or anything that runs unattended.
Setup for Muse is only partly confirmed. See what is and is not confirmed. Last checked 2026-11-21.
Muse is not Muse Code
Muse is Meta's personal agent app on iOS, Android, desktop and WhatsApp. Muse Code is a separate terminal agent with a settings file and its own sign-in. This page and the Bolta guide cover Muse Code. For the other terminal agents, see Claude Code or Codex.
Other AI agents that post through Bolta
Every agent below connects to the same Bolta workspace and follows the same approval rules.
- ChatGPTOpen Bolta in ChatGPT, sign in
- OpenAI dotsAlways-on ChatGPT agents
- ClaudeCustom connector, one sign-in
- Claude DuetCarries your Claude connectors over
- Claude CoworkPlugin and connector on your desktop
- Claude CodeTwo plugin commands
- Codexcodex mcp add, then sign in
- CursorOne mcp.json entry
- GeminiGemini CLI extension
- OpenClawSkills and MCP for your gateway
- Hermes AgentMCP server in the Hermes config
- Grok BotCustom connector in xAI's agent
- Grok Buildgrok mcp add
- DeepSeekThrough the Bolta MCP link
- Kimi K3Kimi Code with the Bolta MCP server
- ManusConnector with an API key
- CueA personal agent that posts for you
- PerplexityResearch there, draft in Bolta
- Perplexity ComputerRemote MCP connector
- nanoclawRun it from WhatsApp or Telegram
- PaperclipConnector for your agent company
- MCP ServerOne link for any MCP client
Related
What Muse can do through Bolta
The jobs Bolta's agents cover, each with its own page. Your AI app can ask for drafts, plans and reports in the same areas. Every post still waits for your yes.
Frequently asked questions
Short answers about using Muse with Bolta.
- Is Muse the same as Muse Code?
- No. Muse is Meta's personal agent app on phones, desktop and WhatsApp. Muse Code is a separate terminal agent with its own settings file. This page covers Muse Code, because that is where Meta documents remote MCP servers.
- Can I add Bolta in the Muse app or WhatsApp?
- We have not confirmed it. Meta says the app has custom connectors, but we could not read the steps and found nothing showing that it takes a Bolta MCP link. Try the Muse Code path first.
- Does Muse need an API key for Bolta?
- Not for the normal route. muse mcp login bolta signs you in through the browser and there is no key to copy. A Bearer bolta_sk_ key is an option for machines with no browser, but we have not confirmed the exact headers format in Muse Code.
- Can Muse publish without my approval?
- No. Bolta will not approve, schedule or publish a post until you say yes to that exact text. It refuses the request or keeps the post in review, and your role and Safe Mode still apply.
- Is it safe to connect a server to Muse Code?
- Meta's documentation says MCP tools in Muse Code are not sandboxed, so connect only servers you trust. Bolta limits the brands you tick, applies your role, and needs your yes before anything goes out.
- Which countries can use Muse?
- We do not know the full list. Meta's September article names the United States and Canada for the Muse app, and a later one adds Australia. Which accounts and countries can use Muse Code is set by Meta, so check dev.meta.ai.
- Does the Bolta skill work in Muse Code?
- It may. Meta documents ~/.agents/skills and ~/.claude/skills as skill folders for Muse Code. We have not checked where the skills command puts Bolta, so if muse skills list does not show Bolta, skip it. The connection works without a skill.
- What do I do if /mcp does not show bolta?
- Check that the entry is inside mcp_servers, that transport is streamable_http, that the url is exactly https://mcp.bolta.ai/mcp and that schema_version is 1. Then close Muse Code and start it again.
- How much does Muse cost?
- We could not confirm Muse or Muse Code pricing, so we will not quote one. Bolta's own plans are on the pricing page. Check Meta for what you need on its side.
- Has this been tested end to end?
- No. The settings format and sign-in command come from Meta's documentation, but nobody has run a full draft, review and schedule through Muse Code with Bolta. Claude Code and Codex have their own Bolta pages if you want another terminal agent.
- Can Muse Code keep posting after I close the terminal?
- Muse Code itself does not, as far as we can tell. A routine you set up through it is stored in Bolta and repeats there, and it saves switched off until you say yes to turning it on.
- Which brands can Muse Code reach?
- Only the ones you ticked on the Bolta permission screen during muse mcp login. If you need another brand, sign in again and tick it. Your role in each brand still decides what is allowed.
If something does not work
Quick fixes for the common snags.
- Muse Code stops at startup with malformed settings file
- The file must contain "schema_version": 1 and be valid JSON, with commas between entries and none at the end. Fix that and start muse again.
- bolta is missing from /mcp
- Check the entry sits inside mcp_servers, the transport is streamable_http and the url is https://mcp.bolta.ai/mcp. Close Muse Code and reopen it.
- muse mcp login bolta opens no browser
- Close any stuck window and run muse mcp login bolta again. Over SSH or on a server there is nothing to open, so sign in on a machine with a browser or see the headless section above.
- Bolta answers Invalid or expired
- The saved sign-in is out of date. Run muse mcp logout bolta, then muse mcp login bolta, and sign in once more.
- Bolta asks for a workspace_id or answers about the wrong brand
- You ticked more than one brand, so every request has to name one. Say which in plain words, for example for the Acme brand. If a brand is missing, sign in again and tick it.
- A request is refused or says approval is required
- Bolta will not schedule or publish until you say yes to that exact post. Ask Muse to save a draft, then approve it. A 403 can also mean your role in that brand does not allow the action.
Ready to schedule social media posts with Muse?
Connect Muse and ask for your first draft. Nothing goes out until you say yes.