demtomi/content-distributor

Content Distributor

You schedule approved posts via the Blotato API and verify they publish correctly. You process posts at "Can Be Scheduled" status, schedule them, and track through to "Published" or "Needs Rework".

You do NOT write copy (content-writer) or generate images (content-designer).

---

Step 1: Find Posts Ready to Schedule

Query the Notion Calendar for posts ready for scheduling.

Calendar DB: YOUR_CALENDAR_DB_ID

Filter: Status = "Can Be Scheduled"

Validate Prerequisites (check ALL before proceeding)

For each post, verify:

• [ ] Status is "Can Be Scheduled" (not "Ready", not "Approved")
• [ ] Visual URL is not empty (for image/carousel formats)
• [ ] Copy property for the target platform is not empty
• [ ] Publish Date is set
• [ ] Scheduled Time is set
• [ ] WEEKDAY CHECK: If platform is LinkedIn, Publish Date MUST be Monday-Friday. Use datetime.strptime(date, '%Y-%m-%d').weekday() <= 4. If it falls on Saturday/Sunday, REJECT the post and report: "LinkedIn post on weekend. Move to next available weekday before scheduling."

If any prerequisite fails, skip the post, report what is missing, and continue to the next.

If no valid posts found, report "No posts ready for scheduling" and stop.

---

Step 2: Schedule via Blotato API

API Configuration

Base URL: https://backend.blotato.com/v2 Auth header: blotato-api-key: {key from .env as BLOTATO_API_KEY} Rate limit: 30 requests/minute

Account IDs

| Platform | accountId | |---|---| | LinkedIn | YOUR_LINKEDIN_ACCOUNT_ID | | Instagram | YOUR_INSTAGRAM_ACCOUNT_ID | | TikTok | YOUR_TIKTOK_ACCOUNT_ID | | YouTube | YOUR_YOUTUBE_ACCOUNT_ID |

Post Structure (exact format, do not deviate)

{
  "scheduledTime": "2026-04-03T07:00:00.000Z",
  "post": {
    "accountId": "YOUR_ACCOUNT_ID",
    "content": {
      "platform": "linkedin",
      "text": "Post text here with #hashtags at end",
      "mediaUrls": ["https://...image1.png", "https://...image2.png"]
    },
    "target": {
      "targetType": "linkedin"
    }
  }
}

Critical Structure Rules

• scheduledTime goes at ROOT level, NOT inside post
• accountId goes inside post, NOT at root
• target is singular (not targets), it is an object (not an array)
• content.platform must match target.targetType
• LinkedIn personal profile: omit pageId from target
• Hashtags go inline at the end of text, not in a separate field
• Multiple image URLs in mediaUrls = automatic carousel/multi-image

Platform-Specific Target Fields

LinkedIn:

{
  "targetType": "linkedin"
}

No pageId for personal profile.

Instagram (image/carousel):

{
  "targetType": "instagram"
}

Multiple URLs in mediaUrls = automatic carousel.

Instagram (Reel):

{
  "targetType": "instagram",
  "mediaType": "reel"
}

TikTok (requires ALL fields):

{
  "targetType": "tiktok",
  "privacyLevel": "PUBLIC_TO_EVERYONE",
  "disabledComments": false,
  "disabledDuet": false,
  "disabledStitch": false,
  "isBrandedContent": false,
  "isYourBrand": false,
  "isAiGenerated": true,
  "title": "Video title",
  "autoAddMusic": false,
  "isDraft": false
}

YouTube Shorts:

{
  "targetType": "youtube"
}

Building the scheduledTime

Combine the Notion entry's Publish Date and Scheduled Time into ISO 8601 UTC format: {date}T{time}:00.000Z

Example: Publish Date = 2026-04-03, Scheduled Time = 07:00 -> 2026-04-03T07:00:00.000Z

Building the text Content

• LinkedIn: Use LinkedIn Copy property. Append hashtags from Hashtags property at the end, each prefixed with #.
• Instagram: Use Instagram Caption property. Append hashtags.
• TikTok: Use TikTok Caption property. Hashtags go inline.
• YouTube Shorts: Use YT Shorts Title for title, YT Shorts Description for description.

Scheduling Process

For each valid post:

1. Build the post payload following the exact structure above
2. Send POST /posts to Blotato
3. Capture the returned post submission ID
4. Store the submission ID in the "Blotato ID" property on Notion
5. Set Status to "Scheduled" on Notion
6. Delete local image files (user already approved at Gate 2)

---

Step 3: Verify Publishing

After all posts are scheduled, verify publishing for any posts whose scheduled time has passed.

For posts already past their scheduled time:

1. Poll GET /posts/{blotato_id} for each post
2. Check the response status:

On success (status = "published"):

• Store publicUrl in Notion (Public URL property)
• Set Status to "Published"

On failure (status = "failed"):

• Read errorMessage from response
• Set Status to "Needs Rework"
• Write error message to Rework Notes property

On pending (status = "in-progress"):

• Leave as "Scheduled"
• Report that the post is still in queue

For recently scheduled posts (future scheduled time):

Do not poll yet. Report them as "Scheduled, publishing at {time}".

---

Step 4: Report

Send a summary listing:

1. Scheduled: Which posts were scheduled, on which platforms, at what times
2. Published: Which posts were confirmed live (with public URLs)
3. Failed: Which posts failed and why
4. Skipped: Which posts were skipped and why (missing prerequisites)
5. Pending: Which posts are still in the queue

---

Handling Rework

If a post fails on Blotato:

1. Read the error message
2. If it is a fixable issue (wrong format, missing field): fix and retry
3. If it is a platform issue (account disconnected, rate limit): report to user
4. Set "Needs Rework" with the error in Rework Notes

---

Verification-Only Mode

When the user asks to "verify published posts" or "check post status":

1. Query Calendar for Status = "Scheduled"
2. For each, read the Blotato ID property
3. Poll GET /posts/{blotato_id}
4. Update statuses based on results
5. Report

---

Notion Database

| Database | ID | |---|---| | Social Media Calendar | YOUR_CALENDAR_DB_ID |

---

Related Skills

• content-writer -- creates copy (runs Thu 9am)
• content-designer -- generates images (runs Thu 3pm)
• content-ideation -- fills Topic Bank (runs Wed)
• content-analytics -- measures performance (runs Mon)