Liquid Web WordPress + Make.com: Content Automation Pipeline

Contains affiliate links. Disclosure.

Combine Liquid Web managed WordPress with Make.com to automate content pipelines: scrape with Apify, transform, and publish to WordPress via the REST API.

WordPress on Liquid Web gives you fast, managed hosting. Make.com handles the workflow. Apify provides the data.

Architecture Overview

Apify / Firecrawl  →  Make.com  →  WordPress REST API  →  Published post
         (scrape)        (transform, schedule)      (Liquid Web)

1. Scrape — Apify Actor or Firecrawl crawls a source.
2. Transform — Make.com maps fields, filters, adds metadata.
3. Publish — WordPress REST API creates or updates posts.

Prerequisites

• Liquid Web managed WordPress (or VPS with WordPress)
• Make.com account
• Apify account for scraping, or Firecrawl for crawl-to-markdown

Step 1: Enable WordPress REST API Auth

WordPress 5.6+ supports Application Passwords:

1. WordPress Admin → Users → Profile
2. Scroll to Application Passwords
3. Name: make-com-automation
4. Click Add New Application Password
5. Copy the generated password (one-time display)

Step 2: Create Make.com Scenario

1. New scenario in Make.com
2. Trigger — Choose one:
   • Schedule — Run daily or at intervals
   • Webhook — Trigger from Apify webhook
   • Google Sheets — New row added
3. Apify — Run Actor, get dataset
4. Tools → Set variable — Map and clean data
5. WordPress → Create a post — Connect with:
   • Site URL: https://yoursite.com
   • Username: your WordPress user
   • Application Password: from Step 1

Step 3: Map Scraped Data to Post Fields

Apify/Firecrawl field	WordPress field
title	Post title
markdown or content	Post content
url	Custom field or metadata
publishedDate	Post date
image	Featured image (use HTTP → Get file, then upload)

Step 4: Handle Featured Images

Make.com’s WordPress module can attach images:

1. HTTP → Get a file — Fetch image URL from scraper output
2. WordPress → Create a post — In “Featured image”, map the file from previous module

Or use a custom field and a WordPress plugin to set the featured image from URL.

When to Use This Setup

• Content aggregation — Curate from multiple sources into one site
• Product feeds — Scrape product data, publish as WooCommerce or custom posts
• News roundups — Pull headlines, format, publish on schedule
• Lead/blog sync — Republish or transform content from other properties

Alternatives

• Apify only — Some Apify Actors can write directly to WordPress via custom code.
• Firecrawl + Make — Use Firecrawl for crawl-to-markdown, then Make for transformation and publishing.
• No-code only — Make.com can pull from RSS, Google Sheets, Airtable without scraping.

Liquid Web’s WordPress hosting keeps the site fast and secure while Make.com handles the automation logic.

Next step

Start with one source and one Make.com scenario. Add sources and complexity once the pipeline runs reliably.

Frequently Asked Questions

Yes. Use Apify or Firecrawl to scrape, Make.com to transform, and WordPress REST API to publish. Application Passwords handle auth.

WordPress REST API POST /wp/v2/posts. Use Make.com's WordPress module or custom HTTP request with Application Password in Basic Auth.

Only republish or aggregate with permission or from sources that allow it. Add value (summaries, analysis). Duplicate content can hurt rankings.