Workflows

HotMic gives customers full control over how content moves from creation to publication. Build workflows that match how your team operates, from how content moves through review and approval to how finished content reaches your CMS, app, or downstream services.

Workflows in HotMic operate across two layers: a front-end layer where producers, programmers, and admins manage content through user-facing tools, and a back-end layer where HotMic integrates with the rest of your stack through webhooks and APIs.

Front-End Workflows

Front-end user workflows are managed inside HotMic through two purpose-built workspaces:

• Clip Manager — Where producers, programmers, and admins review, approve, and route recordings, uploads, and clips on their way to publishing.
• Stream Manager — Where producers, programmers, and admins manage live streams — coordinating shows, delivering graphics, moderating, and running interactive features in real time.

Together, Clip Manager and Stream Manager give your team a single set of tools for managing every piece of content from inside HotMic.

Back-End Workflows

Back-end workflows connect HotMic to the rest of your stack — CMS, analytics, internal services, and any downstream system. They are powered by two integration layers:

• Webhooks — Subscribe to platform events (stream started, recording completed, clip approved, content published, and more) and receive real-time notifications at any endpoint you control. Use webhooks to trigger CMS imports, fire analytics events, alert internal Slack channels, or sync content state with your backend.
• APIs — Programmatically create streams, fetch content metadata, manage users, retrieve analytics, and push or pull assets from your CMS. The API mirrors what's available in the Creator Studio so any manual workflow can be automated.

Common Workflow Examples

• Auto-publish approved clips into your CMS once they exit the Clip Manager.
• Trigger an external moderation review when a recording reaches Pending Review.
• Sync stream schedules with your editorial calendar.
• Push analytics into your data warehouse for unified reporting.

Configuration

Workflows are configured per organization, so different teams can operate with different routing rules, approval steps, and destinations across both the front-end and back-end layers.