Social Post AI workflow template: Three hooks, you pick, it ships.

The ConvOps Social Post template makes your AI turn a brief into a ready-to-publish post: capture platform, audience, core message, proof and call to action, write three variants with different hook angles, then polish the one you pick. It stops once, before publishing. Reject it and the AI drafts new variants.

4 steps · 1 approval · 1 loop back

Social Post · example runyour AI client
  1. 01Brief
  2. 02Draft Variants
  3. 03Polishwaits for approval
  4. 04Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Social Post template do?

For founders and marketers posting on LinkedIn, X or other platforms who want options, not one take.

Social Post is stored in ConvOps as four steps, and your AI client receives them one at a time. A Social Post run holds at Polish until an explicit approval is given.

  • Announce a feature on LinkedIn with three hook options to choose from
  • Turn a blog post into a short, on-brand social post
  • Draft a post about a customer win and polish it before it goes out
step by step

How does the Social Post workflow run?

The 4 Social Post steps in order, each with the instruction your AI receives there as Social Post stores it.

Brief
Draft Variants
Polishapproval
Completeclosing note

One approved post for one platform, chosen from three variants with different hooks and polished before approval.

  1. 01

    Brief

    the agent works

    Establish the brief for this post. Do not draft yet.

    Capture, in plain prose:

    • Platform: LinkedIn, X, or another, since format and length differ
    • Audience: who you are speaking to and what they care about
    • Core message: the single idea in one sentence
    • Proof or specific: a number, example, or detail that earns trust
    • Call to action: comment, click, follow, or none by design
    • Any link to include

    If the core message is fuzzy, ask the operator before advancing: a vague message produces a forgettable post.

    Save the full brief as a task note with task_notes_add. The next step (Draft Variants) reads this note.

  2. 02

    Draft Variants

    the agent works

    Read the task notes with task_notes_list: the note from the Brief step contains platform, audience, message, proof, and CTA. Work from it.

    Write three distinct variants of the post. What good looks like:

    • Each opens with a different hook angle (question, bold claim, story, stat): not three rewrites of the same line
    • Each fits the platform's length and tone
    • Each carries the core message and the proof point
    • Each ends with the CTA from the brief

    Label them Variant A, B, C so the operator can pick.

    Save all three variants as a task note with task_notes_add. The Polish step reads this note and the operator's choice.

  3. 03

    Polish

    waits for your approval

    Read the task notes with task_notes_list: the note from the Draft Variants step contains Variant A, B, and C. Work from it.

    Ask the operator which variant to run with. Polish the chosen one: tighten the hook, fix any awkward phrasing, confirm the link and CTA, check it reads well on the target platform.

    Save the final polished post as a task note with task_notes_add. Then ask the operator to approve it for publishing. This is a checkpoint: publishing is the irreversible moment, so the AI cannot advance until you approve. If you reject, the workflow returns to Draft Variants.

    rejected → back to Draft Variants

  4. 04

    Complete

    closes with a note

    The post is approved and ready to publish. Confirm the final post is saved as a task note, then close out the task.

reach for it when

  • You want options to choose from, not a single take.
  • The post has one platform, one message and one call to action.
  • Nobody should post before seeing the final text.

something else fits when

  • You need a version for several channels at once: Content Repurpose.
  • The message is long enough to be an article.
  • It is a live reply inside a thread.
example · university admissionsenterprise

An open-day announcement on LinkedIn

The agent writes a question hook, a story hook and a statistic hook. The admissions officer picks the story, the agent polishes it, and the post is approved for publishing.

Polish approval

where approval is required

Where do you approve in Social Post?

Social Post holds at Polish until an explicit approval is given, recorded with the account that gave it.

step 3

Polish

You choose the variant, the AI polishes it, and you approve before it is published. Reject it and the workflow returns to Draft Variants.

reject → back to Draft Variants

gates the engine checks without you

  • Complete closes Social Post only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Social Post?

make it yours

How do you customize Social Post?

Once installed, Social Post is a workflow in your workspace. Ask your AI to change Social Post in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

Always write four variants, and make one of them a short story.
workflow_step_update · Social Post
Done. Social Post in your workspace now has the change, and every new run follows it.

more example prompts

  • "Always write four variants, and make one of them a short story."
  • "In Brief, default the platform to LinkedIn."
  • "After Complete, add a step that schedules the post in our tool."
the difference

Social Post: without a workflow vs with it

  • You stare at a blank post box and ship the first line that comes to mind
  • The post goes out the moment it is written, typo and all, with no second look
  • You start a post on your phone, switch tasks, and lose the variants you liked
  • Nobody can tell which version went out or why that angle was picked over the others
  • The Social Post process lives in a prompt, and each run follows it a little differently
  • The AI drives a few distinct variants so you choose the strongest hook instead of settling
  • The AI pauses at a Polish checkpoint so you sign off before anything is published
  • The AI saves the variants as a note, so you reopen the chat later and the options are still there
  • Every step (Brief, Variants, Polish) is logged, so the record of what shipped and why is already there
  • Your AI receives the 4 stored steps one at a time, and the run holds at Polish until an explicit approval is given
questions

Social Post template FAQ

What is the ConvOps Social Post template?

The ConvOps Social Post template makes your AI turn a brief into a ready-to-publish post: capture platform, audience, core message, proof and call to action, write three variants with different hook angles, then polish the one you pick. It stops once, before publishing. Reject it and the AI drafts new variants.

How different are the three variants?

In ConvOps, the Draft Variants step writes Variant A, B and C, each opening with a different hook angle (question, bold claim, story or stat), not three rewrites of one line. Each fits the platform's length and tone and carries the core message, the proof point and the call to action from the brief, so you pick between real alternatives.

Which platforms does it support?

Any. The ConvOps Brief step records the platform (LinkedIn, X or another) because format and length differ, along with the audience, the core message, a proof point, the call to action and any link. The variants are written to fit that platform, and Polish checks the chosen one reads well there before it goes up for approval.

Can it start from a blog post?

Yes. In ConvOps, the post can serve as the brief: its core message and proof point go straight into the Brief step. For several channels at once, use the Content Repurpose template, which turns one source into a version per channel, each with its own approved angle. Both ship in the Content Studio kit with Blog Post and Newsletter Issue.

What happens at Polish?

At the ConvOps Polish step your AI asks which variant to run with, then tightens the hook, fixes awkward phrasing, confirms the link and call to action, and checks the post reads well on the target platform. The final post is saved as a task note, and the run holds until an explicit approval is given. Reject it and it returns to Draft Variants.