2026-04-20

Automated Publishing — Publish to Multiple Platforms with One Click

Publishing content manually across multiple platforms can take time and introduce unnecessary steps. With Automated Publishing in Reports.re, you can streamline this process and publish content to multiple platforms on autopilot.

By using Task Scenarios, Reports.re allows you to automate publishing once all required content is ready—ensuring consistency, reducing manual work, and helping your content go live at the right time.

1. How Automated Publishing Works

Automated publishing is powered by Task Scenarios, which can define rules for when and how content should be published.

For example, in a card where all required tasks are marked as Ready and the Upload to Platform task already contains:

  • The video
  • The title and description document
  • The thumbnail

By executing a Task Scenario, all publishing tasks are triggered at once. Once executed:

  • The task status updates automatically
  • The post is scheduled for publishing on each connected platform

2. Creating a Task Scenario

To set up automated publishing:

  • Hover over Workspace Settings
  • Navigate to Automation
  • Open Task Scenario Templates
  • Click Create Task Scenario Template

You can then:

  • Add a title to represent the scenario (e.g., Auto Publish)
  • Select Task Operation Content Publisher as the automation type

This scenario will define how publishing is triggered and executed.

3. Defining Task Status Triggers

You can control exactly when the scenario executes:

  • Select specific task statuses that trigger the scenario (the scenario will only run when these statuses are met)
  • If no task status is selected, the scenario will execute regardless of status
  • Define the task status that will be applied after execution (e.g., updating the task status to "Ready" once publishing is triggered)

This ensures automation only runs under the correct conditions.

4. Matching Tasks and Outlets by Tag

You can then require the task and outlet to share the same tag category.

For example:

  • Set the tag category to Language Version
  • The scenario will only execute if both the task and outlet share the same language tag

This prevents content from being published to the wrong outlet.

5. Controlling Publishing Time Slots

Next, configure how publishing slots are handled:

  • Skip publishing slots within a specified number of minutes after execution
  • The post will be scheduled for the first available slot after that time

For example:

  • If set to 0 minutes, publishing uses the earliest available slot
  • If set to 15 minutes and the scenario runs at 10:00 AM, slots before 10:15 AM are skipped

This ensures proper spacing between execution and publishing.

6. Optional Execution Conditions

You can then add optional conditions to better match your workflow:

Require the scenario to wait for:

  • A video file
  • A post document (title and description)
  • An image (thumbnail)

Execute the scenario automatically when:

  • An outlet is added to the card
  • A file is added to a task where the scenario is assigned

These conditions allow the scenario to run only when all required assets are ready.

7. Matching Files and Outlets by Tag

Next, apply tag-matching logic to individual assets:

  • Require the video and outlet to share the same tag category
  • Require the text document and outlet to share the same tag category
  • Require the thumbnail and outlet to share the same tag category

You can also:

  • Allow items without tags to be published using applicable tags from the category
  • Reuse data from previously published posts based on tag categories if needed. This option is optional and not required for this guide or video, as all necessary content (video, text document, and thumbnail) is prepared in advance.

This ensures accurate and consistent publishing across platforms.

8. Using Regular Publishing Schedules based on tag matching

You can publish content using Regular Schedule slots that are linked to specific tag categories.

This is especially useful when:

  • Different types of content follow different publishing schedules
  • Tags such as Travel or Promotions determine when and where content goes live

With tag-based matching enabled, Reports.re automatically applies the appropriate schedule, ensuring each post is published at the right time without manual selection.

9. Saving and Executing the Scenario

Once everything is configured:

  • Click Add to save the scenario
  • Got to a task and hover over the Scenario icon
  • Select the Auto Publish scenario
  • Click the Execute icon to run it

After execution:

  • The task status updates
  • The post is scheduled according to the Regular Schedule

Conclusion

With Task Scenarios, Reports.re enables fully automated publishing across multiple platforms. By reducing manual steps, enforcing consistency through tags, and integrating scheduling logic, automated publishing ensures your content goes live efficiently and at the right time—every time.