Documentation Index

Fetch the complete documentation index at: https://docs.signalrooms.xyz/llms.txt

Use this file to discover all available pages before exploring further.

​

Captions

​

Turning it on

• Off → the TikTok caption field is left empty.
• On → pick one of the four sources below.

​

Cheat sheet: which source to pick

                    ┌─ One-or-two variants for all posts   → Inline text
                    │
same captions       ├─ 10+ simple captions, no titles      → Text file (.txt)
across all clips ───┤
                    └─ Need titles, need Sequential        → JSON file

unique caption ──→ Sidecar (video: <name>.json,
per file                     carousel: content.json in subfolder)

​

Option 1. Inline text: multiple captions separated by ;

​

When to use

​

What to set

• Source → Text.
• Descriptions field → all variants on one line, separated by ;.

​

Example

First caption #tag1; Second caption with emoji 🎬; Third caption @mention #hot

​

How variants are picked

​

Pitfalls

• A literal ; in a caption is treated as a separator, move that caption to a .txt or sidecar instead.
• Empty blocks between ;; are ignored.

​

Option 2. Text file: .txt, one caption per line

​

When to use

​

What to set

• Source → TXT file.
• Descriptions file (.txt) → absolute path to a .txt (extension must be .txt; .text, .md, .csv are ignored).

​

File format

• Encoding: UTF-8 (BOM supported).
• Line endings: LF or CRLF (normalized).
• One line = one caption.
• Empty lines are ignored.
• Hashtags and emoji go inline in the caption text, there are no separate fields.

​

Example

Put your caption here, replace this line with your own text
Add hashtags inline like this #example #replace_me
Emojis work too 🎬, drop them anywhere in the caption
Each line in this file becomes one TikTok caption
Empty lines are ignored, max 2200 characters per caption

​

How variants are picked

​

Pitfalls

• Don’t use # for comments, a line starting with # will be posted as a caption with a hashtag.
• Only .txt is parsed. Renaming a .md to .txt works; pointing at a .md does not.

​

Option 3. JSON file: {title, description} per post

​

When to use

• Carousels need separate titles (TikTok’s Title field).
• You need sequential ordering (not just random).
• Content is generated by a pipeline that prefers structured storage.

​

What to set

• Source → JSON file.
• Title+Description file (.json) → absolute path.
• Selection order:
  • Sequential: items used in order: first, second, third…
  • Random: random without repeats.

​

File format

[
  { "title": "...", "description": "..." },
  { "title": "...", "description": "..." }
]

​

Example

[
  {
    "_comment": "This key is ignored by the parser",
    "title": "Put your title here",
    "description": "Put your description here. Replace this with your TikTok caption #hashtag"
  },
  {
    "title": "",
    "description": "Leave title empty if you don't want one. Only the description will be set"
  },
  {
    "title": "Add hashtags inline",
    "description": "Hashtags go inside the description, not a separate field 🎯 #example #replace"
  }
]

​

Pitfalls

• JSON must be valid. Any syntax error and the source falls back to the legacy .txt / inline text, if defined.
• Empty array [] → no descriptions → fallback fires.
• Encoding must be UTF-8.

​

Option 4. Sidecar: a separate .json next to each media file

​

When to use

• Each video or carousel has its own unique caption, and a strict “this caption → this file” binding matters.
• Content is prepared by an external pipeline that drops a caption next to each clip.
• In onboarding runs, to avoid mixing up which caption belongs to which clip.

​

What to set

• Source → Sidecar files.
• If sidecar is missing → what to do when a file has no sidecar:
  • Skip description (default), leave the TikTok caption empty.
  • Use inline text: fall back to the global Descriptions field.
  • Use global .txt: fall back to the global .txt.
  • Use global .json: fall back to the global .json.

​

Sidecar file format

{
  "title": "Put your title here",
  "description": "Put your description here. Replace this with your TikTok caption #hashtag"
}

[
  { "title": "...", "description": "..." }
]

​

Where to put the sidecar

​

Video

videos/
├── clip_1.mp4
├── clip_1.json          ← caption for clip_1.mp4
├── clip_2.mov
├── clip_2.json          ← caption for clip_2.mov
└── clip_3.mp4           ← no sidecar, fallback kicks in

​

Carousel: subfolder mode (supported)

1. content.json
2. description.json
3. caption.json
4. Any first *.json (natural sort).

carousels/
├── 01_summer/
│   ├── 1.jpg
│   ├── 2.jpg
│   ├── 3.jpg
│   └── content.json          ← priority 1
├── 02_promo/
│   ├── photo_a.png
│   ├── photo_b.png
│   └── description.json      ← priority 2
└── 03_lifestyle/
    ├── img1.png
    └── caption.json          ← priority 3

​

Carousel: flat mode (not supported)

​

What happens to the sidecar after publishing

• Video: <name>.json moves to used/ (or is deleted) together with the video, in sync.
• Carousel in subfolders: the entire subfolder moves to used/ as a unit; the sidecar inside goes along.

​

Hashtags, mentions, titles, music: where each lives

​

Limits and normalization

• Maximum 2200 characters per caption (TikTok’s hard cap).
• Longer captions are truncated to 2200 and a WARNING is logged.
• A BOM () at the start of a file is stripped automatically.
• Line endings are normalized (\r\n → \n, \r → \n).
• Leading and trailing whitespace is trimmed.

​

Troubleshooting

​

Related

• Posting runs, full template setup, including the Description card.
• Content folder structure, where media lives for each mode.