- AI providers supply the models behind captions, post versions, alt text, pictures and video clips.
- Social login lets people sign in or register with an existing Google, Facebook, X or LinkedIn account.
Neither of these connects a social network for publishing. Publishing channels use their own developer apps and credentials under Admin → Publishing → Platforms. See Publishing channels and Channel credentials. Setting up LinkedIn login does not connect a LinkedIn channel, and the reverse.
AI providers
MagicPost ships drivers for five providers. Providers that are not listed here cannot be used.
Writing means captions, versions of one post adapted for several networks, and alt text for pictures. Both pages are in the admin sidebar under Publishing: Writing Models and Media Models.
How AI keys work
- Each provider has one key. The same key appears on both pages, so changing it on Writing Models also changes it on Media Models.
- Keys are encrypted in the database. You do not put them in
.env. - A model is offered to users only when its provider key is stored and the model’s own switch is on. Each page tells you how many models are ready to use.
- Every model has a credit price: credits per run for writing, credits per picture for pictures, credits per second for clips. MagicPost holds the credits when a run starts and charges only for what comes back. See Credits and allowances.
- On installs that use plans, the AI writing and AI media plan features decide who can use them. See Subscription plans and Free tier.
- Pictures and clips are made by a background job, so cron or a queue worker must be running. See Cron and queue. A clip that is not ready after 40 minutes is stopped and nothing is charged.
- Providers bill you directly for every request. MagicPost credits are what your users spend, and they are separate from your provider balance.
Keys are encrypted with your site’s
APP_KEY. If you restore the database on an install with a different APP_KEY, the stored keys cannot be read and providers will reject them. Paste the keys again and click Save keys.Model identifiers
Providers rename and retire models. The Model identifier of each row must match the name in the provider’s API exactly. When a Test reports an unknown model, click Edit, correct the identifier and save. For every field you can edit on a model, see AI models. For how users run these models, see AI writing and media.Social login
Social login is configured on Admin → Backend Settings → Auth Settings. Each provider needs an app in its own developer console and four values in MagicPost.
The full callback address is your site address followed by the path, for example
https://your-domain.com/auth/google/callback. Each provider section on Auth Settings shows the exact value in a read-only Callback URL field. Copy it from there.
What each Auth Settings section asks for
The credentials are stored in the database. Nothing goes in
.env. When a provider is switched on, the key, secret and Redirect URL are all required.
How sign-in works
- The master switch Login via Social (oAuth) must be on. It saves as soon as you toggle it.
- A provider appears only when its Enable switch is on and both its key and secret are filled in.
- Buttons appear on the login page under or continue with and on the registration page under or sign up with.
- After the person approves, MagicPost looks for an account in this order:
- An account already linked to that provider identity signs in.
- An account with the same email address is linked to the provider and signs in.
- Otherwise a new account is created, but only if User Registration is on under Admin → Backend Settings → Registration Settings. New accounts get the standard user role and a verified email address.
- The provider must return an email address. If it does not, the sign-in is refused.
- Accounts that are banned or suspended are refused.
Messages people see
AI providers
Start with OpenAI, then add the providers you need.
Social login
Start with Google, then add the providers you need.