Skip to main content

Publishing Overview

Publishing in Influgen is a separate system from generation. That distinction is important. You can generate content today, approve it tomorrow, and publish it next week without losing state or rebuilding the asset.

The publishing flow​

For a post to go live, Influgen moves through four stages:

  1. Generate the content item.
  2. Approve the content item or let autopilot approve it.
  3. Create a scheduled post entry for one or more platforms.
  4. Publish at the scheduled time or trigger publish-now manually.

Each scheduled post has its own platform, media payload, caption selection, and status.

Publishing statuses​

Scheduled posts move through:

  • pending
  • published
  • failed
  • cancelled

Failures also carry an error code so you can tell whether the problem is credentials, rate limiting, or something else. The current error set includes:

  • token_expired
  • rate_limited
  • content_rejected
  • network_error
  • unknown_error

[screenshot: Publishing dashboard with per-platform connection cards and a schedule table showing pending, published, and failed posts]

Content adaptation per platform​

Influgen does not publish the same payload blindly everywhere. Before a scheduled post is sent, the publishing manager adapts it for the destination.

Examples:

  • Instagram can publish images, carousels, stories, and reels.
  • TikTok and YouTube expect video-ready assets.
  • X and Pinterest use image-first payloads and support carousels.

This matters because one approved content item may still need platform-specific caption and media shaping before it can publish cleanly.

What happens when something fails​

Influgen treats retryable and non-retryable failures differently:

  • retryable issues such as some rate limits or network problems can stay pending and get a future attempt time
  • non-retryable issues move the scheduled post to failed

If a token is expired, the content item can remain approved so you can reconnect the platform and resume publishing without regenerating the asset.

Best practices​

  • Keep publishing accounts connected before you batch-schedule a week.
  • Approve content before scheduling unless the character is already stable enough for autopilot.
  • Review platform-specific output, especially when repurposing the same asset across several channels.
  • Reconnect expired tokens from Settings instead of deleting and recreating content.

For platform-specific setup, continue with the guides below.