Resources · Make integration

GatherContent Make integrationAutomate GatherContent with Make.

Can Make keep your GatherContent projects moving without anyone copying data by hand? The GatherContent Make integration gives you 15 modules: 5 triggers, 8 actions and 2 searches. This guide is for content and ops teams, and it walks you from the connection to a first working scenario.

Try the GatherContent integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GatherContent Make integration do?

The GatherContent Make integration links your GatherContent account to Make so that projects and items move on their own. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger, an action or a search. No code is involved.

A starter item in every new project. Watch New Projects spots a project as soon as Make checks, and Create an Item adds the first piece of content, so writers never open an empty project.

Content that comes from your other tools. A request logged in a task board or a form can become a GatherContent item through Create an Item, then Choose an Item Status places it at the right step of your workflow.

A clear view of what exists. List Projects and List Items pull your content inventory into a sheet or a report, and Get an Item fetches one item when a later step needs its details.

Keep the limits in mind. All 5 triggers are scheduled: Make checks GatherContent on the scenario's schedule, not the moment something changes. Rename an Item only changes the item's name. For any other endpoint, Make an API Call reuses the same connection. The Make review explains the editor, Make pricing covers plans, and if you also weigh n8n, read n8n vs Make.

Connect

How do you connect GatherContent to Make?

  1. 01

    Add a GatherContent module

    Open a scenario in Make, add any GatherContent module and click Create a connection. A connection is your GatherContent account linked to Make once, then reused by every GatherContent module.

  2. 02

    Generate your API key

    You need an active GatherContent account. In GatherContent, go to Personal Settings, open the API section, click Generate and copy the key shown on screen.

  3. 03

    Paste the credentials in Make

    Back in Make, give the connection a name in Connection name if you like (it is optional), enter the credentials you copied from GatherContent and save. The module can now read your account.

First scenario

Your first scenario with GatherContent

GoalWhen a new project appears in GatherContent, Make creates a first item inside it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Pick Watch New Projects

    Search for GatherContent, choose Watch New Projects and select your connection, or click Create a connection if this is your first GatherContent module.

  3. 03

    Add Create an Item

    Click the + on the right of the trigger, pick Create an Item and fill its fields. Map the project data coming from the first module so the item lands in the new project.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passing from module to module, here one project.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule (every 15 minutes by default), then switch the scenario on. Each new project now gets its starter item.

Triggers

Which GatherContent triggers start a scenario?

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

GatherContent1Watch New Accounts

Watch New Accounts

Scheduled trigger

In Make“Watches for accounts.”

Hands your scenario each new GatherContent account it finds, one bundle per account. That gives you a starting point for anything that should happen once, at the moment an account shows up, such as a setup checklist.

How it fires
scheduled. Make checks GatherContent on the scenario's schedule, so it is not instant.
When to use it
when an agency or a team manages several accounts and wants each one registered in a tracking sheet.
Watch out
on the Free plan the shortest gap between two scheduled runs is 15 minutes.
GatherContent2Watch New Items

Watch New Items

Scheduled trigger

In Make“Watches for items.”

Gives you every new item as soon as Make checks, so a fresh piece of content can notify the right person or feed another tool without anyone forwarding it.

How it fires
scheduled. Make polls GatherContent following the scenario's schedule; the clock badge on the module shows it.
When to use it
a blog post or a product page is added to GatherContent and your editor should see it in the team chat.
Watch out
each new item is one bundle, and every module after it counts one operation per bundle on your plan.
GatherContent3Watch New Projects

Watch New Projects

Scheduled trigger

In Make“Watches for projects.”

Catches each project created in GatherContent and passes it down the chain, which is the cleanest way to prepare a project the same way every time.

How it fires
scheduled. Make looks for new projects on the scenario's schedule, every 15 minutes by default.
When to use it
a website redesign kicks off and you want starter items, a notice to the client lead and a row in your planning sheet.
Watch out
pair it with Create an Item rather than Create a Project, otherwise the scenario would feed itself new projects.
GatherContent4Watch New Statuses

Watch New Statuses

Scheduled trigger

In Make“Watches for statuses.”

Reports the statuses that appear in GatherContent, one bundle per status, so the rest of your stack stays aligned with the workflow steps your team defines.

How it fires
scheduled. Make queries GatherContent at the rhythm set on the first module, not the second a status is added.
When to use it
a content lead adds a new review step and a reporting sheet or a project tool should list it too.
Watch out
this trigger watches statuses themselves, not items changing status; for items, start from Watch New Items or List Items.
GatherContent5Watch New Templates

Watch New Templates

Scheduled trigger

In Make“Watches for templates.”

Tells your scenario when a template is added in GatherContent, which helps you keep a shared catalogue of content structures current without checking by hand.

How it fires
scheduled. The check happens on the scenario's schedule, shown by the clock badge.
When to use it
your team designs a new landing page template and writers should hear about it in their usual channel.
Watch out
test it with Run once after creating a template, otherwise the first run may return no bundle and look broken.
Modules

What can Make do in GatherContent?

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

GatherContent1

Choose an Item Status

Action

In Make“Applies a specific status to an existing item.”

Moves an existing item to the workflow step you pick, so a draft can go to review the moment another tool says it is ready.

When to use it
a writer ticks a task as done in a project tool and the matching item should switch to its review status.
Watch out
the item must already exist; get or list it first so the module receives the right one.
GatherContent2

Create an Item

Action

In Make“Creates a new item.”

Adds a new piece of content to GatherContent from data your scenario already holds, which saves the copy and paste between a request and the writing space.

When to use it
a content request arrives through a form or a task card and should become an item ready for a writer.
Watch out
map fields from earlier modules instead of typing fixed values, or every run creates identical items.
GatherContent3

Create a Project

Action

In Make“Creates a new project.”

Opens a fresh GatherContent project from another tool, so a signed deal or a new client file already has its content space when the team starts.

When to use it
a project starts in your task manager and the editorial workspace should be ready before writing starts.
Watch out
never place it after Watch New Projects in the same scenario: each created project would start the scenario again.
GatherContent4

Get an Item

Action

In Make“Returns a specified item.”

Returns the details of one item you already know, so the following modules can use its content in a message, a document or a report.

When to use it
a trigger hands you an item reference and the next step needs the full record, not just its name.
Watch out
it needs one specific item; when you are hunting for items by criteria, List Items fits better.
GatherContent5

Get a Project

Action

In Make“Returns a specified project.”

Fetches a single project in full, which gives your scenario the context it needs before it writes to a CRM or notifies a client lead.

When to use it
a new item arrives and you want to show the name of the project it belongs to in a notification.
Watch out
for an overview of all projects, List Projects returns several bundles in one step instead.
GatherContent6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the GatherContent API with the connection you already set up, so a need that the listed modules miss does not stop your project.

When to use it
you need an action none of the other modules offers, and the GatherContent API documents it.
Watch out
you write the request yourself, so read the API documentation of GatherContent first; the other modules build it for you.
GatherContent7

Move an Item

Action

In Make“Moves an existing item.”

Shifts an existing item to another place in GatherContent, keeping content where the team expects to find it after a change of plan.

When to use it
content is reorganized after a site restructure and items should follow the new layout without manual dragging.
Watch out
run it with Run once on a test item first, since a wrong target moves real content.
GatherContent8

Rename an Item

Action

In Make“Updates a name of specified item.”

Gives an existing item a new name, which keeps titles consistent with a naming rule or with the name used in another tool.

When to use it
a product is renamed in your catalogue and its page item in GatherContent should carry the same name.
Watch out
this module only changes the name; to alter anything else, turn to Make an API Call.
GatherContent9

List Items

Search

In Make“Lists items or searches for them by specified parameters.”

Brings back the items that match your criteria, or all of them, so you can build an inventory or process a batch of content in one scenario.

When to use it
you want a sheet listing every item of a project for a content audit.
Watch out
a search returns zero, one or many bundles, and each module after it runs once per bundle, which adds operations.
GatherContent10

List Projects

Search

In Make“Lists projects.”

Returns your GatherContent projects as separate bundles, a handy base for a dashboard or for looping the same action over each project.

When to use it
a manager asks for an up to date list of active projects in a shared spreadsheet.
Watch out
every project becomes one bundle, so what follows counts one operation per project on your plan.
Need help

Need help automating GatherContent with Make?

A person reads every message.

FAQ

GatherContent and Make: frequent questions

01Is the GatherContent Make integration free?
Yes, GatherContent is a standard app in Make, available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios, with usage counted each month in credits, meaning operations. You still need your own active GatherContent account.
02What do you need to connect GatherContent to Make?
You need an active GatherContent account and an API key. In GatherContent, open Personal Settings, go to the API section, click Generate and copy the key. In Make, add a GatherContent module, click Create a connection, optionally name it in Connection name, then enter the credentials. That single connection serves all 15 GatherContent modules, so you set it up once and reuse it in every scenario that talks to the same account.
03Do GatherContent triggers in Make fire instantly?
No. All 5 GatherContent triggers are scheduled: Make checks GatherContent on the scenario's schedule, shown by a clock badge on the module. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. None of the modules is an instant trigger, so no webhook is involved, and a change in GatherContent appears in your scenario at the next check.
04What if a GatherContent module is missing in Make?
Use Make an API Call. It reaches any endpoint of the GatherContent API with the connection you already created, so you can cover what the other modules do not, for example editing more than the name of an item, since Rename an Item only changes the name. You write the request yourself, so keep the GatherContent API documentation open. If you prefer help, the team behind this site builds such scenarios.
05Make or n8n for GatherContent?
It depends on your criteria. On Make, GatherContent comes with 15 ready modules covering projects, items and statuses, plus Make an API Call for the rest, and a visual editor where you test with Run once. The same app often has an n8n node as well, so check whether one exists for GatherContent and compare the modules each tool offers for your use case. Pick the tool your team already uses and knows how to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations