SOCIAL MEDIA

Loom teaser with Slack approval gate before scheduling

Generates a captioned vertical teaser from a Loom clip and posts a preview to Slack for one-click approval; only approved clips get scheduled across platforms.

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Loom recording completedLoomLoom
  • ActionRender teaser and draft per-platform copyOpenAI
  • ActionPost preview to Slack approval channelSlack
  • LogicBranch on approve vs reject decision
  • OutputSchedule approved teaser across platformsSocial publishing

What it does

Adds a human checkpoint to short-form publishing. It builds the captioned vertical teaser and proposed copy from a Loom recording, then posts the preview to a Slack channel. Marketing approves or rejects; only approved clips are scheduled.

When to use it

For brands that want automation speed but require a human to sign off before anything goes live. Good for regulated industries or teams burned by an auto-post mistake who still want the grunt work done for them.

How it works

  1. 1A finished Loom recording triggers the flow.
  2. 2A render action cuts a 9:16 teaser with burned-in captions, and OpenAI drafts per-platform copy.
  3. 3The preview clip and copy are posted to a Slack approval channel with approve and reject actions.
  4. 4A logic branch waits on the Slack decision: reject ends the run; approve continues.
  5. 5The post action schedules the approved teaser and copy across the configured platforms.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Connect Social publishingCross-post to X, LinkedIn, Instagram, TikTok, and 4 more in one call.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.