Skip to main content

Social Media Automation

Configure social provider apps and exact OAuth callback URLs

Save the correct application credentials securely and register the callback shown by the selected workspace before testing a social connection.

Reviewed 13 November 20262 minute read5 steps

Where to start
Social Media Automation → Configuration → provider application

Fields and options

Access needed
Administrator with Manage settings; authorised access to the provider developer app
Application / client ID
Required, up to 250 characters. TikTok calls this a client key.
Client secret
Up to 512 characters. A blank secret retains the stored secret only when the client ID is unchanged; a different app needs its matching secret.
Configured
Means credentials were stored. It does not prove OAuth consent, provider approval, a connected account or a successful post.

Before you begin

Use a developer app owned by your organisation or a dedicated sandbox owner. Keep passwords, client secrets and tokens out of chat, post content and support screenshots.

Follow these steps

  1. Open Configuration and find the provider application card. Copy its Authorised callback URL exactly.
  2. In the provider’s developer console, configure the required OAuth product, permissions and exact callback. Use the callback from this workspace, including its scheme, host and path.
  3. Complete the provider-specific ownership, test-user, privacy-policy and review requirements for the intended account and publication mode.
  4. Enter Application / client ID and Client secret in the matching card. Choose Save encrypted credentials.
  5. Return to Social accounts, start the official connection flow and verify the discovered destination before considering live publishing.

Check the result

Reload Configuration and verify the card is configured without exposing its stored secret. Complete a real callback and connection verification with an authorised test account.

If something does not look right

For redirect_uri mismatch, compare the exact displayed callback against the provider app; a Help Centre domain is not necessarily the workspace callback domain. If credentials are rejected after changing the ID, supply the new app’s matching secret through the protected settings form.

Fields, rules and limits

  • Seven provider cards use saved apps: Facebook, Instagram, Threads, LinkedIn, TikTok, Pinterest and YouTube.
  • Bluesky uses an app password in its connection flow. Mastodon registers an app for the selected public instance.
  • The module does not bypass provider app review, quota, business verification or account eligibility.

Questions and answers

Can I use the Help Centre URL as the callback?

Use only the callback displayed in the selected workspace’s Configuration card.

Does Configured mean the app has passed review?

No. Provider approval and a successful account connection are separate checks.

Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.