Is it safe to publish from MagicPost?
MagicPost connects to LinkedIn through LinkedIn's official sign-in (OAuth) and publishes through LinkedIn's API. You sign in on LinkedIn's own window, so MagicPost never receives your LinkedIn password, and no browser extension is involved. Publishing from MagicPost is included in Growth, Creator, Agency, and Team, and in the free trial.
The connection flow for teams and agencies is presented on the safe LinkedIn connection page. This article describes what MagicPost does once LinkedIn is connected.
How MagicPost connects to your LinkedIn account
When you click Connect LinkedIn in MagicPost, a LinkedIn window opens. You sign in there and approve the access. LinkedIn then gives MagicPost a connection that MagicPost uses to publish and to read the statistics of your posts.
MagicPost does not see or store your LinkedIn password.
MagicPost does not use a browser extension to act on LinkedIn.
MagicPost sends posts and comments to LinkedIn through LinkedIn's API.
What MagicPost publishes, and when
MagicPost publishes on LinkedIn only what was scheduled or sent from the seat. In a MagicPost organization, the people who manage a seat can schedule posts on that seat too. Four kinds of content go out from a seat.
Posts and reposts that were scheduled or published from the seat.
Comments under your own posts, scheduled or sent from the seat.
Comments and reactions you send on other people's posts from Engagement, which is included in Growth, Creator, Agency, and Team.
Posts that an AI assistant schedules or publishes on the seat, once you have connected that assistant with an API key or MCP. API keys are included in Creator, Agency, and Team: see what you can do with MCP.
Three rules apply to the posts you publish from the MagicPost app.
Publishing a post now asks for a confirmation. When you click Publish now in the scheduling panel of a post, MagicPost asks "Do you want to publish this post?" before sending anything. Two immediate actions have no second confirmation: a repost sent with Publish now from the Repost this post window, and a comment sent with Publish under a published post.
A scheduled post goes out at the time you chose. You can change the time or unschedule the post until then.
A post can wait for approval. With Approve later on, MagicPost keeps a scheduled post on the calendar and does not publish it.
The safeguards built into MagicPost publishing
Identity check. On a personal profile, MagicPost refuses to publish when the LinkedIn account behind the connection is not the one shown in MagicPost. The post fails with a message asking you to reconnect the right account, instead of going out under someone else's name.
Media test before the scheduled time. MagicPost tests the media of a scheduled post with LinkedIn ahead of time, and flags the post in the Posts page when the test fails.
Typed confirmation to delete. Deleting a published post from LinkedIn requires typing a confirmation word, and MagicPost keeps a draft with the content of the post.
No silent failure. When a post cannot be published, MagicPost marks it with a red warning triangle and emails the account. See why a post did not publish.
The LinkedIn connection has an end date
LinkedIn limits how long a connection with an app like MagicPost stays valid. MagicPost emails a reminder before the connection expires. Renewing the connection does not disconnect anything, and your scheduled posts are kept. MagicPost also refuses to schedule a post after the end date of the connection, so a post is not silently scheduled into a period where it could not go out.
The renewal steps are in how to renew your LinkedIn connection.
How to disconnect LinkedIn from MagicPost
Open Settings in MagicPost.
Go to the LinkedIn tab.
Click Disconnect on the row that shows your connected LinkedIn account.
Once LinkedIn is disconnected, MagicPost can no longer publish from that seat. A post that reaches its scheduled time without a connection fails with the Reconnection required label.
Connecting someone else's LinkedIn account without their password
In a MagicPost organization, the person who manages a seat is not always the person who owns the LinkedIn account. MagicPost then offers a connection link to send to that person. They open the link, sign in to LinkedIn themselves and approve the access. Nobody shares a LinkedIn password.
What this article does not cover
This article makes no claim about the reach of posts published from MagicPost compared with posts published directly on LinkedIn. To follow the results of your own MagicPost posts, see how to analyze your LinkedIn metrics.
FAQ
Does MagicPost know my LinkedIn password?
No. You type your password on LinkedIn's own sign-in window, and LinkedIn gives MagicPost a connection that does not contain the password.
Do I need to install a browser extension to publish from MagicPost?
No. MagicPost publishes through LinkedIn's API from its servers. Nothing has to be installed in your browser, and scheduled posts go out while your computer is off.
Can MagicPost publish something I did not ask for?
No. MagicPost publishes only what was scheduled or sent from the seat: posts, reposts, comments, and the comments and reactions sent from Engagement. Two cases deserve a check. In an organization, the people who manage your seat can schedule posts on it. An AI assistant connected with an API key or MCP can also schedule and publish posts on the seat.
What happens if the wrong LinkedIn account is connected to my MagicPost profile?
On a personal profile, MagicPost refuses to publish. The post fails and MagicPost asks you to reconnect the LinkedIn account of that profile. For a seat managed by an organization, only an administrator of the organization can redo the connection.
Does disconnecting LinkedIn delete my posts in MagicPost?
No. Disconnecting LinkedIn removes the connection, and your drafts and scheduled posts stay in MagicPost. Scheduled posts cannot be published until LinkedIn is connected again.
Need help?
Reach out via the in-app chat, or book a 30-minute onboarding call: https://cal.com/magicpost/book-a-call