Resources · Make integration

Ghost Make integrationAutomate Ghost with Make.

Can Make take the repetitive side of running Ghost off your plate? The Ghost Make integration brings 13 modules: 4 instant triggers, 6 actions and 3 searches. This page connects your account, builds a first scenario with you and explains each module.

Try the Ghost integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Ghost Make integration do for your site?

The Ghost Make integration links your Ghost site to Make, a no-code tool where you chain apps into a scenario (the automation you build, one brick after another). Ghost can start a scenario the moment a member, post, page or tag changes, and Make can create, update, delete or search members and posts for you.

Paying customers become members without copy-paste. A sale or a form entry in another app starts the scenario, and Create a Member adds that person to your Ghost audience. When the same email might already be there, Search Members checks first.

Your team hears about every change on the blog. Watch Posts reacts when a post is created, updated or deleted, and the next module passes the news to the chat app or spreadsheet your editors already use.

Old content gets tidied in one pass. Search Posts returns the posts that match your criteria, then Update a Post or Delete a Post works through them one at a time.

What the list does not cover: pages and tags only have triggers, with no module to create or edit them. For anything missing, Make an API Call reaches the Ghost API with the same connection. Ghost also exists as a node in n8n, described on the Ghost n8n integration page, and the n8n vs Make comparison helps you pick a side. New to Make altogether? The Make training starts from zero.

Connect

How do you connect Ghost to Make?

  1. 01

    Create a custom integration in Ghost

    In Ghost admin, open Settings, then Integrations, and click Add custom integration. Name it and click Create. Copy the API key Ghost displays, the API URL from your browser's address bar and the Integration Id at the end of that URL.

  2. 02

    Open the connection window in Make

    Add any Ghost module to your scenario and click Create a connection. A connection is your Ghost account linked to Make once, then reused by every Ghost module. The Connection name field is optional, yet a clear name helps if you manage two sites.

  3. 03

    Paste the credentials and save

    Enter the details you copied from Ghost, or follow the on-screen instructions, and confirm. From then on, Make can read your site, so the module fields offer lists to pick from instead of blank boxes.

First scenario

Your first scenario: turn a new customer into a Ghost member

GoalWhen a new customer shows up in another app, Make adds them to Ghost as a member.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your customers first appear, such as your form or checkout tool, and choose its trigger.

  2. 02

    Add Create a Member

    Click the + on the right of that first module, search for Ghost and choose Create a Member. Select your Ghost connection, or create it now with the details from the section above.

  3. 03

    Map the customer data

    Fill the fields Create a Member shows by mapping data from the first module. Each customer travels as a bundle, one item passed from a module to the next, so one customer gives one member.

  4. 04

    Test with Run once

    Click Run once, then send a test entry through your first app. Read the bundles each module received and look for the new member in Ghost admin before going further.

  5. 05

    Schedule and switch it on

    If the first module is a scheduled trigger, its clock sets how often Make checks, every 15 minutes by default. Switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

Which Ghost events can start a scenario?

4 modules start a scenario when something happens in Ghost. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Ghost as soon as it happens.

Ghost1Watch Members

Watch Members

Instant trigger

In Make“Triggers when a member is created, updated or deleted.”

Watch Members starts your scenario whenever someone joins your Ghost audience, changes their member record or is removed from it. The member reaches Make as a bundle, ready for whatever module comes next.

How it fires
instant: Ghost calls Make through a webhook as soon as it happens.
When to use it
a new subscriber should land in your CRM or your support tool while the signup is still fresh.
Watch out
creation, update and deletion all run the same trigger, so a removed member also starts the scenario. Build the next modules with those three cases in mind.
Ghost2Watch Pages

Watch Pages

Instant trigger

In Make“Triggers when a page is created, updated or deleted.”

Pages are the standalone parts of a Ghost site, like an About or a Contact page, kept apart from your blog posts. Watch Pages sends Make every page that gets created, edited or deleted.

How it fires
instant: Ghost calls Make through a webhook as soon as it happens.
When to use it
your legal or pricing page changes and the team wants each edit logged in a shared sheet.
Watch out
no Ghost module creates or edits a page, so the reaction to this trigger happens in another app, or through Make an API Call.
Ghost3Watch Posts

Watch Posts

Instant trigger

In Make“Triggers when a post is created, updated or deleted.”

For an editorial scenario, this is the natural starting point. Watch Posts hands Make each post the moment it is created, edited or deleted, and the rest of the scenario runs on it.

How it fires
instant: Ghost calls Make through a webhook as soon as it happens.
When to use it
an article goes out and your social media manager should get a heads-up in the team chat.
Watch out
think twice before following it with Update a Post on the same site. An edit is exactly what Watch Posts listens for, so the scenario could restart itself and use up operations.
Ghost4Watch Tags

Watch Tags

Instant trigger

In Make“Triggers when a tag is created, updated or deleted.”

Tags sort your Ghost content into topics. Watch Tags tells Make each time a tag is added, renamed or removed, and passes that tag on as a bundle.

How it fires
instant: Ghost calls Make through a webhook as soon as it happens.
When to use it
your editors keep a topic list in a spreadsheet or a wiki and want it to match Ghost without manual updates.
Watch out
Make has no module to create or edit a tag, so this flow only runs one way, from Ghost toward your other tools.
Modules

What can Make do inside Ghost?

Ghost gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Ghost1

Create a Member

Action

In Make“Creates a member.”

Create a Member adds a person to your Ghost audience from any other app, whether they bought something, registered for an event or filled in a form.

When to use it
a customer pays in your checkout tool and should get member access on Ghost without anyone typing their email.
Watch out
if the same person may already be a member, place Search Members before this step to check.
Ghost2

Create a Post

Action

In Make“Creates a post.”

With this action, text written somewhere else lands in Ghost as a brand new post, whether it comes from a shared doc, a spreadsheet row or a writing tool.

When to use it
your writers draft outside Ghost and the editor wants each piece waiting in Ghost for review.
Watch out
one bundle makes one post. Run once on a list of ten rows gives ten posts, so test on a single row.
Ghost3

Delete a Member

Action

In Make“Deletes a member.”

Removing someone from your Ghost member list becomes a step of a scenario, driven by an event in another tool.

When to use it
a reader asks your support desk to erase their data, and the request has to reach Ghost as well.
Watch out
a delete cannot be undone from Make. Confirm with Search Members that the mapped member is the right one before this module runs.
Ghost4

Delete a Post

Action

In Make“Deletes a post.”

Outdated articles, test posts and forgotten drafts go away with Delete a Post, one post for each bundle it receives.

When to use it
right after Search Posts has gathered the posts you no longer want on the site.
Watch out
Watch Posts fires on deletions too. If another scenario starts from that trigger, expect it to hear about the posts this module removes.
Ghost5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

The other twelve modules cover the common jobs. Make an API Call sends your own request to the Ghost API, reusing the connection you already set up.

When to use it
you need an action the list does not offer, and no other module comes close.
Watch out
you write the request yourself, which makes it the most technical module here. Keep the Ghost API documentation open while you build it.
Ghost6

Update a Post

Action

In Make“Updates a Post.”

Update a Post edits an article that already exists instead of publishing a copy, so links and readers stay on the same post.

When to use it
a product name or an event date changed in your spreadsheet and the related article should follow.
Watch out
the module needs the post to edit, so find it with Search Posts first. Behind Watch Posts on the same site, be careful: an edit is a change that trigger watches, so the scenario may start again.
Ghost7

Search Authors

Search

In Make“Lists all authors or searches authors by criteria.”

Search Authors pulls the writers of your site, all of them or only those matching the criteria you set.

When to use it
you keep a contributor directory in a spreadsheet and want it filled straight from Ghost.
Watch out
a search can return zero, one or several bundles. Every module after it runs once per author found, and each of those runs counts as an operation.
Ghost8

Search Members

Search

In Make“Lists all members or searches members by criteria.”

This search looks through your Ghost audience and returns the whole list or just the members that fit your criteria.

When to use it
before Create a Member, to check a customer is not already there, or to copy your members into a spreadsheet for a review.
Watch out
a wide search on a large audience produces many bundles, and every module that follows multiplies the operations used.
Ghost9

Search Posts

Search

In Make“Lists all posts or searches posts by criteria.”

Search Posts gathers articles from your site so the next modules can work on them, the full archive or a filtered slice.

When to use it
you want a roundup for a newsletter, an audit sheet of old content or a cleanup with Delete a Post.
Watch out
before chaining Update a Post or Delete a Post, test with Run once and read the bundles to be sure the criteria caught only the posts you meant.
Need help

Need help automating Ghost with Make?

A person reads every message.

FAQ

Questions people ask about Ghost and Make

01Is the Ghost Make integration free?
Yes. Ghost is a standard app in Make, so it works on the Free plan. That plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on each bundle. Your Ghost subscription is a separate matter, handled on Ghost's side.
02What does it take to connect Ghost to Make?
An active Ghost account; the Make documentation also mentions a Content API Key. In Ghost admin, go to Settings, then Integrations, click Add custom integration, name it and click Create. Copy the API key, the API URL from the address bar and the Integration Id found at the end of that URL. Back in Make, click Create a connection on any Ghost module, give it a name if you like, and paste those details. For one of the four Watch triggers, click Create a webhook before Create a connection.
03Do Ghost triggers in Make react in real time?
Yes. All four Ghost triggers, Watch Members, Watch Pages, Watch Posts and Watch Tags, are instant: Ghost calls Make through a webhook as soon as something is created, updated or deleted. They do not wait for a polling interval, unlike scheduled triggers, which Make checks every 15 minutes by default on a new scenario. The flip side is that every change of the watched type runs the scenario, deletions included, so plan the next modules for all three events. Each run uses operations on your plan.
04What if a Ghost module is missing in Make?
Look at Make an API Call. It sends a request to any endpoint of the Ghost API with the connection you already have, which covers what the listed modules leave out. The list has no module to create a page or a tag, for example, since those two only have triggers. Keep in mind that the Make documentation for Ghost is AI-generated from Ghost's own documentation and warns it may contain mistakes, so check important details with Ghost before you rely on them.
05Make or n8n for Ghost?
It depends on the tool your team already works in. Ghost exists on both sides: 13 modules in Make, and a node in n8n that has its own page on this site. This page covers the Make side, with scenarios built from modules and a connection set up once. No ranking between the two is given here, and the n8n vs Make comparison on the site lays out the criteria. If your other automations already live in one of the two tools, adding Ghost there keeps everything in a single place.
Same platform

Other docs you might need on this stack.

Browse all integrations