# AI Post Rewrites and CTA Rotation for a Content Team

> Two n8n workflows that rewrite a social post when a reviewer ticks Redo, and add the best call-to-action to each thread from a rotating library.

Section: n8n Automations

Page: https://mburhan.com/case/n8n-social-post-redo-and-cta-rotation

## Project Overview

This project uses two n8n workflows to improve a content team's social media review and publishing preparation process. Drafts for X, LinkedIn, and Threads are stored in Airtable, where reviewers can request revisions and manage content before approval.

The first workflow, **Redo**, rewrites posts when a reviewer provides feedback and checks the Redo box. Claude applies the requested changes while preserving the existing content that does not need revision.

The second workflow, **CTA Auto-Insert**, selects suitable calls to action from an Airtable library, arranges them within a social thread, and tracks usage to help balance CTA rotation.

Both workflows use a shared Claude sub-workflow and retrieve their writing rules, playbook, and CTA configuration from Airtable. This allows the team to adjust content standards and CTA selection without editing the main n8n workflows.

**Technology stack:** n8n, Airtable, Claude, X, LinkedIn, Threads.

## 01. The Business Problem: Revisions and CTAs Require Consistent Handling

Social media drafts often need several rounds of review before they are ready. Reviewers may request specific changes, but applying feedback across multiple platform formats can be time-consuming and may unintentionally alter content that was already correct.

Calls to action create another challenge. A team may maintain several CTAs for different topics, campaigns, and audiences. Selecting them manually can lead to repetitive links, inconsistent placement, and excessive use of the same CTA.

The main challenges were:

- **Manual revision work:** Reviewer feedback must be applied consistently across multiple social platforms.
- **Content consistency:** Existing facts, approved wording, and account-specific voice rules must be preserved.
- **Platform-specific formatting:** X, LinkedIn, and Threads require different content lengths and formatting.
- **CTA repetition:** Frequently used CTAs can become overused if rotation is not managed.
- **Changing content rules:** Writing standards and CTA preferences need to remain editable without modifying workflow logic.
- **Duplicate processing:** A card should not be rewritten or assigned a CTA repeatedly after its task has been completed.

The objective was to automate these repetitive tasks while retaining reviewer control and clear records of each content change.

## 02. The Solution: Two Connected Content Workflows

### Workflow 1: Redo — AI-Powered Post Rewriting

The Redo workflow checks Airtable for cards where the reviewer has selected the Redo checkbox and provided source text.

A dispatcher can start the workflow, while an hourly scheduled run catches requests that may have been missed.

The workflow retrieves the current Post Rules and Craft Playbook from Airtable and sends Claude the original source, previous draft, and reviewer feedback. Claude produces revised versions for X, LinkedIn, and Threads, following the required platform formats and account voice.

A cleanup step removes unwanted hedging language, applies image-credit rules, and prepares the output for review. n8n then writes the revised posts back to Airtable, clears the Redo checkbox, and changes the card status to `Pending Review`.

The original feedback remains on the card for reference.

### Workflow 2: CTA Auto-Insert — Automated CTA Selection and Rotation

The CTA workflow searches Airtable every two minutes for draft cards that do not yet have a linked CTA.

It retrieves active CTA records, filters out those that have reached their usage caps, and ranks the remaining options using weight, conversions, and previous usage.

Claude receives the post, its source material, and the ranked CTA list. It selects a primary CTA and, when appropriate, a different secondary CTA based on topic relevance and each CTA's usage notes.

The workflow builds the thread with the primary CTA as the first reply and the secondary CTA at the end. It then saves the thread, links the primary CTA record to the card, and increments the usage counters.

**Operational status:** The Redo workflow is live. CTA Auto-Insert is switched off in the current version because running every two minutes would use approximately 21,600 executions per month.

## 03. Project Snapshot

| Item | Detail |
| --- | --- |
| Platform | n8n |
| Content database | Airtable |
| AI writing and selection | Claude |
| Supported platforms | X, LinkedIn, Threads |
| Main workflows | Redo and CTA Auto-Insert |
| Shared component | Claude writing sub-workflow |
| Writing configuration | Post Rules and Craft Playbook in Airtable |
| CTA configuration | Airtable CTA library |
| Redo trigger | Dispatcher plus hourly scheduled check |
| CTA trigger | Every two minutes in the configured workflow |
| Redo status | Live |
| CTA Auto-Insert status | Switched off in the current version |
| Duplicate prevention | Redo checkbox reset; CTA record linked to card |

## 04. How Workflow 1 Works: Redo

### Step 1: Identify Revision Requests

The workflow searches Airtable for cards with Redo enabled and source text available.

Requests can be started through a dispatcher, while the hourly run catches cards that were not processed by the initial trigger.

### Step 2: Load Current Writing Rules

The workflow retrieves the Post Rules and Craft Playbook from a settings record in Airtable.

These settings define the account's writing style and content requirements, allowing the team to update its standards centrally.

### Step 3: Send Context and Feedback to Claude

Claude receives three inputs:

- The original source material.
- The previous draft.
- The reviewer's feedback.

The model is instructed to apply the requested changes while retaining content that the reviewer did not ask to change.

It returns three platform-specific drafts:

| Platform | Required format |
| --- | --- |
| X | Revised X post |
| LinkedIn | 600–1,100 characters |
| Threads | Approximately 420 characters, with a maximum of 500, ending on a complete sentence |

### Step 4: Clean and Validate the Drafts

A cleanup step removes hedging lines such as “the source does not establish…” and applies the required image-credit formatting.

The “shared by a publisher” credit line is retained only for posts containing an image and is moved to the final line.

The prompt also enforces factual accuracy, quotation requirements, and account-specific voice rules.

### Step 5: Update Airtable for Review

n8n writes all three revised drafts back to the Airtable card, unticks Redo, and sets the status to `Pending Review`.

Clearing the checkbox prevents the same revision request from being processed repeatedly, while retaining the feedback provides an audit trail for the reviewer.

## 05. How Workflow 2 Works: CTA Auto-Insert

### Step 1: Find Drafts Without a CTA

The workflow checks Airtable every two minutes for draft cards that do not have a CTA linked yet.

Once a CTA is linked, the card no longer matches the search criteria, preventing it from being processed again.

### Step 2: Retrieve the CTA Library

The workflow reads active CTA records from Airtable. Each record can include:

- CTA text and link.
- Category.
- Weight.
- Times used.
- Conversions.
- Weekly usage cap.
- A “use when” note describing the appropriate context.

This makes CTA selection configurable without changing the n8n workflow.

### Step 3: Filter and Rank CTA Options

A code step removes CTAs that have reached their usage caps and scores the remaining candidates.

The ranking formula uses the following rules:

- Each CTA's weight counts double.
- Each conversion adds half a point.
- Each previous use subtracts one point.

The remaining candidates are sorted from highest to lowest score.

This ranking helps balance relevance, performance, and usage frequency. Claude still considers the topic and each CTA's usage notes before making its final selection.

### Step 4: Ask Claude to Select the CTAs

Claude receives the post, its source material, and the ranked CTA options.

It selects a primary CTA that fits the topic and a different secondary CTA when appropriate. When two candidates are equally suitable, the higher-ranked option is preferred.

The generated reply follows the account's voice, and CTA links must remain exactly as stored in Airtable.

### Step 5: Assemble and Save the Thread

The workflow builds the thread in this order:

1. Lead post.
2. Primary CTA as the first reply.
3. Remaining thread content.
4. Secondary CTA at the end, when selected.

Each part is numbered sequentially, such as `1/`, `2/`, and so on.

n8n saves the completed thread to Airtable and links the primary CTA record to the card. It then increments the Times Used counter for the primary CTA and, when a secondary CTA is included, the secondary CTA as well.

## 06. Workflow Architecture

### Redo workflow

Image (https://mburhan.com/uploads/2b20d2ee118a67e5f7bdb10a.png)

### CTA Auto-Insert workflow

Image (https://mburhan.com/uploads/a69d46969575084a02393736.png)

Both workflows share the same Airtable content base and Claude writing sub-workflow. This reduces duplicated writing logic and helps maintain consistent content-generation behavior.

### n8n Work Flow

Image: Together, the workflows demonstrate how n8n, Airtable, and Claude can automate repetitive content operations while retaining configurable rules, traceable reviewer feedback, and human approval. (https://mburhan.com/uploads/17853f24b5fb8b0133866532.png)

## 07. AI Writing Rules and Content Safeguards

The Redo workflow is designed to apply feedback without introducing unsupported information or changing unrelated content.

### Factual Accuracy

- Use facts contained in the source material or previous draft.
- Never invent numbers, dates, figures, or view counts.
- Return the complete revised post rather than a list of suggested changes.

### Quotation Handling

If the reviewer requests a quote, the publisher's own words must remain verbatim and enclosed in quotation marks. Any interpretation or analysis must be written separately after the quotation.

### Voice and Formatting

The workflow follows the account's voice rules, including a list of banned words and AI-sounding phrases.

It also applies platform-specific length requirements and cleans up unwanted hedging language before writing the drafts back to Airtable.

### CTA Controls

CTA Auto-Insert filters out options that have reached their usage caps, uses a ranking system to guide selection, and preserves stored CTA links exactly.

The primary and secondary CTAs are intended to be different, helping reduce repetitive calls to action within the same thread.

These controls guide the output but do not replace a human review of factual accuracy, tone, and suitability.

## 08. Airtable as the Content Control Center

Airtable stores the drafts, review feedback, writing settings, and CTA library used by both workflows.

| Component | Purpose |
| --- | --- |
| Content cards | Store source material and platform-specific drafts. |
| Redo checkbox | Signals that a reviewer wants the drafts rewritten. |
| Feedback field | Captures the changes requested by the reviewer. |
| Post Rules | Defines the account's content requirements. |
| Craft Playbook | Provides the broader writing guidance. |
| CTA library | Stores CTA text, links, categories, scores, usage caps, conversions, and context notes. |
| Linked CTA field | Identifies the CTA assigned to a card and prevents repeated processing. |
| Times Used counter | Tracks CTA usage for rotation. |

Centralizing these settings allows the team to modify its writing guidance and CTA options without editing the underlying workflow.

## 09. Results and Operational Status

The project description confirms that the Redo workflow is live and the CTA workflow is configured but switched off in the current version.

No measured figures were provided for hours saved, revision turnaround, approval rates, engagement improvements, or CTA conversion uplift.

### Implemented Capabilities

- Reviewer-triggered AI rewriting.
- Hourly recovery checks for missed Redo requests.
- Platform-specific drafts for X, LinkedIn, and Threads.
- Centralized writing rules and playbook settings.
- Preservation of source facts and reviewer feedback.
- Cleanup of unwanted hedging language.
- Image-credit formatting rules.
- CTA filtering and weighted ranking.
- Primary and secondary CTA placement.
- Airtable-based usage tracking and duplicate prevention.

### Important Operational Consideration

The CTA workflow is switched off because its two-minute schedule would generate approximately 21,600 executions per month. Before enabling it, the team should evaluate a less frequent schedule or event-based triggering to reduce execution consumption.

### Metrics to Measure Next

- Average time from reviewer feedback to revised drafts.
- Percentage of rewritten drafts approved without another revision.
- Frequency of unsupported facts or formatting corrections.
- CTA processing volume and execution consumption.
- CTA usage distribution and weekly-cap enforcement.
- Click-through and conversion performance of approved CTAs.

## 10. Key Takeaways

- **Automate targeted revisions:** Reviewers can request changes through Airtable without manually rewriting every platform version.
- **Preserve existing content:** Claude receives the source, previous draft, and specific feedback so unrelated content can remain unchanged.
- **Centralize writing standards:** Post Rules and the Craft Playbook are editable in Airtable.
- **Make CTA rotation data-driven:** Ranking uses weight, conversions, and usage history, while Claude considers contextual relevance.
- **Prevent duplicate processing:** Clearing Redo and linking a CTA give each workflow a clear completion condition.
- **Consider execution costs:** Frequent scheduled checks should be balanced against operational needs and n8n execution limits.
- **Keep human review in the loop:** Rewritten drafts return to `Pending Review` rather than being published automatically.

## 11. Future Development

- Evaluate event-based triggering or a longer polling interval for CTA Auto-Insert.
- Measure the quality and approval rate of AI-rewritten drafts.
- Track CTA click-through and conversion performance to validate the ranking method.
- Add monitoring for cards that remain in Redo status after repeated failures.
- Review whether the scoring weights should be adjusted based on actual campaign outcomes.
- Add reporting on CTA usage, weekly caps, and the distribution of primary and secondary CTAs.

## 12. Final Outcome

The project establishes a shared content-automation foundation for reviewer-requested rewrites and CTA management.

The live Redo workflow applies feedback to platform-specific drafts, enforces account writing rules, and returns revised content to Airtable for review. The separate CTA Auto-Insert workflow provides a configurable method for ranking and placing CTAs while tracking usage.
