Newsletter production from content sources to distribution

Introduction

You've spent hours curating content, writing thoughtful analysis, and now you need to distribute it to your audience. The problem is that each platform demands a different format: your email newsletter needs a clean layout, your blog post requires SEO optimisation, and your social channels want punchy summaries. Right now, you're probably copying text between tabs, reformatting by hand, and uploading each version separately. It's repetitive work that consumes an afternoon every week.

What if you could feed a single content source into a system that automatically rewrites it for your newsletter, summarises it for your blog, and pulls quotes for social media? Then it publishes everything to your distribution channels without touching it again. That's what this workflow does.

This Alchemy recipe connects three AI tools through a no-code orchestrator so that content flows from your source, through multiple processing stages, and out to your audience automatically. You'll use Copy.AI to generate newsletter variants, Resoomer to distil content into summaries, and Widify to format images and social assets. The entire pipeline runs once you trigger it, with zero manual handoff between stages.

The Automated Workflow

Which Orchestration Tool to Use

For this workflow, Zapier is the easiest starting point if you've never built automation before. It has the most straightforward UI and the deepest integrations with these three AI tools out of the box. If you need more control over data transformation or want to run this on your own infrastructure, n8n or Make work equally well and cost far less at scale.

This guide shows Zapier syntax because it's widely accessible, but I'll note where n8n differs significantly.

The Five-Step Pipeline

The workflow operates like this: content arrives at your chosen source (RSS feed, email, or webhook), Copy.AI generates three newsletter variations, Resoomer condenses one variation into a blog summary, Widify creates social media graphics, and finally everything publishes to your newsletter platform and blog.

Let's build this step by step.

Step 1: Trigger on New Content

Your automation needs a starting point. The most reliable approach is an RSS feed trigger, which checks for new content at regular intervals. If you're publishing to a blog already, use that feed. If content comes from multiple sources, create a feed aggregator first (Feedly or Zapier's built-in feed tools work fine).

In Zapier, set up a trigger like this:

Copy
Trigger: RSS by Zapier
Feed URL: https://yourblog.com/feed
Check every: 15 minutes

The trigger extracts these fields from each new post:

• Title
• Description (excerpt)
• Full content
• Publication date
• Author

If you're using n8n instead, use the RSS Read node:

Copy{
  "nodeType": "n8n-nodes-base.rss",
  "parameters": {
    "url": "https://yourblog.com/feed",
    "pollInterval": 15
  }
}

Step 2: Generate Newsletter Variations with Copy.AI

Copy.AI's API endpoint /generate creates content variants based on a prompt. You'll send the original article and ask for three different newsletter styles: professional, conversational, and summary-heavy.

First, get your Copy.AI API key from the dashboard and store it in your orchestrator as an environment variable.

In Zapier, add three separate API call actions (one for each variation). Here's the first one:

Copy
Action: Webhooks by Zapier
Method: POST
URL: https://api.copy.ai/generate
Authentication: Bearer Token
Token: [Your Copy.AI API Key]

Body (JSON):
{
  "prompt": "Rewrite this article for a professional B2B newsletter. Keep it under 200 words and include a clear call-to-action.",
  "content": "{{content from RSS trigger}}",
  "tone": "professional",
  "max_tokens": 300
}

Copy.AI returns a JSON response:

Copy{
  "generated_text": "After careful analysis of current market trends...",
  "tokens_used": 145,
  "finish_reason": "stop"
}

Store this response in a variable called newsletter_variation_1. Repeat the process twice more with different prompts: one for a conversational tone ("Write this as if you're chatting with a friend") and one for an executive summary tone ("Summarise the key takeaway in 100 words").

In n8n, you'd use the HTTP Request node:

Copy{
  "nodeType": "n8n-nodes-base.httpRequest",
  "parameters": {
    "url": "https://api.copy.ai/generate",
    "method": "POST",
    "headerParameters": {
      "Authorization": "Bearer {{$env.COPYAI_API_KEY}}"
    },
    "bodyType": "json",
    "bodyParameters": {
      "prompt": "Rewrite this article for a professional B2B newsletter...",
      "content": "{{$node['RSS'].json['content']}}",
      "tone": "professional",
      "max_tokens": 300
    }
  }
}

Step 3: Summarise with Resoomer

Resoomer's strength is distilling long content into concise summaries. You'll feed one of your newsletter variations into Resoomer to create a blog summary snippet.

Resoomer works via API, though it's less well documented than Copy.AI. The endpoint is /api/summarize:

Copy
Action: Webhooks by Zapier
Method: POST
URL: https://api.resoomer.com/api/summarize
Authentication: API Key
Key: [Your Resoomer API Key]

Body (JSON):
{
  "text": "{{newsletter_variation_1}}",
  "type": "summarization",
  "language": "en",
  "percentToKeep": 30
}

Resoomer returns the condensed version:

Copy{
  "summary": "The article explores market shifts in Q4...",
  "originalLength": 450,
  "summaryLength": 135,
  "ratio": 0.30
}

Store the summary in blog_summary.

Step 4: Create Social Graphics with Widify

Widify generates branded social media images from text. You'll use it to create a quote graphic from your article.

Widify's API is straightforward. Send text and a template ID, get back an image URL.

Copy
Action: Webhooks by Zapier
Method: POST
URL: https://api.widify.com/generate
Authentication: Bearer Token
Token: [Your Widify API Key]

Body (JSON):
{
  "template_id": "quote_card_blue",
  "text": "Extract a compelling quote from {{article content}} in 15 words or less",
  "branding": {
    "logo_url": "https://yourbrand.com/logo.png",
    "brand_colour": "#2E5BFF",
    "font": "inter"
  },
  "format": "instagram"
}

Widify returns:

Copy{
  "image_url": "https://cdn.widify.com/images/abc123.png",
  "format": "1080x1080",
  "expires_at": "2024-02-15T12:00:00Z"
}

Store this as social_image_url.

Step 5: Publish to Distribution Channels

Now everything goes out. You'll send the professional newsletter variation to your email platform, the summary to your blog platform, and the social image to Buffer or similar.

For email (using Mailchimp as an example):

Copy
Action: Mailchimp
Campaign Type: Regular
List: Your Newsletter List

Subject: {{original article title}}
Body: {{newsletter_variation_1}}
HTML: [Use Mailchimp's templating to wrap the text]

For blog publishing (using WordPress REST API):

Copy
Action: Webhooks by Zapier
Method: POST
URL: https://yourblog.com/wp-json/wp/v2/posts
Authentication: Basic Auth
Username: [WordPress username]
Password: [WordPress application password]

Body (JSON):
{
  "title": "{{original article title}} - Summary",
  "content": "{{blog_summary}}",
  "status": "draft",
  "categories": [12],
  "featured_media": 0
}

Note: WordPress returns a 201 response with the post ID. Set this to "draft" so you can review before publishing.

For social media (using Buffer):

Copy
Action: Webhooks by Zapier
Method: POST
URL: https://api.buffer.com/1/updates/create.json
Authentication: API Key
Key: [Your Buffer API Key]

Body (JSON):
{
  "profile_ids": ["[Your Instagram profile ID]"],
  "media": {
    "link": "https://yourblog.com/{{article slug}}",
    "picture": "{{social_image_url}}"
  },
  "text": "New article: {{original article title}}. Read the full piece.",
  "scheduled_at": "{{current time + 2 hours}}"
}

Testing the Full Workflow

Before running this live, test it with a single article. In Zapier, use the "Test" button on each step to verify the outputs. Check that:

• Copy.AI generates coherent variations (you may need to adjust prompts if outputs are generic)
• Resoomer doesn't lose critical information in the summary
• Widify produces readable graphics (test the brand colour contrast)
• API responses map correctly to each next step

Use Zapier's logs view to debug any failures. Common issues: API keys stored incorrectly, content fields too long for the API's token limit, or missing required fields in JSON bodies.

The Manual Alternative

If you want to keep human review in the loop (which is wise initially), set everything up the same way but change the final step. Instead of publishing directly, use Zapier's "Send email" action to mail a digest to yourself with all generated content, the social image, and the blog summary. You review everything, make edits, and publish manually.

This takes five minutes instead of thirty because all the rewriting and formatting happens automatically; you're only checking quality, not doing the work yourself.

To do this, create a new action after Widify:

Copy
Action: Send Outlook/Gmail Email
To: your@email.com
Subject: New content ready for review: {{article title}}
Body:

NEWSLETTER VERSION (PROFESSIONAL):
{{newsletter_variation_1}}

NEWSLETTER VERSION (CONVERSATIONAL):
{{newsletter_variation_2}}

BLOG SUMMARY:
{{blog_summary}}

SOCIAL IMAGE:
[Image attached]
Image URL: {{social_image_url}}

Review and approve before publishing to channels.

This hybrid approach is actually recommended for the first two weeks, until you're confident the AI outputs match your standards consistently.

Pro Tips

Rate Limiting and Costs

Copy.AI and Resoomer both rate-limit API calls. Copy.AI allows 60 requests per minute on the starter plan; Resoomer allows 100 per day. If you're running this for multiple articles daily, you'll hit those limits. Space out your triggers using Zapier's "Delay" action, or batch articles together by scheduling the automation to run once daily rather than on every new post.

Copy
Insert before Step 2:
Action: Delay
Wait: 5 minutes

This prevents overwhelming the APIs and also gives you time to review content before it distributes.

Error Handling

Set up error notifications so you know when a step fails. In Zapier, use the "Filter" action to check API responses:

Copy
Condition: Copy.AI response status is 200
(If not, send error email before continuing)

In n8n, use the "Error Trigger" node to catch failures and route them to a notification channel.

Prompt Tuning

The quality of your newsletter variations depends entirely on the prompts you send to Copy.AI. Generic prompts produce generic output. Instead of "Rewrite this," use:

"Rewrite this article for senior managers at fintech companies. Emphasise ROI and compliance implications. Use no jargon. Include a specific number or metric from the article."

Test different prompt structures over a week and keep what works. Copy.AI tracks prompt history, so review your best-performing variations and replicate their prompts.

Avoiding Republishing

Zapier may re-trigger the same article if your RSS feed doesn't update cleanly. Add a deduplication step using Zapier's "Filter" action:

Copy
Condition: {{article URL}} has not been seen before
(Or: Store URL in a database and check against it)

Alternatively, store article URLs in a Google Sheet and use the "Lookup Spreadsheet" action to skip ones you've already processed.

Cost Optimisation

Running this three times daily costs roughly £30 per month (see Cost Breakdown below). If that's high, reduce Copy.AI variations from three to one, or run the workflow only on weekdays. You can also batch articles: instead of publishing immediately, queue five articles and send a weekly digest newsletter. This reduces API calls by 80% and often performs better anyway.

Cost Breakdown

If you're running this for a single weekly newsletter, costs drop to roughly £50/month. If you're publishing twenty articles daily, you'll move into higher-tier plans and costs could reach £250/month, but you'll be distributing at scale.