Content workflow automations you can copy to stop repeating the same manual work

Start with the automations that remove real production bottlenecks

Each recipe below removes a handoff that usually waits on someone remembering: drafting posts after approval, acting on a finished transcript, or keeping trial content out of the main-feed queue. Every recipe gives you the trigger, conditions, and actions to build in Organization settings → Automations. If you have not set one up before, read How Automations Work first.

Every recipe assumes you have at least one agent. See AI Agents.

---

Recipe 1: Draft a post for every platform when media is approved

The workhorse. This is the automation Clipflow builds for you when you connect your first channel, written out so you can rebuild or extend it.

Trigger: a media file’s status was updated

Condition: media status equals approved

Actions: one per channel and post type you publish to.

For each action:

1. Choose your drafting agent.

2. Allow the Create Post tool.

3. In the tool settings, set the Platform Product, for example Instagram Reel. This is the field that decides what kind of post gets drafted.

4. Leave Channel empty to use the organization’s channel for that platform, or pick one explicitly.

5. Set a title template so drafts are easy to scan, such as {{ title }} - Instagram Reel.

6. Turn on Skip if Media In Use so re-approving a file does not create a second draft.

7. Write the instruction, for example:

   Write a caption for this reel. Two short lines, no hashtags, no emoji. End with a question.

Duplicate the action for the next platform and change the Platform Product and instruction. Six actions covering Instagram, TikTok, YouTube, LinkedIn and Facebook is normal.

---

Recipe 2: Split feed posts from trial posts

Useful once you are testing content before it hits the main feed. Without this, one approval drafts both a trial post and a feed post whether you wanted both or not.

Setup first: create a Content Type label group under Organization settings → Labels with feed and trial options, then label your projects.

Trigger: a media file’s status was updated

Condition: media status equals approved

Actions:

• Trial action: Create Post with Platform Product set to Instagram Trial Reel, and an action condition of content type equals trial.
• Feed actions: Create Post targeting Instagram Reel, YouTube Short, and TikTok, each with an action condition of content type equals feed.

Turn on Skip if Media In Use on every one of them. Approving the same clip twice is common when a client changes their mind, and without it you get a duplicate draft each time.

Conditions on the action rather than the automation are what make this work. The automation still fires for every approval, and each action decides whether it applies.

The full publishing side of this is in Bulk Schedule Instagram Trial Reels.

---

Recipe 3: Summarise a transcript when it finishes

Turn a long interview into something skimmable without anyone watching it back.

Trigger: a media file’s transcription finished

Conditions: none, or narrow it to one project category.

Action:

1. Choose a researcher or producer agent.

2. Allow Project Overview so it can read the project. No Create Post tool.

3. Instruction:

   Summarise this transcript in under 200 words, then list the five strongest standalone moments with a one-line description of each.

The reply lands as a comment on the file, so the editor and the strategist see it in the same place they are already working. See Transcription.

---

Recipe 4: Suggest hooks when new media lands

Trigger: a new media file was added

Condition: none, or media type equals edited video so raw footage does not trigger it.

Action:

1. Choose a scriptwriter agent.

2. Allow the Hook Generator tool and Project Overview.

3. Instruction:

   Give five hook options for this video based on the project outline. Keep each under twelve words.

---

Recipe 5: Answer questions raised in comments

Trigger: a new comment was posted

Conditions: narrow this one. Without a condition it reacts to every comment in the organization, which gets noisy fast. Scope it to a project category or a label your team uses for questions.

Action: an agent with Project Overview and an instruction telling it to answer only when the comment is a question about the project.

For most teams, mentioning an agent by name in a comment is the better tool here. Reach for this recipe only when you want a reply without anyone remembering to ask.

---

Tips for building your own

• Start with the narrowest condition you can. Loosen it once you trust the output. Automations that do too much get switched off, and then nothing is automated.
• Test on one project. Label a test project, add that label as a condition, and run it for real before removing the condition.
• Read the runs. Each action records what the agent did. When output is wrong, the run usually shows whether the instruction or the tool settings caused it.
• One job per action. If an instruction contains the word “and” twice, it is probably two actions.

---

Frequently asked questions

---

Related articles

• How Automations Work: triggers, conditions, and actions
• AI Agents: build the agent that runs these
• Bulk Schedule Instagram Trial Reels: recipe 2 in full