Scheduled Task Content Workflow: Generate, Review, and Publish as Planned

Scheduled Automatic Publishing

Studio scheduled tasks can attempt to generate content and call authorized Skills according to a schedule. It is suitable for regularly executing processes that have already been manually verified, but it does not guarantee a "set it once and it will succeed forever" publication.

The task results depend on the model, balance, connection status, credential validity, Skill permissions, target platform availability, review, and risk control. First, save drafts, regularly check the running history, and maintain manual review and deactivation mechanisms.

1. Entry and Task Composition

Enter Studio Scheduled Tasks, create a new task, and configure:

  • Name and execution schedule;
  • Fixed model and prompt;
  • Allowed Skills and MCP;
  • Unattended allowed list;
  • Enabled status and running history.

Scheduled Task List

2. Why Configure the Allowed List

When the scheduled task runs, there is no one present to confirm each step, so not all external capabilities are loaded by default. It is necessary to explicitly allow the Skills and MCP that this task will use:

{
  "name": "Weekly Technical Content Draft",
  "schedule": {
    "type": "cron",
    "value": "0 9 * * 1"
  },
  "template": {
    "model": "gpt-5.5",
    "question": "Generate a technical draft based on the verified product updates of this week",
    "skills": ["juejin"],
    "mcp_servers": ["openai"]
  },
  "unattended_policy": {
    "allowed_skills": ["juejin"],
    "allowed_mcp_servers": ["openai"]
  }
}

If the running history shows skill_not_active, check whether the Skill is connected and included in allowed_skills; image generation capabilities also need to be included in the allowed MCP list.

Scheduled Task Edit

3. Validate Manually First, Then Set the Schedule

  1. Connect to the target platform according to Connector Overview;
  2. Manually execute the same prompt in a normal conversation;
  3. Verify facts, links, images, formats, and platform rules;
  4. Prioritize confirming that the draft can be successfully saved;
  5. Then create a low-frequency scheduled task and first "run it immediately";
  6. Check the final state and actual results on the target platform in the running history.

Do not assume that the content has been published just because the task shows "completed." Some Skills only save drafts, and some platforms may require confirmation, verification codes, or reviews.

4. A Conservative Example of Technical Content

The prompt can start from generating a draft:

Based on the verified AI product updates of this week, choose a suitable topic for developers:

1. Only cite verifiable public information;
2. Write a technical draft of 800–1200 words, including a reproducible small example;
3. Generate a cover image that does not contain brand misleading or false text;
4. Keep my invitation link placeholder at the end;
5. Save to the target platform's draft box, not publish directly;
6. Return the draft title, link, and facts that need my review.

First, observe the quality and stability with a weekly frequency. After manual review stabilizes, decide whether to allow direct publishing based on platform capabilities.

5. Regular Checks

After Each Run

  • Whether a draft or published content was genuinely generated;
  • Whether there are errors in facts, code, links, or images;
  • Whether it triggered reviews, rate limits, or account alerts;
  • Whether it incurred expected quota consumption.

Weekly

  • Check credential and account status;
  • Review failure reasons and correct prompts;
  • Delete duplicate, low-quality, or outdated tasks;
  • Confirm that the publishing frequency complies with target platform rules.

If there are consecutive failures, declining content quality, or account risk alerts, the task should be immediately deactivated, and automatic retries should not be used to spam.

6. Scenarios Not Suitable for Unattended Operation

  • Platforms that require a local browser online, verification codes, or on-site confirmation;
  • Content involving news, prices, policies, or other easily changeable facts;
  • Using customer data, unpublished information, or copyrighted materials;
  • High-frequency cross-platform duplication of the same content;
  • New Skills that have not undergone a complete manual verification.

Processes like Xiaohongshu that require a local browser are more suitable for triggering by a person in front of a computer. Specific restrictions can be found in the corresponding channel tutorials.

Next Steps