Planly
MARKETING · MARKETING
Social channels, scheduled posts, media library, and AI credits in the account they connected.
Connect Planly with Fabriq Developer
Your user pastes their Planly credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Planly in practice
Planly puts nine social networks behind one scheduling API, and each one adds its own required fields, so there is no single publish payload: TikTok demands a privacyLevel of PUBLIC_TO_EVERYONE, MUTUAL_FOLLOW_FRIENDS, FOLLOWER_OF_CREATOR or SELF_ONLY, Pinterest a boardId unless the post is a draft, Mastodon at most 4 poll options of 25 characters, and Instagram at most three collaborator usernames. Authentication is one bearer key from Settings › Security sent against app.planly.com/api/v2.
Scopes that draw scrutiny
Authorization: Bearer api_keyPlanly documents a single account-level key with no scope mechanism, so the credential that lists channels can also publish to every one of them.
Worth knowing
- File-size and monthly scheduling limits are described as varying by team permissions, so the same call succeeds for one team member and fails for another with no change to the request.
- Required fields differ per network, so a payload that posts successfully to LinkedIn is rejected by TikTok or Pinterest rather than degraded.
- YouTube privacy status is an enum of public, unlisted and private, and Pinterest only skips boardId for drafts, so "schedule everywhere" needs per-channel branches.
Checked against Planly documentation (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Planly behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.