Clone Social: complete knowledge base (for your clones)
Everything about Clone Social: what it does, the app page by page, platforms and limits, connecting accounts, comment replies, roles, the skill's actions and parameters, schedule recipes, troubleshooting and FAQ. Add it to the knowledge base of every clone that uses Clone Social or helps your team.
Version 2 · updated Nov 16, 2026
# Clone Social: complete knowledge base
*For clones. Load this document into the knowledge base of every clone that uses the Clone Social skill, and every clone that helps people with Clone (support, sales, onboarding). It covers everything Clone Social does, how it works, how to set it up, how to use the skill, and how to troubleshoot it. Last updated November 16, 2026.*
---
## 1. Clone Social in one minute
Clone Social lets clones run a company's or person's social media. It is two things:
1. **The Clone Social skill** in Clone Studio. A clone with this skill can write, schedule, approve, revise and publish social posts, and answer comments, when someone asks in chat or when a Schedule Task runs.
2. **The Clone Social app at https://social.clone.org**, where people review and approve posts, see the calendar, read the comments inbox, connect accounts, set rules, and see a log of everything every clone did.
What makes it different:
- **The clone is the author.** It researches its own knowledge base (and the web when useful) and writes in its own voice. It does not write generic AI filler.
- **It makes the visuals.** If no images are supplied, it designs single images and full carousels, sized for each platform. If the clone has a headshot, slides can show the clone itself.
- **Nothing goes out without the rules you set.** Every account starts with "every post needs approval".
- **Approve one platform at a time.** Good versions publish right away; the rest stay in review. "Revise with AI" changes only the platform and the slide you point at.
- **The clone that wrote a post answers its comments**, drafted for approval by default.
- **Customers connect their own apps and keys** (the way n8n and Make work). Clone never puts customers on a shared Clone app.
- **Everything is logged.**
Useful links:
| What | Link |
|---|---|
| The app | https://social.clone.org |
| Complete guide (support article) | https://support.clone.org/articles/clone-social |
| Setup guide: Facebook | https://support.clone.org/articles/clone-social-connect-facebook |
| Setup guide: Instagram | https://support.clone.org/articles/clone-social-connect-instagram |
| Setup guide: X | https://support.clone.org/articles/clone-social-connect-x |
| Setup guide: TikTok (through Blotato) | https://support.clone.org/articles/clone-social-connect-tiktok |
| Setup guide: Threads | https://support.clone.org/articles/clone-social-connect-threads |
| Daily social post routine | https://support.clone.org/libraries/skill-instructions/daily-social-post |
| Weekly social plan routine | https://support.clone.org/libraries/skill-instructions/weekly-social-plan |
| Product pages | https://clone.me/social (also /social/comments and /social/security-and-your-apps) |
---
## 2. Words to know
| Term | Meaning |
|---|---|
| **Workspace** | A Clone organization's space in Clone Social. Everyone in the same Clone organization shares one workspace. |
| **Account** | One social profile or page Clone Social may use, for example the "CloneMe" Facebook Page or the "@_clone.org_" Instagram account. |
| **Connection** | The link to a platform through the customer's own app or key (for example one Meta app connection can provide several Facebook Pages and Instagram accounts). |
| **Post** | One piece of content going to one or more accounts. |
| **Version** (variant) | The platform-specific copy of a post for one account: its own text, images, slides and limits. A post to five accounts has five versions. |
| **Approvals** | The queue of posts waiting for review. |
| **Revise with AI** | Asking the AI to change a draft. Only the named platforms and slides change. |
| **Held** | A version that couldn't publish because the account needs attention (for example a disconnected account). Held is not failed: it publishes after the problem is fixed. |
| **Inbox** | Comments on your posts, the replies clones drafted, and anything flagged for a person. |
| **Reply mode** | Per account: Draft & suggest (default), Always automatic, or Off. |
| **Activity log** | The record of every action by every clone and person. |
| **Blotato** | A posting service some customers already use. Clone Social can post through the customer's own Blotato account. |
---
## 3. Why it's valuable
Social media rewards consistency, and consistency is what busy teams can't sustain. Most businesses post in bursts, go quiet for weeks and leave comments unanswered. Clone Social takes over the parts that take the time:
| The usual work | With Clone Social |
|---|---|
| Deciding what to say | The clone already knows the products, customers, pricing and stories, and proposes and writes the post. |
| Rewriting one idea for five platforms | One request becomes a native version per platform: a carousel for Instagram, slides for TikTok, a professional post for LinkedIn, 280 characters for X. |
| Making graphics | Images and carousels are designed for you, on brand, with the clone in them when it helps. |
| Copy-pasting into five apps at the right time | Approved posts publish themselves on schedule. |
| Comments sitting for days | The clone that wrote the post drafts a reply within minutes, in context. |
| Checking facts and claims | A compliance pass flags unsupported numbers, missing credits and risky claims before anyone reviews. |
| "Who posted that?" | Every action is logged with who did it and who approved it. |
**Real example (Clone's own accounts, November 16, 2026):** one chat request, "Write today's Daily Use Case Spotlight for all our accounts, and send it for review", produced five versions in about 8 minutes: a Facebook image post, a 6-slide Instagram carousel, a LinkedIn image post, an X post and a 6-slide TikTok carousel featuring the clone. The team approved them one at a time and fixed one TikTok slide with "Revise with AI" without touching anything else. All five went live.
---
## 4. How a post gets made
When someone asks for a post without giving the finished words, Clone Social runs a writing pipeline on the requesting clone's behalf:
1. **Understand the request.** Topic, angle, audience, call to action, which accounts, any exact wording, links, special day.
2. **Research.** Search the clone's own knowledge base for facts, stories, offers and the right links; search the web when timely context helps (a recent survey, a seasonal moment).
3. **Write.** A platform-native version for every account the clone may draft for, within each platform's limits.
4. **Compliance check.** Flags unsupported statistics, claims that need a source, missing credits and anything risky. Notes appear on the draft for the reviewer.
5. **Design images.** Single images or carousels (up to 20 slides on Instagram), correctly sized. Slides can feature the clone if it has a headshot in Clone Studio.
6. **Send for review.** Drafts land in Approvals and the clone tells the person in chat, with a link.
**Timing.** The clone replies right away with an estimate. Text-only posts take about 1 to 2 minutes; posts with designed images or carousels usually take 5 to 10 minutes. The clone messages again when the drafts are ready.
**Media.**
- If the person supplies images or videos (public https links), Clone Social uses them. Media can be sent to a specific platform with a prefix, for example `instagram: https://...`.
- If no media is supplied, Clone Social designs it where the platform benefits from it.
- All media is copied into Clone Social's own storage before publishing, so every platform can fetch it reliably.
**Exact copy.** If the person gives the exact words ("post this exactly: ..."), Clone Social posts that text as written, with no rewriting. Finished text can also be different per platform.
**Which accounts.** By default, every account the clone is allowed to draft for (set on the Team page). The person can name platforms: "just Facebook and LinkedIn".
---
## 5. Reviewing and approving
### In the app (social.clone.org)
Each post opens with one card per platform version, two per row on a computer and one per row on a phone.
- **Status bar** at the top: "3 of 5 decided" plus one pill per platform (green = live, amber = needs review, blue = approved/publishing, red = failed). Tap a pill to jump to that card. **Request changes** and **Approve all** / **Approve remaining** sit in the same bar.
- **Each card** shows the account, platform, status, the media (carousels as numbered slides; click any image to open it full size, use arrow keys to move between slides), the text (editable inline, with a character counter for the platform's limit), compliance notes and any errors.
- **Card buttons:** **Approve & publish** (publishes that platform now, or at the scheduled time) and **Revise with AI**. Live cards show **View on [platform] ↗**.
- **Editing:** change any text inline. An edited card says "Edited, not saved". Approving saves the edit first. Editing a version clears its approval (it goes back to review).
- **Request changes** sends the post back to the clone with the note.
- **Notes & decisions:** notes the clone sees when it revises.
- **History:** every version is saved with who changed what.
- **Archive post** removes a post that won't be used.
### Approving one platform at a time
Approve each version on its own. Approved versions publish right away (or at the scheduled time) even while other versions stay in review. The post stays "in review" until every version is decided. "Approve all" approves everything still waiting. A version with a blocking check (for example "X allows 280 characters") must be fixed before it can be approved.
### Revise with AI
Say what to change. Only that changes.
- **Pick platforms:** on a card, **Revise with AI** selects just that platform. In the Revise box you can pick several. None picked means every platform still in review.
- **Slides by number:** "redo slide 3 so it shows the clone at a desk" regenerates only slide 3. Every other slide keeps its exact image.
- **Text only:** if the feedback isn't about images, images stay as they are.
- The revised versions go back to review, and the clone tells the person in chat when the revision is ready (usually a minute or two, longer with new images).
### From chat
- "Approve the latest post." (approves everything waiting)
- "Approve only Facebook and LinkedIn." (approves just those; the rest stay in review)
- "Revise the TikTok version: redo slide 4 with the clone at a desk."
- "Reject it." / "Send it back: make it shorter."
- "Discard the latest draft." (nothing is posted)
Only people with the **approver** role or higher can approve, from chat or the app. A Schedule Task (no person in the chat) cannot approve.
---
## 6. Publishing
- Approved versions publish at the scheduled time, or within about a minute if no time was set.
- Times are in the workspace's time zone.
- When versions go live, the clone posts the live links back into the chat ("Facebook: https://..."), plus anything still waiting for review. It tells you once per finished batch.
- **Held, not lost:** if an account is disconnected or its sign-in expired, its versions are held. The person is told, and the posts go out after reconnecting.
- **Failed:** if a platform rejects a post (for example a rule the platform enforces at publish time), the version is marked failed with the platform's reason, and the person is told.
- **Sign-ins renew automatically** where the platform allows it (X every 2 hours, Google every hour, Threads before 60 days, Bluesky sessions). LinkedIn sign-ins last 60 days; Clone Social reminds the workspace a week before.
---
## 7. Comment replies
### How it works
1. Clone Social checks connected accounts for new comments **every 15 minutes**. Facebook and Instagram can also notify in real time if the Meta connection includes the app ID, app secret and the `pages_manage_metadata` permission.
2. Obvious **spam and abuse is hidden automatically** (never deleted; it can be unhidden). Hidden spam does not wake a clone and costs nothing.
3. For a real comment, **the clone that made the post is woken** (through a Studio Event) with the comment, its own post and the team's notes. It writes the reply from its own knowledge.
4. What happens next depends on the account's **reply mode**.
### Reply modes (per account)
| Mode | What happens |
|---|---|
| **Draft & suggest** (default) | The clone drafts every reply; a person approves it in the Inbox. |
| **Always automatic** | Replies go out on their own after a short, natural delay (3 to 12 minutes by default, not instantly). Anything the clone flags as sensitive still waits for a person. |
| **Off** | Comments show in the Inbox and people answer them; no clone is woken. |
### Reply settings (per account, Accounts page)
| Setting | Default |
|---|---|
| Reply mode | Draft & suggest |
| Hide obvious spam and abuse | On (hidden, never deleted) |
| Sensitive replies wait for a person, even in automatic mode | On |
| Reply delay window (automatic) | 3 to 12 minutes |
| Quiet hours | Off (for example 22:00 to 07:00 in the workspace time zone) |
| Maximum replies per hour | 20 |
| One reply per thread | On |
| Signature | None (for example "Quinn, our AI teammate") |
| Clone for comments on posts no clone wrote | None (people's own posts and older posts) |
### Turning on comment replies for a clone (one time per clone)
Comment replies wake the clone through Clone Studio Events. On the **Team** page in Clone Social, under *Comment replies*, the steps are:
1. In Clone Studio → **Events → Sources**, add a **Custom HTTP push** source named "Clone Social – [clone name]". Copy its URL and secret into Clone Social.
2. On the clone → **Events → Link event source**: filter **off**, **immediate**, batch size **1**, thread **Fresh**. Paste the processing prompt shown on the Team page (it has a Copy button).
3. Press **Send a test** in Clone Social to confirm the clone receives events.
### Comment support by platform
| Platform | Read comments | Reply | Other actions |
|---|---|---|---|
| Facebook | Yes (real time available) | Yes | Hide, delete, like |
| Instagram | Yes (real time available) | Yes | Hide, delete |
| Threads | Yes | Yes | Hide replies |
| X | Mentions and quotes | Only to people who @mentioned or quoted the account (an X rule since February 2026) | Delete own replies |
| LinkedIn | Company pages, once LinkedIn approves the customer's app for its Community Management API | Yes (same) | Delete |
| YouTube | Yes | Yes (to the top-level comment) | Hold for review, remove |
| Bluesky | Yes | Yes | None |
| Through Blotato | Instagram and Facebook only | Yes | None |
### Inbox
The Inbox lists new comments, replies waiting for approval, scheduled automatic replies, and anything a clone escalated. People approve, edit, skip or answer themselves. Approved answers saved in Settings can be reused.
### Cost
Each comment reply is a run of the clone and uses Clone credits like any other task. Hidden spam doesn't wake a clone, so it costs nothing.
---
## 8. Activity log and undo
The **Activity log** records every action by every clone and every person: drafts, edits, approvals, publishes, failures, replies, hides, connection changes and settings changes, with who did it, who approved it, and when. Undo is one click where it makes sense: hold an automatic reply before it goes, delete a reply that was posted, or unhide a comment.
---
## 9. The app, page by page
Signing in: say **"Open Clone Social"** to any clone with the skill. It sends a one-time link that works once and expires in 10 minutes. Sessions last 7 days. People who aren't signed in see a public landing page at social.clone.org.
The header (same design as support.clone.org) has: Overview, Approvals (with a count), Calendar, Inbox (with a count), Activity log, Accounts, plus **Help** (the guide), the account menu (Team, Settings, Connected accounts, Guide & setup help, Sign out) and a **New post** button. On a phone, the menu button shows all pages.
| Page | What it's for |
|---|---|
| **Overview** | What's waiting, what's scheduled, what went out, connected accounts and recent activity. |
| **Approvals** | Every post waiting for review, plus posts clones are still writing (with their progress). |
| **Post page** | The review screen described in section 5. |
| **New post** | Write or paste a post yourself, pick accounts, add media, schedule it. |
| **Calendar** | Everything scheduled and published, by day. |
| **Inbox** | Comments, drafted replies, escalations. |
| **Activity log** | Every action by every clone and person. |
| **Accounts** | Connect platforms, choose which accounts Clone Social may use, set each account's post-approval and reply rules, refresh or disconnect. |
| **Team** | People and roles, which accounts each clone may draft for and publish to, and the comment-replies setup per clone. |
| **Settings** | Optional guidance for clones, approved answers, and the voice helper. |
---
## 10. People, roles and clone permissions
**People.** Anyone in the Clone organization can sign in through their own clone. The first person becomes the **owner**.
| Role | Can do |
|---|---|
| **Viewer** | See everything. |
| **Editor** | Create and edit posts, request revisions. |
| **Approver** | Everything an editor can, plus approve or reject posts and replies. |
| **Admin** | Everything an approver can, plus connect accounts, change account rules, set clone permissions, set up comment replies, and change settings and the voice helper. |
| **Owner** | Everything, including changing people's roles. |
**Clones.** On the Team page, an admin sets for each clone and each account whether it may **draft** posts, **publish** without approval (only on accounts whose posting rule is "Clones with publish rights skip approval"), and **reply** to comments. By default every post needs approval.
**Post approval rule (per account):** "Every post needs approval" (default) or "Clones with publish rights skip approval".
---
## 11. Settings (all optional)
Clones already know the business from their knowledge bases. Settings add optional guidance that goes along with every request:
| Setting | Use it for |
|---|---|
| Brand name | How to refer to the business. |
| Voice notes | "Warm, a little playful, never salesy. First names. No exclamation marks." |
| Extra facts | Hours, policies, offers the clones should always know. |
| Link template | Tracking parameters added to links (for example UTM tags). |
| Image style | A house style for designed images. |
| Approved answers | Exact answers the team wants used for common questions in replies. |
| **Voice helper** | An admin pastes any clone's Clone Studio embed code (Clone Studio → the clone → Integrations → Embed). That clone appears as a voice bubble in the bottom-right corner of every page for everyone in the workspace. Voice must be on for that clone. |
---
## 12. Platforms
### What's connected today
| Platform | How it connects | Post types | Key limits |
|---|---|---|---|
| **Facebook Pages** | Customer's own Meta app | Text, links, photos (up to 10), video, Reels | Text or media required |
| **Instagram** (professional accounts linked to a Facebook Page) | Same Meta app | Photo, carousel (up to 20 items), Reels (video up to 15 minutes), Stories | Media required; caption 2,200 characters; at most 30 hashtags; links in captions are not clickable |
| **Threads** | Customer's own Meta app with the Threads use case | Text, links, images, carousels (up to 20), video | 500 characters; at most 5 links |
| **X** | Customer's own X developer app | Text, links, images (up to 4) or one video, threads | 280 characters per post; every link counts as 23 |
| **LinkedIn** | Customer's own LinkedIn app | Text, links, images (up to 20) on the person's profile; company pages after LinkedIn approves the app | 3,000 characters; video not yet |
| **YouTube** | Customer's own Google Cloud app | Videos and Shorts (vertical, up to 3 minutes) | Exactly one video; title up to 100 characters (no < or >); description up to 5,000 bytes |
| **Bluesky** | An app password (no developer app) | Text, links, up to 4 images, threads | 300 characters; images up to 1 MB; video not yet |
| **Blotato** | Customer's own Blotato API key | Every account linked in their Blotato: X, TikTok, LinkedIn (including company pages), YouTube, Threads, Bluesky, Pinterest, Facebook, Instagram | Same platform limits; TikTok up to 35 images and needs media; Pinterest one image and needs media |
**TikTok today goes through Blotato.** A direct TikTok connection is coming; TikTok audits every app before it can post publicly. Through Blotato, TikTok posts default to public and are labeled as AI-generated content.
**Coming soon:** Mastodon, Telegram, Discord and Tumblr (customer's own app), and the posting services Ayrshare, Zernio, Upload-Post and Publer. Google Business Profile, Pinterest (direct), Reddit and Snapchat require the platform to approve the customer's app first.
### Platform-specific rules the clone writes for
- **Instagram:** links in captions aren't clickable, so the clone writes a plain destination such as "example.com/menu" (or puts the link in the first comment where that helps). At most 5 hashtags is the house style; Instagram's hard limit is 30.
- **X:** under 280 characters per post, links count as 23 each. Threads are supported.
- **LinkedIn:** under 3,000 characters, professional tone.
- **Threads:** under 500 characters, conversational, one idea.
- **Bluesky:** under 300 characters.
- **YouTube:** needs a title and a video.
---
## 13. Connecting accounts: your apps, your keys
Clone Social works like n8n and Make: **the customer brings their own app**. They create a developer app in their own Meta, X, LinkedIn or Google account (or use their own Blotato account) and give Clone Social its keys. Why:
- **Security:** the app lives in the customer's account. They decide its permissions and can revoke it any time from the platform.
- **Control:** when connecting, they pick exactly which pages and profiles Clone Social may use. Nothing else is touched.
- **No middleman:** posting isn't routed through a shared app that a platform could throttle or suspend for everyone.
- **Their limits, their costs:** platform API costs (X charges per post) and limits stay on their own account.
- **Encrypted:** keys and tokens are encrypted at rest, never shown again after saving, and never handed to clones. Clones only ask Clone Social to act; they never see credentials.
Only **owners and admins** can connect accounts (Accounts page). After connecting, a picker lists the pages and profiles found; tick the ones Clone Social may use and press Done.
### Summary of each connection (full steps in the support guides)
| Platform | What the customer creates | Notes |
|---|---|---|
| Facebook + Instagram | A Meta app (business portfolio), with the Pages and Instagram permissions; a **system user** with a token set to **never expire**, with the Pages and Instagram accounts assigned to it first. Paste the token, plus the App ID and App secret for real-time comments. | Switch the app to **Live** (needs a privacy policy link); in Development mode posts are only visible to people with a role on the app. Alternative: "Sign in through your app" with Facebook Login for Business and the redirect address shown. Instagram must be a professional account linked to a Facebook Page. |
| X | An X developer app, OAuth 2.0, Web App (confidential client), Read and write, with the callback URL shown in Clone Social. Paste the OAuth 2.0 Client ID and Secret, then sign in. | X bills usage to the customer's developer account (roughly $0.015 per post, more with a link; check the X console). |
| Threads | The Meta app with the "Access the Threads API" use case and its four permissions, the redirect address shown, and the **Threads** app ID and secret (different from Facebook's). | Until Meta approves the app, it can only post for **Threads testers**: add your own Threads profile as a tester and accept the invite in Threads (Settings → Account → Website permissions). |
| LinkedIn | A LinkedIn app linked to a company page, with "Sign In with LinkedIn using OpenID Connect" and "Share on LinkedIn". | Company pages and their comments need LinkedIn to approve the app for the Community Management API (LinkedIn requires a separate app with no other products). Sign-ins last 60 days. |
| YouTube | A Google Cloud project with the YouTube Data API v3, an OAuth consent screen (External, **published** so sign-ins don't end after 7 days), and a Web OAuth client with the redirect address shown. | Uploads have their own daily quota per Google project. |
| Bluesky | An app password (Bluesky → Settings → Privacy and security → App passwords). | No developer app needed. |
| Blotato (and TikTok) | The Blotato API key (Blotato → Settings → API; API access needs a paid Blotato plan). Link TikTok and other accounts inside Blotato first. | Don't disconnect accounts inside Blotato or Clone Social loses them too. |
The redirect/callback address for every "sign in through your app" connection is **https://social.clone.org/connect/oauth/callback**.
If someone needs help, point them to the setup guide for their platform and walk them through it step by step.
---
## 14. Getting started checklist
1. **Add the skill:** in Clone Studio, add the **Clone Social** skill to the clones that should manage social media.
2. **Open Clone Social:** say "Open Clone Social" and tap the one-time link. The first person becomes the owner.
3. **Connect accounts:** on the Accounts page, pick a platform and follow its guide; tick the pages and profiles to use.
4. **Set each account's rules:** post approval and reply mode (Draft & suggest is the default).
5. **Give clones access:** on the Team page, choose which accounts each clone may draft for (and publish to, if wanted).
6. **Turn on comment replies:** one time per clone, on the Team page (see section 7).
7. **Invite the team:** colleagues sign in through their own clones; give them roles.
8. **Ask for the first post:** "Write a post introducing our team for all our accounts and send it for review."
9. **Optional:** add a Schedule Task so it runs every day or week (section 16), add a voice helper in Settings.
---
## 15. The Clone Social skill: reference for clones
**Golden rules**
- Call the skill **once per request**. Never retry the same call.
- **Relay Clone Social's reply to the person exactly as written.** Put every link on its own line (some chat channels, like SMS, break formatted links).
- When the reply says "Relay this to the user as written", do exactly that, without adding anything.
- Actions that need a person in the chat (like **open**) don't work from a Schedule Task.
**Actions**
| Action | What it does | Main parameters |
|---|---|---|
| `open` | Sends a one-time sign-in link (10 minutes, single use). Goes to Accounts if nothing is connected yet. | `page`: queue, inbox, calendar, accounts, team, settings |
| `create_post` | Writes and sends drafts for review from a request, or saves finished text. Replies immediately with a time estimate when writing. | `request` (the person's words) OR `text` (finished copy); `platforms`; `media_urls`; `scheduled_at`; `approval`; `per_platform`; `first_comment`; `title` |
| `queue` | Lists what's waiting for review and what's scheduled. | None |
| `approve` | Approves the post (all waiting versions), or only named platforms. Needs a person with the approver role. | `post` (id or "latest"); `platforms`; `note` |
| `reject` | Rejects the post. | `post`; `note` |
| `request_changes` | Sends the post back with a note. | `post`; `note` |
| `revise` | Revise with AI: changes only what the note asks, only on the named platforms and slides. | `post`; `note` (what to change); `platforms` |
| `discard` | Discards a draft; nothing is posted. | `post` |
| `status` | Lists connected accounts and their health. | None |
| `inbox` | Lists comments needing attention. | None |
| `reply_comment` | Answers a comment when a Clone Social event asks the clone to. | `comment_id`; `text` (the reply); `escalate: true` + `note` when a person should check first |
| `skip_comment` | Declines to answer a comment. | `comment_id`; `note` |
**Parameters**
| Name | Type | Notes |
|---|---|---|
| `action` | string | One of the actions above. |
| `request` | string | create_post: what the person wants, in their own words. Clone Social researches, writes and designs. |
| `text` | string | Finished post text (create_post), or the reply (reply_comment). |
| `per_platform` | string (JSON) | Finished text per platform, e.g. `{"x":{"text":"..."},"linkedin":{"text":"..."}}`. |
| `platforms` | string | Comma list: facebook, instagram, threads, x, linkedin, youtube, bluesky, tiktok, pinterest. create_post: where to post. approve: approve only these. revise: revise only these. |
| `media_urls` | string | Public https image/video links, one per line or comma separated. Optionally `instagram: https://...` to send a file to one platform. |
| `approval` | string | `review` (always wait for approval) or `auto` (publish without review where the account and clone allow it). |
| `scheduled_at` | string | ISO date-time. Empty = publish when approved. |
| `title` | string | Short internal label. |
| `first_comment` | string | Posted as the first comment (finished-text posts). |
| `post` | string | Post id or "latest". |
| `note` | string | revise: what to change. approve/reject/request_changes: feedback. reply/skip: a note for the team. |
| `page` | string | open: which page to land on. |
| `comment_id` | string | From the Clone Social event. |
| `escalate` | boolean | reply_comment: true when a person should check before it's posted. |
**When a Clone Social event asks for a comment reply**
1. Read the event: the comment, the thread, and your original post.
2. Search your knowledge base for the facts and voice you need. If the event has team notes, follow them as guidance from the team (use an approved answer when it fits). Never invent prices, dates, policies or promises.
3. Call the Clone Social skill exactly once with `reply_comment`, the `comment_id` from the event, and `text` = your reply, written as you: 1 to 3 short sentences, friendly, no hashtags.
- If the comment needs a person (complaint, refund, legal, medical, safety, or anything you're unsure about), still write your best holding reply, and set `escalate: true` with a one-line `note` for the team.
- If no reply is needed, call `skip_comment` with the `comment_id` and a `note` instead.
4. Do nothing else: don't message anyone else or use other skills.
---
## 16. Schedule Tasks: put it on autopilot
Give the clone a Schedule Task in Clone Studio and Clone Social runs on its own. Scheduled runs can create posts and check the queue; approving needs a person.
**Daily post (weekdays 8am):**
> "Use Clone Social to write today's post for all our accounts. Pick one practical topic from your knowledge that we haven't covered this week: a use case, a customer question, a tip, or something new we offer. Check the Clone Social queue first so you don't repeat a topic. Send it for review, not straight to publish."
**Daily series:**
> "Use Clone Social to write today's 'Daily Use Case Spotlight' for all our accounts: one concrete way a customer uses our product, with a clear call to action to [LINK]. Check the queue first so you don't repeat a use case this week. Send it for review."
**Weekly plan (Mondays 8am):**
> "Use Clone Social to write this week's posts for all our accounts: three posts, scheduled for Tuesday, Wednesday and Thursday at 9:00 AM. Mix the topics: one about [OUR SERVICES], one practical tip for [OUR CUSTOMERS], and one customer story or result from your knowledge. Check the queue first so you don't repeat a recent topic. Send each one for review."
The team reviews the queue once; approved posts go out on time all week.
---
## 17. Things people can ask a clone
**Posting**
- "Write today's post about [topic] for all our accounts."
- "Write a LinkedIn post and an X thread about our new feature, scheduled for Tuesday at 9am."
- "Make an Instagram carousel from these photos: [links]."
- "Post this exact text to Facebook: ..."
- "Announce our holiday hours on Facebook and Instagram, Friday at 9am."
**Reviewing**
- "What's waiting in Clone Social?"
- "Approve the latest post." / "Approve only Facebook and LinkedIn."
- "Revise the TikTok version: redo slide 3 so it shows you at a desk."
- "Make the X version shorter and send it back for review."
- "Discard the latest draft."
**Comments and accounts**
- "Any comments that need me?"
- "Open my Clone Social inbox."
- "Which accounts can you post to?"
- "Open Clone Social so I can connect Instagram."
---
## 18. Troubleshooting
| What the person sees | Likely cause | What to do |
|---|---|---|
| "No social accounts are connected yet." | Nothing connected in this workspace. | Say "Open Clone Social" and connect an account on the Accounts page (owner or admin). |
| The sign-in link says it expired | Links last 10 minutes and work once. | Ask the clone to "Open Clone Social" again. |
| A post is "held" | The account's sign-in expired or was disconnected. | Reconnect on the Accounts page; held posts go out after. |
| Facebook/Instagram posts are invisible to others | The Meta app is still in Development mode. | Switch the Meta app to Live (needs a privacy policy link). |
| Instagram account doesn't show up when connecting | It isn't a professional account, isn't linked to a Facebook Page, or isn't assigned to the system user. | Make it a Business/Creator account, link it to the Page, assign it to the system user, generate a new token and connect again. |
| "Real-time comments not on" after connecting Meta | The token lacks `pages_manage_metadata` or the App ID/secret weren't added. | Optional: add the permission and App ID/secret. Otherwise comments are still checked every 15 minutes. |
| Threads won't post | The Threads profile isn't a tester on the app. | Add it under App roles → Threads testers and accept the invite in Threads. |
| X replies fail (403) | X only lets self-serve apps reply to people who @mentioned or quoted the account. | Expected; reply in the X app for other comments. |
| YouTube sign-in stops after a week | The Google app's consent screen is in Testing. | Publish the consent screen. |
| YouTube "quota" error | The Google project's daily upload quota is used. | It resets the next day. |
| LinkedIn company page isn't available | The LinkedIn app isn't approved for the Community Management API. | Post to the profile, apply for Community Management on a separate app, or connect the page through Blotato. |
| TikTok account missing | It isn't linked inside Blotato, or was disconnected there. | Link it in Blotato, then refresh the Blotato connection in Clone Social. |
| "Fix these first: ..." when approving | A version breaks a platform rule (length, image count, missing video or title). | Edit the version or use Revise with AI, then approve. |
| "Only a person with the Approver role can approve" | The person's role is viewer or editor. | The workspace owner changes their role on the Team page. |
| Drafts are taking a while | Designed images and carousels take 5 to 10 minutes. | Wait for the clone's message, or check Approvals (posts being written show there). |
| A carousel slide doesn't show the clone | The image model missed the headshot reference on that slide. | Revise with AI: "redo slide N so it shows you, using your headshot." |
| The voice helper won't start | Voice is off for that clone, or the embed's allowed websites don't include social.clone.org. | Turn voice on in Clone Studio; add social.clone.org to the embed's allowed websites. |
For anything else, open a support case at https://support.clone.org.
---
## 19. Frequently asked questions
**Does anything get posted without approval?**
Not unless the workspace allows it. Every account starts with "every post needs approval". Admins can let specific clones publish without approval on specific accounts.
**Who writes the posts?**
The clone. Clone Social researches that clone's own knowledge base and writes in its voice. Settings only add optional guidance.
**Can I approve some platforms and fix others?**
Yes. Approve each version separately; approved ones publish while the others stay in review.
**Can the clone appear in the images?**
Yes, if the clone has a headshot in Clone Studio.
**Can I use my own photos and videos?**
Yes. Give the links when asking, or add them in the app.
**Why do I need my own app?**
It keeps the customer in control and their accounts safe: the app lives in their account, they choose which pages it can use, they can revoke it any time, and their posting isn't tied to anyone else's.
**I already use Blotato. Can I keep using it?**
Yes. Connect the Blotato API key and use every account linked there, including TikTok.
**What does it cost?**
Clone Social is a Clone skill. Comment replies are runs of the clone and use Clone credits like any other task; hidden spam costs nothing. Platform API costs (like X's per-post fee) are billed by the platform to the customer's own developer account. For plans, see https://clone.org/pricing.
**What happens if an account disconnects?**
Its posts are held, not lost, and go out after reconnecting.
**Can different clones post to different accounts?**
Yes. Choose which accounts each clone may draft for and publish to on the Team page.
**Can several people review?**
Yes. Everyone in the Clone organization can sign in; roles decide who can approve.
**How fast are comment replies?**
Comments are checked every 15 minutes (Facebook and Instagram can be real time). Automatic replies go out after a short, natural delay.
**Is my data safe?**
Keys and tokens are encrypted at rest and never shown to clones or anyone after saving. Every action is logged. Access can be revoked from each platform at any time.
**Where do I get help?**
The guides at https://support.clone.org (search "Clone Social"), the Help link in the app, or a support case.
Clone Social: complete knowledge base
For clones. Load this document into the knowledge base of every clone that uses the Clone Social skill, and every clone that helps people with Clone (support, sales, onboarding). It covers everything Clone Social does, how it works, how to set it up, how to use the skill, and how to troubleshoot it. Last updated November 16, 2026.
1. Clone Social in one minute
Clone Social lets clones run a company's or person's social media. It is two things:
- The Clone Social skill in Clone Studio. A clone with this skill can write, schedule, approve, revise and publish social posts, and answer comments, when someone asks in chat or when a Schedule Task runs.
- **The Clone Social app at https://social.clone.org**, where people review and approve posts, see the calendar, read the comments inbox, connect accounts, set rules, and see a log of everything every clone did.
What makes it different:
- The clone is the author. It researches its own knowledge base (and the web when useful) and writes in its own voice. It does not write generic AI filler.
- It makes the visuals. If no images are supplied, it designs single images and full carousels, sized for each platform. If the clone has a headshot, slides can show the clone itself.
- Nothing goes out without the rules you set. Every account starts with "every post needs approval".
- Approve one platform at a time. Good versions publish right away; the rest stay in review. "Revise with AI" changes only the platform and the slide you point at.
- The clone that wrote a post answers its comments, drafted for approval by default.
- Customers connect their own apps and keys (the way n8n and Make work). Clone never puts customers on a shared Clone app.
- Everything is logged.
Useful links:
| What | Link |
|---|---|
| The app | https://social.clone.org |
| Complete guide (support article) | https://support.clone.org/articles/clone-social |
| Setup guide: Facebook | https://support.clone.org/articles/clone-social-connect-facebook |
| Setup guide: Instagram | https://support.clone.org/articles/clone-social-connect-instagram |
| Setup guide: X | https://support.clone.org/articles/clone-social-connect-x |
| Setup guide: TikTok (through Blotato) | https://support.clone.org/articles/clone-social-connect-tiktok |
| Setup guide: Threads | https://support.clone.org/articles/clone-social-connect-threads |
| Daily social post routine | https://support.clone.org/libraries/skill-instructions/daily-social-post |
| Weekly social plan routine | https://support.clone.org/libraries/skill-instructions/weekly-social-plan |
| Product pages | https://clone.me/social (also /social/comments and /social/security-and-your-apps) |
2. Words to know
| Term | Meaning |
|---|---|
| Workspace | A Clone organization's space in Clone Social. Everyone in the same Clone organization shares one workspace. |
| Account | One social profile or page Clone Social may use, for example the "CloneMe" Facebook Page or the "@clone.org" Instagram account. |
| Connection | The link to a platform through the customer's own app or key (for example one Meta app connection can provide several Facebook Pages and Instagram accounts). |
| Post | One piece of content going to one or more accounts. |
| Version (variant) | The platform-specific copy of a post for one account: its own text, images, slides and limits. A post to five accounts has five versions. |
| Approvals | The queue of posts waiting for review. |
| Revise with AI | Asking the AI to change a draft. Only the named platforms and slides change. |
| Held | A version that couldn't publish because the account needs attention (for example a disconnected account). Held is not failed: it publishes after the problem is fixed. |
| Inbox | Comments on your posts, the replies clones drafted, and anything flagged for a person. |
| Reply mode | Per account: Draft & suggest (default), Always automatic, or Off. |
| Activity log | The record of every action by every clone and person. |
| Blotato | A posting service some customers already use. Clone Social can post through the customer's own Blotato account. |
3. Why it's valuable
Social media rewards consistency, and consistency is what busy teams can't sustain. Most businesses post in bursts, go quiet for weeks and leave comments unanswered. Clone Social takes over the parts that take the time:
| The usual work | With Clone Social |
|---|---|
| Deciding what to say | The clone already knows the products, customers, pricing and stories, and proposes and writes the post. |
| Rewriting one idea for five platforms | One request becomes a native version per platform: a carousel for Instagram, slides for TikTok, a professional post for LinkedIn, 280 characters for X. |
| Making graphics | Images and carousels are designed for you, on brand, with the clone in them when it helps. |
| Copy-pasting into five apps at the right time | Approved posts publish themselves on schedule. |
| Comments sitting for days | The clone that wrote the post drafts a reply within minutes, in context. |
| Checking facts and claims | A compliance pass flags unsupported numbers, missing credits and risky claims before anyone reviews. |
| "Who posted that?" | Every action is logged with who did it and who approved it. |
Real example (Clone's own accounts, November 16, 2026): one chat request, "Write today's Daily Use Case Spotlight for all our accounts, and send it for review", produced five versions in about 8 minutes: a Facebook image post, a 6-slide Instagram carousel, a LinkedIn image post, an X post and a 6-slide TikTok carousel featuring the clone. The team approved them one at a time and fixed one TikTok slide with "Revise with AI" without touching anything else. All five went live.
4. How a post gets made
When someone asks for a post without giving the finished words, Clone Social runs a writing pipeline on the requesting clone's behalf:
- Understand the request. Topic, angle, audience, call to action, which accounts, any exact wording, links, special day.
- Research. Search the clone's own knowledge base for facts, stories, offers and the right links; search the web when timely context helps (a recent survey, a seasonal moment).
- Write. A platform-native version for every account the clone may draft for, within each platform's limits.
- Compliance check. Flags unsupported statistics, claims that need a source, missing credits and anything risky. Notes appear on the draft for the reviewer.
- Design images. Single images or carousels (up to 20 slides on Instagram), correctly sized. Slides can feature the clone if it has a headshot in Clone Studio.
- Send for review. Drafts land in Approvals and the clone tells the person in chat, with a link.
Timing. The clone replies right away with an estimate. Text-only posts take about 1 to 2 minutes; posts with designed images or carousels usually take 5 to 10 minutes. The clone messages again when the drafts are ready.
Media.
- If the person supplies images or videos (public https links), Clone Social uses them. Media can be sent to a specific platform with a prefix, for example
instagram: https://.... - If no media is supplied, Clone Social designs it where the platform benefits from it.
- All media is copied into Clone Social's own storage before publishing, so every platform can fetch it reliably.
Exact copy. If the person gives the exact words ("post this exactly: ..."), Clone Social posts that text as written, with no rewriting. Finished text can also be different per platform.
Which accounts. By default, every account the clone is allowed to draft for (set on the Team page). The person can name platforms: "just Facebook and LinkedIn".
5. Reviewing and approving
In the app (social.clone.org)
Each post opens with one card per platform version, two per row on a computer and one per row on a phone.
- Status bar at the top: "3 of 5 decided" plus one pill per platform (green = live, amber = needs review, blue = approved/publishing, red = failed). Tap a pill to jump to that card. Request changes and Approve all / Approve remaining sit in the same bar.
- Each card shows the account, platform, status, the media (carousels as numbered slides; click any image to open it full size, use arrow keys to move between slides), the text (editable inline, with a character counter for the platform's limit), compliance notes and any errors.
- Card buttons: Approve & publish (publishes that platform now, or at the scheduled time) and Revise with AI. Live cards show View on [platform] ↗.
- Editing: change any text inline. An edited card says "Edited, not saved". Approving saves the edit first. Editing a version clears its approval (it goes back to review).
- Request changes sends the post back to the clone with the note.
- Notes & decisions: notes the clone sees when it revises.
- History: every version is saved with who changed what.
- Archive post removes a post that won't be used.
Approving one platform at a time
Approve each version on its own. Approved versions publish right away (or at the scheduled time) even while other versions stay in review. The post stays "in review" until every version is decided. "Approve all" approves everything still waiting. A version with a blocking check (for example "X allows 280 characters") must be fixed before it can be approved.
Revise with AI
Say what to change. Only that changes.
- Pick platforms: on a card, Revise with AI selects just that platform. In the Revise box you can pick several. None picked means every platform still in review.
- Slides by number: "redo slide 3 so it shows the clone at a desk" regenerates only slide 3. Every other slide keeps its exact image.
- Text only: if the feedback isn't about images, images stay as they are.
- The revised versions go back to review, and the clone tells the person in chat when the revision is ready (usually a minute or two, longer with new images).
From chat
- "Approve the latest post." (approves everything waiting)
- "Approve only Facebook and LinkedIn." (approves just those; the rest stay in review)
- "Revise the TikTok version: redo slide 4 with the clone at a desk."
- "Reject it." / "Send it back: make it shorter."
- "Discard the latest draft." (nothing is posted)
Only people with the approver role or higher can approve, from chat or the app. A Schedule Task (no person in the chat) cannot approve.
6. Publishing
- Approved versions publish at the scheduled time, or within about a minute if no time was set.
- Times are in the workspace's time zone.
- When versions go live, the clone posts the live links back into the chat ("Facebook: https://..."), plus anything still waiting for review. It tells you once per finished batch.
- Held, not lost: if an account is disconnected or its sign-in expired, its versions are held. The person is told, and the posts go out after reconnecting.
- Failed: if a platform rejects a post (for example a rule the platform enforces at publish time), the version is marked failed with the platform's reason, and the person is told.
- Sign-ins renew automatically where the platform allows it (X every 2 hours, Google every hour, Threads before 60 days, Bluesky sessions). LinkedIn sign-ins last 60 days; Clone Social reminds the workspace a week before.
7. Comment replies
How it works
- Clone Social checks connected accounts for new comments every 15 minutes. Facebook and Instagram can also notify in real time if the Meta connection includes the app ID, app secret and the
pages_manage_metadatapermission. - Obvious spam and abuse is hidden automatically (never deleted; it can be unhidden). Hidden spam does not wake a clone and costs nothing.
- For a real comment, the clone that made the post is woken (through a Studio Event) with the comment, its own post and the team's notes. It writes the reply from its own knowledge.
- What happens next depends on the account's reply mode.
Reply modes (per account)
| Mode | What happens |
|---|---|
| Draft & suggest (default) | The clone drafts every reply; a person approves it in the Inbox. |
| Always automatic | Replies go out on their own after a short, natural delay (3 to 12 minutes by default, not instantly). Anything the clone flags as sensitive still waits for a person. |
| Off | Comments show in the Inbox and people answer them; no clone is woken. |
Reply settings (per account, Accounts page)
| Setting | Default |
|---|---|
| Reply mode | Draft & suggest |
| Hide obvious spam and abuse | On (hidden, never deleted) |
| Sensitive replies wait for a person, even in automatic mode | On |
| Reply delay window (automatic) | 3 to 12 minutes |
| Quiet hours | Off (for example 22:00 to 07:00 in the workspace time zone) |
| Maximum replies per hour | 20 |
| One reply per thread | On |
| Signature | None (for example "Quinn, our AI teammate") |
| Clone for comments on posts no clone wrote | None (people's own posts and older posts) |
Turning on comment replies for a clone (one time per clone)
Comment replies wake the clone through Clone Studio Events. On the Team page in Clone Social, under Comment replies, the steps are:
- In Clone Studio → Events → Sources, add a Custom HTTP push source named "Clone Social – [clone name]". Copy its URL and secret into Clone Social.
- On the clone → Events → Link event source: filter off, immediate, batch size 1, thread Fresh. Paste the processing prompt shown on the Team page (it has a Copy button).
- Press Send a test in Clone Social to confirm the clone receives events.
Comment support by platform
| Platform | Read comments | Reply | Other actions |
|---|---|---|---|
| Yes (real time available) | Yes | Hide, delete, like | |
| Yes (real time available) | Yes | Hide, delete | |
| Threads | Yes | Yes | Hide replies |
| X | Mentions and quotes | Only to people who @mentioned or quoted the account (an X rule since February 2026) | Delete own replies |
| Company pages, once LinkedIn approves the customer's app for its Community Management API | Yes (same) | Delete | |
| YouTube | Yes | Yes (to the top-level comment) | Hold for review, remove |
| Bluesky | Yes | Yes | None |
| Through Blotato | Instagram and Facebook only | Yes | None |
Inbox
The Inbox lists new comments, replies waiting for approval, scheduled automatic replies, and anything a clone escalated. People approve, edit, skip or answer themselves. Approved answers saved in Settings can be reused.
Cost
Each comment reply is a run of the clone and uses Clone credits like any other task. Hidden spam doesn't wake a clone, so it costs nothing.
8. Activity log and undo
The Activity log records every action by every clone and every person: drafts, edits, approvals, publishes, failures, replies, hides, connection changes and settings changes, with who did it, who approved it, and when. Undo is one click where it makes sense: hold an automatic reply before it goes, delete a reply that was posted, or unhide a comment.
9. The app, page by page
Signing in: say "Open Clone Social" to any clone with the skill. It sends a one-time link that works once and expires in 10 minutes. Sessions last 7 days. People who aren't signed in see a public landing page at social.clone.org.
The header (same design as support.clone.org) has: Overview, Approvals (with a count), Calendar, Inbox (with a count), Activity log, Accounts, plus Help (the guide), the account menu (Team, Settings, Connected accounts, Guide & setup help, Sign out) and a New post button. On a phone, the menu button shows all pages.
| Page | What it's for |
|---|---|
| Overview | What's waiting, what's scheduled, what went out, connected accounts and recent activity. |
| Approvals | Every post waiting for review, plus posts clones are still writing (with their progress). |
| Post page | The review screen described in section 5. |
| New post | Write or paste a post yourself, pick accounts, add media, schedule it. |
| Calendar | Everything scheduled and published, by day. |
| Inbox | Comments, drafted replies, escalations. |
| Activity log | Every action by every clone and person. |
| Accounts | Connect platforms, choose which accounts Clone Social may use, set each account's post-approval and reply rules, refresh or disconnect. |
| Team | People and roles, which accounts each clone may draft for and publish to, and the comment-replies setup per clone. |
| Settings | Optional guidance for clones, approved answers, and the voice helper. |
10. People, roles and clone permissions
People. Anyone in the Clone organization can sign in through their own clone. The first person becomes the owner.
| Role | Can do |
|---|---|
| Viewer | See everything. |
| Editor | Create and edit posts, request revisions. |
| Approver | Everything an editor can, plus approve or reject posts and replies. |
| Admin | Everything an approver can, plus connect accounts, change account rules, set clone permissions, set up comment replies, and change settings and the voice helper. |
| Owner | Everything, including changing people's roles. |
Clones. On the Team page, an admin sets for each clone and each account whether it may draft posts, publish without approval (only on accounts whose posting rule is "Clones with publish rights skip approval"), and reply to comments. By default every post needs approval.
Post approval rule (per account): "Every post needs approval" (default) or "Clones with publish rights skip approval".
11. Settings (all optional)
Clones already know the business from their knowledge bases. Settings add optional guidance that goes along with every request:
| Setting | Use it for |
|---|---|
| Brand name | How to refer to the business. |
| Voice notes | "Warm, a little playful, never salesy. First names. No exclamation marks." |
| Extra facts | Hours, policies, offers the clones should always know. |
| Link template | Tracking parameters added to links (for example UTM tags). |
| Image style | A house style for designed images. |
| Approved answers | Exact answers the team wants used for common questions in replies. |
| Voice helper | An admin pastes any clone's Clone Studio embed code (Clone Studio → the clone → Integrations → Embed). That clone appears as a voice bubble in the bottom-right corner of every page for everyone in the workspace. Voice must be on for that clone. |
12. Platforms
What's connected today
| Platform | How it connects | Post types | Key limits |
|---|---|---|---|
| Facebook Pages | Customer's own Meta app | Text, links, photos (up to 10), video, Reels | Text or media required |
| Instagram (professional accounts linked to a Facebook Page) | Same Meta app | Photo, carousel (up to 20 items), Reels (video up to 15 minutes), Stories | Media required; caption 2,200 characters; at most 30 hashtags; links in captions are not clickable |
| Threads | Customer's own Meta app with the Threads use case | Text, links, images, carousels (up to 20), video | 500 characters; at most 5 links |
| X | Customer's own X developer app | Text, links, images (up to 4) or one video, threads | 280 characters per post; every link counts as 23 |
| Customer's own LinkedIn app | Text, links, images (up to 20) on the person's profile; company pages after LinkedIn approves the app | 3,000 characters; video not yet | |
| YouTube | Customer's own Google Cloud app | Videos and Shorts (vertical, up to 3 minutes) | Exactly one video; title up to 100 characters (no < or >); description up to 5,000 bytes |
| Bluesky | An app password (no developer app) | Text, links, up to 4 images, threads | 300 characters; images up to 1 MB; video not yet |
| Blotato | Customer's own Blotato API key | Every account linked in their Blotato: X, TikTok, LinkedIn (including company pages), YouTube, Threads, Bluesky, Pinterest, Facebook, Instagram | Same platform limits; TikTok up to 35 images and needs media; Pinterest one image and needs media |
TikTok today goes through Blotato. A direct TikTok connection is coming; TikTok audits every app before it can post publicly. Through Blotato, TikTok posts default to public and are labeled as AI-generated content.
Coming soon: Mastodon, Telegram, Discord and Tumblr (customer's own app), and the posting services Ayrshare, Zernio, Upload-Post and Publer. Google Business Profile, Pinterest (direct), Reddit and Snapchat require the platform to approve the customer's app first.
Platform-specific rules the clone writes for
- Instagram: links in captions aren't clickable, so the clone writes a plain destination such as "example.com/menu" (or puts the link in the first comment where that helps). At most 5 hashtags is the house style; Instagram's hard limit is 30.
- X: under 280 characters per post, links count as 23 each. Threads are supported.
- LinkedIn: under 3,000 characters, professional tone.
- Threads: under 500 characters, conversational, one idea.
- Bluesky: under 300 characters.
- YouTube: needs a title and a video.
13. Connecting accounts: your apps, your keys
Clone Social works like n8n and Make: the customer brings their own app. They create a developer app in their own Meta, X, LinkedIn or Google account (or use their own Blotato account) and give Clone Social its keys. Why:
- Security: the app lives in the customer's account. They decide its permissions and can revoke it any time from the platform.
- Control: when connecting, they pick exactly which pages and profiles Clone Social may use. Nothing else is touched.
- No middleman: posting isn't routed through a shared app that a platform could throttle or suspend for everyone.
- Their limits, their costs: platform API costs (X charges per post) and limits stay on their own account.
- Encrypted: keys and tokens are encrypted at rest, never shown again after saving, and never handed to clones. Clones only ask Clone Social to act; they never see credentials.
Only owners and admins can connect accounts (Accounts page). After connecting, a picker lists the pages and profiles found; tick the ones Clone Social may use and press Done.
Summary of each connection (full steps in the support guides)
| Platform | What the customer creates | Notes |
|---|---|---|
| Facebook + Instagram | A Meta app (business portfolio), with the Pages and Instagram permissions; a system user with a token set to never expire, with the Pages and Instagram accounts assigned to it first. Paste the token, plus the App ID and App secret for real-time comments. | Switch the app to Live (needs a privacy policy link); in Development mode posts are only visible to people with a role on the app. Alternative: "Sign in through your app" with Facebook Login for Business and the redirect address shown. Instagram must be a professional account linked to a Facebook Page. |
| X | An X developer app, OAuth 2.0, Web App (confidential client), Read and write, with the callback URL shown in Clone Social. Paste the OAuth 2.0 Client ID and Secret, then sign in. | X bills usage to the customer's developer account (roughly $0.015 per post, more with a link; check the X console). |
| Threads | The Meta app with the "Access the Threads API" use case and its four permissions, the redirect address shown, and the Threads app ID and secret (different from Facebook's). | Until Meta approves the app, it can only post for Threads testers: add your own Threads profile as a tester and accept the invite in Threads (Settings → Account → Website permissions). |
| A LinkedIn app linked to a company page, with "Sign In with LinkedIn using OpenID Connect" and "Share on LinkedIn". | Company pages and their comments need LinkedIn to approve the app for the Community Management API (LinkedIn requires a separate app with no other products). Sign-ins last 60 days. | |
| YouTube | A Google Cloud project with the YouTube Data API v3, an OAuth consent screen (External, published so sign-ins don't end after 7 days), and a Web OAuth client with the redirect address shown. | Uploads have their own daily quota per Google project. |
| Bluesky | An app password (Bluesky → Settings → Privacy and security → App passwords). | No developer app needed. |
| Blotato (and TikTok) | The Blotato API key (Blotato → Settings → API; API access needs a paid Blotato plan). Link TikTok and other accounts inside Blotato first. | Don't disconnect accounts inside Blotato or Clone Social loses them too. |
The redirect/callback address for every "sign in through your app" connection is **https://social.clone.org/connect/oauth/callback**.
If someone needs help, point them to the setup guide for their platform and walk them through it step by step.
14. Getting started checklist
- Add the skill: in Clone Studio, add the Clone Social skill to the clones that should manage social media.
- Open Clone Social: say "Open Clone Social" and tap the one-time link. The first person becomes the owner.
- Connect accounts: on the Accounts page, pick a platform and follow its guide; tick the pages and profiles to use.
- Set each account's rules: post approval and reply mode (Draft & suggest is the default).
- Give clones access: on the Team page, choose which accounts each clone may draft for (and publish to, if wanted).
- Turn on comment replies: one time per clone, on the Team page (see section 7).
- Invite the team: colleagues sign in through their own clones; give them roles.
- Ask for the first post: "Write a post introducing our team for all our accounts and send it for review."
- Optional: add a Schedule Task so it runs every day or week (section 16), add a voice helper in Settings.
15. The Clone Social skill: reference for clones
Golden rules
- Call the skill once per request. Never retry the same call.
- Relay Clone Social's reply to the person exactly as written. Put every link on its own line (some chat channels, like SMS, break formatted links).
- When the reply says "Relay this to the user as written", do exactly that, without adding anything.
- Actions that need a person in the chat (like open) don't work from a Schedule Task.
Actions
| Action | What it does | Main parameters |
|---|---|---|
open | Sends a one-time sign-in link (10 minutes, single use). Goes to Accounts if nothing is connected yet. | page: queue, inbox, calendar, accounts, team, settings |
create_post | Writes and sends drafts for review from a request, or saves finished text. Replies immediately with a time estimate when writing. | request (the person's words) OR text (finished copy); platforms; media_urls; scheduled_at; approval; per_platform; first_comment; title |
queue | Lists what's waiting for review and what's scheduled. | None |
approve | Approves the post (all waiting versions), or only named platforms. Needs a person with the approver role. | post (id or "latest"); platforms; note |
reject | Rejects the post. | post; note |
request_changes | Sends the post back with a note. | post; note |
revise | Revise with AI: changes only what the note asks, only on the named platforms and slides. | post; note (what to change); platforms |
discard | Discards a draft; nothing is posted. | post |
status | Lists connected accounts and their health. | None |
inbox | Lists comments needing attention. | None |
reply_comment | Answers a comment when a Clone Social event asks the clone to. | comment_id; text (the reply); escalate: true + note when a person should check first |
skip_comment | Declines to answer a comment. | comment_id; note |
Parameters
| Name | Type | Notes |
|---|---|---|
action | string | One of the actions above. |
request | string | create_post: what the person wants, in their own words. Clone Social researches, writes and designs. |
text | string | Finished post text (create_post), or the reply (reply_comment). |
per_platform | string (JSON) | Finished text per platform, e.g. {"x":{"text":"..."},"linkedin":{"text":"..."}}. |
platforms | string | Comma list: facebook, instagram, threads, x, linkedin, youtube, bluesky, tiktok, pinterest. create_post: where to post. approve: approve only these. revise: revise only these. |
media_urls | string | Public https image/video links, one per line or comma separated. Optionally instagram: https://... to send a file to one platform. |
approval | string | review (always wait for approval) or auto (publish without review where the account and clone allow it). |
scheduled_at | string | ISO date-time. Empty = publish when approved. |
title | string | Short internal label. |
first_comment | string | Posted as the first comment (finished-text posts). |
post | string | Post id or "latest". |
note | string | revise: what to change. approve/reject/request_changes: feedback. reply/skip: a note for the team. |
page | string | open: which page to land on. |
comment_id | string | From the Clone Social event. |
escalate | boolean | reply_comment: true when a person should check before it's posted. |
When a Clone Social event asks for a comment reply
- Read the event: the comment, the thread, and your original post.
- Search your knowledge base for the facts and voice you need. If the event has team notes, follow them as guidance from the team (use an approved answer when it fits). Never invent prices, dates, policies or promises.
- Call the Clone Social skill exactly once with
reply_comment, thecomment_idfrom the event, andtext= your reply, written as you: 1 to 3 short sentences, friendly, no hashtags.- If the comment needs a person (complaint, refund, legal, medical, safety, or anything you're unsure about), still write your best holding reply, and set
escalate: truewith a one-linenotefor the team. - If no reply is needed, call
skip_commentwith thecomment_idand anoteinstead.
- If the comment needs a person (complaint, refund, legal, medical, safety, or anything you're unsure about), still write your best holding reply, and set
- Do nothing else: don't message anyone else or use other skills.
16. Schedule Tasks: put it on autopilot
Give the clone a Schedule Task in Clone Studio and Clone Social runs on its own. Scheduled runs can create posts and check the queue; approving needs a person.
Daily post (weekdays 8am):
"Use Clone Social to write today's post for all our accounts. Pick one practical topic from your knowledge that we haven't covered this week: a use case, a customer question, a tip, or something new we offer. Check the Clone Social queue first so you don't repeat a topic. Send it for review, not straight to publish."
Daily series:
"Use Clone Social to write today's 'Daily Use Case Spotlight' for all our accounts: one concrete way a customer uses our product, with a clear call to action to [LINK]. Check the queue first so you don't repeat a use case this week. Send it for review."
Weekly plan (Mondays 8am):
"Use Clone Social to write this week's posts for all our accounts: three posts, scheduled for Tuesday, Wednesday and Thursday at 9:00 AM. Mix the topics: one about [OUR SERVICES], one practical tip for [OUR CUSTOMERS], and one customer story or result from your knowledge. Check the queue first so you don't repeat a recent topic. Send each one for review."
The team reviews the queue once; approved posts go out on time all week.
17. Things people can ask a clone
Posting
- "Write today's post about [topic] for all our accounts."
- "Write a LinkedIn post and an X thread about our new feature, scheduled for Tuesday at 9am."
- "Make an Instagram carousel from these photos: [links]."
- "Post this exact text to Facebook: ..."
- "Announce our holiday hours on Facebook and Instagram, Friday at 9am."
Reviewing
- "What's waiting in Clone Social?"
- "Approve the latest post." / "Approve only Facebook and LinkedIn."
- "Revise the TikTok version: redo slide 3 so it shows you at a desk."
- "Make the X version shorter and send it back for review."
- "Discard the latest draft."
Comments and accounts
- "Any comments that need me?"
- "Open my Clone Social inbox."
- "Which accounts can you post to?"
- "Open Clone Social so I can connect Instagram."
18. Troubleshooting
| What the person sees | Likely cause | What to do |
|---|---|---|
| "No social accounts are connected yet." | Nothing connected in this workspace. | Say "Open Clone Social" and connect an account on the Accounts page (owner or admin). |
| The sign-in link says it expired | Links last 10 minutes and work once. | Ask the clone to "Open Clone Social" again. |
| A post is "held" | The account's sign-in expired or was disconnected. | Reconnect on the Accounts page; held posts go out after. |
| Facebook/Instagram posts are invisible to others | The Meta app is still in Development mode. | Switch the Meta app to Live (needs a privacy policy link). |
| Instagram account doesn't show up when connecting | It isn't a professional account, isn't linked to a Facebook Page, or isn't assigned to the system user. | Make it a Business/Creator account, link it to the Page, assign it to the system user, generate a new token and connect again. |
| "Real-time comments not on" after connecting Meta | The token lacks pages_manage_metadata or the App ID/secret weren't added. | Optional: add the permission and App ID/secret. Otherwise comments are still checked every 15 minutes. |
| Threads won't post | The Threads profile isn't a tester on the app. | Add it under App roles → Threads testers and accept the invite in Threads. |
| X replies fail (403) | X only lets self-serve apps reply to people who @mentioned or quoted the account. | Expected; reply in the X app for other comments. |
| YouTube sign-in stops after a week | The Google app's consent screen is in Testing. | Publish the consent screen. |
| YouTube "quota" error | The Google project's daily upload quota is used. | It resets the next day. |
| LinkedIn company page isn't available | The LinkedIn app isn't approved for the Community Management API. | Post to the profile, apply for Community Management on a separate app, or connect the page through Blotato. |
| TikTok account missing | It isn't linked inside Blotato, or was disconnected there. | Link it in Blotato, then refresh the Blotato connection in Clone Social. |
| "Fix these first: ..." when approving | A version breaks a platform rule (length, image count, missing video or title). | Edit the version or use Revise with AI, then approve. |
| "Only a person with the Approver role can approve" | The person's role is viewer or editor. | The workspace owner changes their role on the Team page. |
| Drafts are taking a while | Designed images and carousels take 5 to 10 minutes. | Wait for the clone's message, or check Approvals (posts being written show there). |
| A carousel slide doesn't show the clone | The image model missed the headshot reference on that slide. | Revise with AI: "redo slide N so it shows you, using your headshot." |
| The voice helper won't start | Voice is off for that clone, or the embed's allowed websites don't include social.clone.org. | Turn voice on in Clone Studio; add social.clone.org to the embed's allowed websites. |
For anything else, open a support case at https://support.clone.org.
19. Frequently asked questions
Does anything get posted without approval? Not unless the workspace allows it. Every account starts with "every post needs approval". Admins can let specific clones publish without approval on specific accounts.
Who writes the posts? The clone. Clone Social researches that clone's own knowledge base and writes in its voice. Settings only add optional guidance.
Can I approve some platforms and fix others? Yes. Approve each version separately; approved ones publish while the others stay in review.
Can the clone appear in the images? Yes, if the clone has a headshot in Clone Studio.
Can I use my own photos and videos? Yes. Give the links when asking, or add them in the app.
Why do I need my own app? It keeps the customer in control and their accounts safe: the app lives in their account, they choose which pages it can use, they can revoke it any time, and their posting isn't tied to anyone else's.
I already use Blotato. Can I keep using it? Yes. Connect the Blotato API key and use every account linked there, including TikTok.
What does it cost? Clone Social is a Clone skill. Comment replies are runs of the clone and use Clone credits like any other task; hidden spam costs nothing. Platform API costs (like X's per-post fee) are billed by the platform to the customer's own developer account. For plans, see https://clone.org/pricing.
What happens if an account disconnects? Its posts are held, not lost, and go out after reconnecting.
Can different clones post to different accounts? Yes. Choose which accounts each clone may draft for and publish to on the Team page.
Can several people review? Yes. Everyone in the Clone organization can sign in; roles decide who can approve.
How fast are comment replies? Comments are checked every 15 minutes (Facebook and Instagram can be real time). Automatic replies go out after a short, natural delay.
Is my data safe? Keys and tokens are encrypted at rest and never shown to clones or anyone after saving. Every action is logged. Access can be revoked from each platform at any time.
Where do I get help? The guides at https://support.clone.org (search "Clone Social"), the Help link in the app, or a support case.
Earlier versions (1)
- v1 · Nov 16, 2026
Was this useful?
Thanks!