Resources · Make integration

Drupal Make integrationAutomate Drupal with Make.

Could new Drupal content reach your other tools without anyone copying it by hand? The Drupal Make integration gives you 6 modules: one trigger that spots new content and five actions that create, read, update, delete or call the API. This guide shows site editors and ops teams how to connect Drupal and build a first scenario.

Try the Drupal integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Drupal Make integration let you automate?

The Drupal Make integration links your Drupal site to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes something in an app. With Drupal, those bricks work on content of any content type you pick.

Publish once, share everywhere. Watch New Content picks up each new article or page, and the next module sends its title and link to the tool your marketing team already reads. Nobody has to remember to announce it.

Turn outside data into draft pages. A product team that keeps its catalog in a spreadsheet can feed Create a Content, so every new row becomes a Drupal item of the right type. If your list lives in a base, the Airtable Make integration page shows the other side of that flow.

Keep content in sync. When a record changes elsewhere, Update a Content rewrites the matching Drupal item, and Get a Content reads an item back so a later module can use its fields.

Know the limits before you start. Make's own documentation for Drupal is marked as limited, because there is not enough public information about the app, so expect to test each module with Run once. Anything the five actions do not cover goes through Make an API Call. Drupal is also worth checking on n8n; the n8n vs Make comparison lays out how the two tools differ, and the Make training helps if you are new to scenarios.

Connect

How do you connect your Drupal site to Make?

  1. 01

    Add a Drupal module

    In your scenario, click the + and search for Drupal, then pick any module. Click Create a connection: a connection is your Drupal account linked to Make once, and every Drupal module in your scenarios can reuse it.

  2. 02

    Name it and authorize

    Give the connection a name if you like, such as the site it points to, which helps once you run several sites. Then follow what Drupal asks for: either approve Make on the authorization page or paste the key your site provides.

  3. 03

    Save and check the lists

    Click Save. The module is now tied to your site, and Make can show the content types it can read. If that list stays empty, the account behind the connection is the first thing to look at.

First scenario

Your first scenario: read each new Drupal item as it lands

GoalWhen new content is created in Drupal, Make picks it up and reads the full item so the next module can use it.

  1. 01

    Create the scenario

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

  2. 02

    Place the trigger

    Search for Drupal, choose Watch New Content and click Create a connection to link your site, or pick the connection you already saved.

  3. 03

    Choose the content type

    Fill in the module: select the content type to watch. Once the connection exists, Make lists the types it can read, so there is nothing to type from memory.

  4. 04

    Add Get a Content

    Click the + on the right of the trigger, add Get a Content, and map the item found by the trigger so Make reads that exact piece of content.

  5. 05

    Test with Run once

    Create a test item in Drupal, then click Run once. Open each module's bubble to read the bundles it received, one bundle per content item.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. You can add a third module later to send the content elsewhere.

Triggers

What starts a Drupal scenario

1 module starts a scenario when something happens in Drupal. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Drupal as soon as it happens.

Drupal1Watch New Content

Watch New Content

Scheduled trigger

In Make“Triggers when a new content is being created for any content type you specify.”

Watch New Content hands your scenario every fresh piece of content created on your site, for the content type you choose, so each new article, page or product item can start a chain of work.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default and never under 15 minutes on the Free plan.
When to use it
pick it when publishing should lead to something else, such as a message to the editorial channel or a row in a tracking sheet.
Watch out
its description covers newly created content only, so do not count on it to catch edits to existing items.
Modules

What Make can do in Drupal

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

Drupal1

Create a Content

Action

In Make“Creates a new content for any content type you specify.”

Create a Content adds a new item to your Drupal site in the content type you pick, filled with data that came from an earlier module.

When to use it
a form reply, a spreadsheet row or a product record should become a Drupal page without anyone opening the admin screen.
Watch out
run it once on a test type first, since every run adds a new item.
Drupal2

Delete a Content

Action

In Make“Deletes a content by type.”

Delete a Content removes one item of a given type from your site, which keeps Drupal tidy when the source record disappears elsewhere.

When to use it
a product is withdrawn from your catalog and its Drupal page should go with it.
Watch out
every run removes the item it receives, so map the item carefully and test on a dummy entry first.
Drupal3

Get a Content

Action

In Make“Retrieves a сontent based on type.”

Get a Content reads one existing Drupal item of a given type and passes its data to the modules that follow it in the scenario.

When to use it
the trigger or another app gives you an item reference, and you need the full content before sending it to a newsletter tool or an archive.
Watch out
it reads a single item, not a list, so feed it one reference at a time.
Drupal4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Drupal API from your scenario, using the same connection as the other Drupal modules.

When to use it
you need something the five listed modules do not offer, like a request your site's API exposes but Make has no ready-made module for.
Watch out
Make's Drupal documentation is limited, so read your own site's API reference before building the request.
Drupal5

Update a Content

Action

In Make“Updates a content by type.”

Update a Content rewrites an existing item of a given type with fresh data, so your Drupal site reflects changes made in another tool.

When to use it
a price, a date or a description changes in your source of truth and the matching page must follow.
Watch out
it needs the right item to change, so place Get a Content before it when the reference is uncertain.
Need help

Need help automating Drupal with Make?

A person reads every message.

FAQ

Drupal and Make: common questions

01Is the Drupal Make integration free?
Yes, Drupal is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Each module run on one item is an operation, which is what Make counts against your monthly credits.
02What does it take to connect Drupal to Make?
You need access to your Drupal site and a Make account. Make's documentation lists no specific prerequisite for Drupal and gives no dedicated setup steps, so the generic flow applies: add a Drupal module, click Create a connection, optionally name it, then authorize Make on your site or paste the key it gives you, and click Save. Pick an account that can see the content types you want to automate, and run a quick test right after saving to confirm the connection reads your content.
03Does the Drupal trigger in Make work in real time?
No. Watch New Content is a scheduled trigger: Make checks your site on the scenario's schedule instead of being called by Drupal the moment something happens. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. For most publishing workflows that delay is fine, but if you need an immediate reaction, plan for it before building on this trigger.
04What if a Drupal module is missing in Make?
Use Make an API Call. It calls any endpoint of the Drupal API from your scenario with the connection you already set up, so you are not limited to the five ready-made actions. Keep in mind that Make flags its own Drupal documentation as limited because little public information exists about the app, so your site's API reference is the better guide for building the request. Test each call with Run once and read the bundle it returns before switching the scenario on.
05Make or n8n for Drupal: which fits better?
It depends on the tool your team already works in. Make gives Drupal 6 modules: one scheduled trigger for new content and actions to create, read, update and delete items, plus Make an API Call for the rest. Drupal may also have an n8n node, so check what that node offers for your use case before choosing. Compare the specific operations you need on each side, try your main flow in both if you can, and keep the one your team can maintain without help.
Same platform

Other docs you might need on this stack.

Browse all integrations