Connect Facebook, Instagram, WhatsApp, TikTok, YouTube, X and LinkedIn

Connect every social channel to Social Hub

Social Hub posts, schedules, answers messages and runs ads from one admin. Each channel uses your own developer app, so you own the keys, the data and the approvals. This guide walks through every channel step by step: what to create, which address to paste where, what each platform must approve, and how to fix the errors people meet most.

At a glance

Channel	What Social Hub does	Where you create the app	Approval before going public
Facebook	Page posts, photos, videos, Reels, stories, Messenger, comments, ads, catalog, Pixel and Conversions API	developers.facebook.com (one Meta app)	Business verification and Advanced Access for the permissions you use
Instagram	Posts, carousels, Reels, stories, product tags, DMs and comments	Same Meta app	Same as Facebook
WhatsApp	AI and team chats, order messages, cash-on-delivery confirmations, campaigns	Same Meta app + WhatsApp Business account	Approved message templates and a verified business
TikTok	Video and photo posts, the TikTok Pixel and Events API	developers.tiktok.com (Login Kit + Content Posting API)	TikTok app review. Until then posts go only to private accounts
YouTube	Video uploads with title, tags, thumbnail, playlist and captions	console.cloud.google.com (OAuth client)	Google verification and the YouTube API audit. Until then uploads are private
X	Text, photo and video posts	console.x.com	None, but the X API is pay-per-use: buy credits first
LinkedIn	Text, photo (up to 20) and video posts to your profile or company page	linkedin.com/developers	Page verification; company-page posting needs page-level access (see below)

Before you start

• Open Admin → Social Hub → Connections. The channels are grouped as Meta (Facebook, Instagram, WhatsApp share one app), Video (TikTok, YouTube) and Social & professional (X, LinkedIn). Pick a channel to open its setup.
• Each setup card shows the exact redirect or callback URL for your store with a copy button. Always copy it from the card; it contains your own domain.
• Your privacy policy and terms of service pages must be public. Every platform asks for both links.
• Keys are stored encrypted on your server and are never shown again. To keep a saved secret, leave the secret box empty when you save.
• Copy secrets with the platform's own Copy button. Store Console trims spaces and line breaks, and accepts every character a platform uses, including / + = ..

1. Meta: Facebook, Instagram and WhatsApp

1. At developers.facebook.com/apps press Create app, choose Business and link your business portfolio.
2. Add the use cases Manage everything on your Page, Engage with customers on Messenger, Manage messaging & content on Instagram, Create & manage ads with Marketing API, Manage products with Catalog API, and Connect with customers through WhatsApp if you use it.
3. In Social Hub open Facebook → Your Meta app. Copy each address into the Meta app: the Valid OAuth Redirect URI (Facebook Login for Business → Settings), the app domain, privacy, terms and data-deletion URLs (App settings → Basic) and the deauthorize callback.
4. Paste the App ID and App Secret and press Save and check. Store Console asks Meta whether they are valid before it saves them.
5. Press Continue with Facebook, signed in as an admin of your Page. Choose only your own Page, business and Instagram account.
6. Pick the Page; its Instagram account follows. Pick the ad account, Pixel and catalog if you run ads or a shop.
7. Press Subscribe the Page so messages, comments and leads arrive live. Health turns green after the first one.
8. For WhatsApp, create a permanent System User token with whatsapp_business_messaging and whatsapp_business_management, paste it under WhatsApp, press Save and find numbers and choose the number customers message.
9. Complete Business verification and switch the app to Live. Request Advanced Access for each permission you need (Messenger replies to every customer need pages_messaging).

If Meta shows Invalid Scopes, add the listed permissions under Use cases → Customize. If it shows URL blocked, the redirect URI is missing or mistyped.

2. TikTok

1. Create a TikTok for Developers account at developers.tiktok.com (email and code), then Manage apps → Connect an app. Choose the owner (individual or organization) and app type Other.
2. Fill the basics: a 1024 × 1024 icon, category, a short description, your terms and privacy URLs, platform Web and your website URL.
3. Verify your domain. Open URL properties → Verify properties → URL prefix, enter https://your-domain/, download the signature file and make it reachable at https://your-domain/tiktokXXXX.txt (it must answer with the file's text), then press Verify. TikTok rejects the terms, privacy and website links until this is done.
4. Open Sandbox → Create Sandbox (clone from the draft). Add the products Login Kit and Content Posting API, and turn on Direct Post.
5. Under Login Kit → Redirect URI → Web, paste the redirect URI from Social Hub's TikTok card.
6. Add the scopes user.info.basic, user.info.profile, user.info.stats, video.list, video.upload, video.publish, then press Apply changes.
7. Under Sandbox settings → Target users → Add account, sign in with the TikTok account you will post to.
8. Copy the sandbox Client key and Client secret into Social Hub → TikTok, press Save, then Continue with TikTok.
9. Go public: until TikTok reviews your app, TikTok only accepts posts to private accounts and marks them Only me. Record a short demo of the sandbox flow (sign in, compose, post), fill App review on the production app with what each scope does, upload the video and press Submit for review. After approval, save the production key and secret and connect again.

For the TikTok Pixel and server events, open TikTok Events Manager → your Pixel and paste the Pixel ID and an Events API access token in Commerce & Tracking → TikTok. TikTok ads use a separate TikTok API for Business developer account (business-api.tiktok.com).

3. YouTube

1. At console.cloud.google.com, use the Google account that owns the channel and create a project.
2. APIs & Services → Library → YouTube Data API v3 → Enable, and check that its overview page says Enabled.
3. Google Auth Platform → Get started: app name, support email, audience External. Under Branding add your home page, privacy and terms links. Under Data Access add youtube.upload and youtube.force-ssl.
4. Clients → Create client → Web application, with the redirect URI from Social Hub's YouTube card.
5. Audience → Publish app (in testing mode Google ends the sign-in after 7 days).
6. Paste the Client ID and Client secret into Social Hub → YouTube, press Save app keys, then Continue with Google and pick the channel. If Google warns that the app is unverified, choose Advanced → Go to your app.
7. Go public: until Google audits the project every upload is private. Add a YouTube section to your privacy policy (which data, why, how to remove access, the Limited Use statement), verify your domain in Search Console with the same Google account, submit Verification Center → Prepare for verification with a short demo video, and fill the YouTube API Services audit form.

4. X

1. At console.x.com sign in with the X account you post from and accept the Developer Agreement.
2. Open your app → User authentication settings → Set up: permissions Read and write, type Web App, Automated App or Bot, the callback URI from Social Hub's X card, your website, terms and privacy links. Save.
3. Under Keys & Tokens → OAuth 2.0 Keys there are three rows: Client ID, Client Secret and Access Token. Social Hub needs only the first two. The Access Token and Refresh Token rows are for scripts; you do not need them.
4. Press Regenerate on the Client Secret row and copy the secret at once (X shows it only once).
5. Paste the Client ID and Client Secret into Social Hub → X, press Save app keys, then Continue with X and authorize.
6. Buy credits: the X API is pay-per-use. Under Billing → Credits add credits, or every post fails with credits depleted.

5. LinkedIn

1. At linkedin.com/developers/apps → Create app: app name, your company LinkedIn Page, privacy policy URL and a square logo. Accept the API Terms of Use.
2. In Settings press Verify next to the Page and open the verification link as a Page admin. Products that need approval stay greyed out until the app is verified.
3. In Products add Share on LinkedIn and Sign In with LinkedIn using OpenID Connect. To post as the company page and run ads, also request the Advertising API (or the Community Management API on a separate app) and complete its access form.
4. In Auth → Authorized redirect URLs add the URL from Social Hub's LinkedIn card.
5. Copy the Client ID and the Primary Client Secret (use LinkedIn's Copy button) into Social Hub → LinkedIn.
6. Turn on Post as a company page when the app has page access; leave it off to post as your own profile. Press Save app keys, then Continue with LinkedIn and press Allow.
7. If you manage more than one page, pick it under Post as.

LinkedIn tokens last 60 days. Health shows Connect again when one ends; apps with page access also get a refresh token and renew on their own.

6. Check that it works

• The Health card on Connections lists every check, including one row per channel: connected as …, keys saved, press Continue, or the permissions a platform did not grant. Press the refresh icon to run the checks again.
• Create a test post in Content Studio for the channel. The post page shows the result per channel with a link to the live post, or the reason it failed.
• The admin chat assistant and MCP clients use the same connections: social.post.schedule refuses a channel that is not connected.

Troubleshooting

Message	Cause	Fix
The client secret field format is invalid	The pasted value was not the secret (for example the Client ID, or an old copy).	Copy the secret again with the platform's Copy button and save.
The X connection expired or lost a permission right after connecting	X did not accept the Client Secret (X says Missing valid authorization header).	Regenerate the Client Secret, save it, and connect again.
X refused the request: credits depleted	No X API credits.	Buy credits under Billing → Credits in console.x.com.
Until TikTok audits your app, posts can only be private	The app has not passed TikTok review and the TikTok account is public.	Submit the app for review; until then test with a private account.
The video file could not be read	The media URL does not answer 200, often a stale CDN 404 after a re-upload.	Open the URL in a browser; add ?v=2 or re-upload under a new name.
YouTube upload stays private	The Google project is not audited.	Complete Google verification and the YouTube API audit.
YouTube Data API v3 has not been used in project …	The API is not enabled on that project.	Enable it on the API overview page and try again.
Meta Invalid Scopes or URL blocked	A permission or the redirect URI is missing in the Meta app.	Add the permission under Use cases, paste the redirect URI under Facebook Login for Business.