Connecting Social Media Accounts

After a Google Business Profile post publishes, the platform can automatically syndicate the same content to the client's social channels. This is per profile — each profile keeps its own connected social accounts.

Feature flag: social syndication is gated by your plan and the socialAccounts feature flag. If you don't see Social Accounts in the sidebar, your org has it disabled — contact support to enable.

What's supported

Channel	What it posts to	Notes
Facebook	A Facebook Page you administer	You pick the Page during the connect flow.
Instagram	Business / Creator accounts	Must be linked to a Facebook Page — Instagram's requirement, not ours.
LinkedIn	The personal profile that authorizes	Company / organization pages need LinkedIn's Community Management API, which isn't approved yet.
X (Twitter)	The one X account that authorizes	X offers no account picker — see Connecting X (Twitter).
YouTube	Video uploads on the channel that authorizes	A post with no video is skipped — YouTube Community posts aren't supported.

TikTok is on the roadmap.

Connecting a social account

1. Open the profile → Social Accounts tab. (Or go to Social Accounts in the sidebar and pick a profile.)
2. Click Connect on the channel you want.
3. Sign in to the account that administers the page — for Facebook that's your personal admin account, not the Page itself.
4. Approve the requested permissions (page management, content publish).
5. Pick which Page(s) to connect to this profile. Instagram accounts attached to those pages are connected automatically.
6. Save.

X (Twitter) does not offer step 5 — it has no account picker at all. Use Connecting X (Twitter) instead.

The accounts now appear under the profile with a green "Connected" status.

If the same account is already connected to another profile, that row shows an "Also connected to …" warning. That's usually a sign the wrong account authorized — see Connecting X (Twitter). Google Business Profile and LinkedIn are excluded from this warning, because sharing one account across profiles is normal for both.

What the client sees

When you use Invite Client to Connect, the email and the page it opens both tell the client what to expect, in the same words:

• Each Connect button opens that network's own site — facebook.com for Facebook and Instagram (Instagram authorizes through its linked Facebook Page), linkedin.com for LinkedIn, twitter.com for X, and accounts.google.com for YouTube.
• The page they land on has no password field. They are granting permission to publish, not handing over a password.
• If they are asked to sign in anywhere other than those sites, they are told to stop and check with you.

Both surfaces tell the client to go by the web address, not by the name on the screen. Any app name shown while they authorize comes from our registration in that network's own console — nothing you configure in the platform controls it, so it may not match your agency's name or the platform's.

The invite email is sent under your agency's name, and the connect page names your agency too. Both come from your organization's name, or its white-label brand name when one is set.

Connecting X (Twitter)

X behaves differently from every other channel and it is the most common source of wrong-account connections:

• X never asks which account to connect. It authorizes whichever X account is signed in to the browser you use, and it doesn't tell you which one that was.
• Switching accounts in X is not enough. With more than one X session open, X uses its own idea of the primary one.
• Accounts you manage as a delegate can't be selected. X's delegate / team access is a feature of x.com itself; X does not expose delegated accounts to other apps, so they can never appear as a choice here.

The reliable way to connect a client's X account:

1. Open the profile → Social Accounts tab → Connect X (Twitter).
2. Click Generate private link, then Copy link.
3. Open that link in a private / incognito window — a fresh window has no X session, so nothing can hijack the authorization.
4. Sign in as the account this profile should post from, then authorize. The link expires in 2 hours.

You can also send that link to the client, or use Invite Client to Connect, so they authorize their own account without sharing a password.

Always check the result. After connecting, the row under Connected Accounts shows the handle that was actually authorized (for example @clienthandle (Client Name)). If it isn't the account you wanted, Remove the row and redo the steps above — a wrong connection publishes the client's posts to the wrong audience.

Connecting X once per profile is required — each profile posts from its own X account.

How syndication works

When a content calendar entry has platforms: ['gbp', 'facebook', 'instagram']:

1. Platform publishes to Google Business Profile first (the primary channel).
2. If GBP publish succeeds, the same content (text + image, adapted for each platform's quirks) goes to Facebook and Instagram.
3. Syndication failures don't fail the GBP post. If Facebook is down, your GBP post still goes live, and the Facebook attempt is logged to Admin → Failed Jobs so you can retry.

Per-post platform selection

In the content calendar, each entry has a Platforms field where you choose which channels to publish to. You can:

• Send to GBP only (the default for many agencies).
• Send to GBP + Facebook + Instagram.
• Skip GBP entirely and use this as a Facebook-only post.

The set of available platforms is limited to what's been connected for that profile.

Platform-specific adaptations

The platform makes small adjustments per channel:

• Image aspect ratio: cropped automatically (Facebook is flexible; Instagram prefers square or 4:5).
• Text length: truncated with a "…" if necessary.
• Links: GBP allows a CTA button; Facebook treats the URL as a link; Instagram doesn't allow clickable links in captions (so URLs are removed or moved to the bio).

You see a preview per channel before scheduling.

Disconnecting

Social Accounts → row → Disconnect. The token is revoked with Facebook and any scheduled posts using that account will fall back to GBP-only at publish time (with a warning sent to the team).

Common issues

Problem	Cause / Fix
"Instagram not appearing"	Instagram must be a Business or Creator account, linked to a Facebook Page. Switch in the Instagram app under Settings → Account.
"Page already managed by another connection"	Disconnect from the other connection first, then reconnect here.
"Permission denied" on publish	The token expired. Reconnect from the Social Accounts tab.
The wrong X account got connected	X has no account picker. Remove the row, then reconnect with Generate private link in a private window. See Connecting X (Twitter).
"Also connected to …" on a row	The same account is connected to another profile too. Check which profile should have it, and reconnect the other one with the right account.
X accounts you manage as a delegate aren't listed	X doesn't expose delegated accounts to other apps. You have to authorize as the account itself.
A client says the invite asked them to log in to a domain they don't recognise	Ask for the exact address that was in the address bar. The sign-in after Connect is the network's own — facebook.com (Facebook and Instagram), linkedin.com, twitter.com, accounts.google.com — while the invite link and the page it opens are both on the platform's own domain.
The client got part-way and then saw an error, or a sign-in page	Send a fresh invite. A connection attempt has to be finished within about 10 minutes of leaving the invite page; after that the attempt can no longer be matched and has to start again.
Post visible on GBP but not on Facebook	Check Admin → Failed Jobs. The Facebook attempt was probably a soft failure — retry from there.

---

Next: Choosing & Changing Your Plan