Drupal Zapier integrationAutomate Drupal with Zapier.
The Drupal Zapier integration gives you 1 trigger, 2 actions and 0 searches. Enough to push every new page or article from your site into other tools, or to create content in Drupal from a form, a sheet or a CRM, without a developer.
Verified Trustpilot reviews · AI, automation & growth agency
What the Drupal Zapier integration actually does for you
It links your Drupal site to the other apps you use, through a Zap: an automation with one starting event and one or more steps that run every time that event happens. Drupal can start a Zap when content is created, and it can receive content another app sends.
Three outcomes come up again and again. A publishing alert: New Content spots each fresh article and a chat tool tells the editorial team it is live. A content intake: Create Content turns a form answer, a sheet row or a CRM record into a Drupal node of the type you choose. A custom call: API Request (Beta) reaches the parts of your site the two ready-made operations leave out, with your login already attached.
Now what it does not do. There is no instant trigger here, so Zapier checks your site on a timer and a new page waits for the next check. There is no search step, so a Zap cannot look up an existing node before acting. And there is no ready-made action to edit or delete content: anything beyond creation goes through API Request, which is a technical step.
If you are weighing tools, the Drupal Make integration page covers the same app on another platform, and our Zapier review is the place to judge the tool itself.
Zapier vocabulary in one minute
Eight words, and the rest of this page reads easily.
- Zap
- A Zap is an automation that runs on its own: a new node appears on your site, for instance, and the steps you lined up behind it follow.
- Trigger
- The starting event of a Zap. For Drupal it can only be New Content; any other app you connect can play that role too.
- Action
- Each step that runs after the start: post in Slack, add a row, or create a node on your Drupal site with Create Content.
- Task
- Zapier's billing unit: one action that goes through. A Slack post about a new article is one task; your plan counts those.
- Polling trigger
- Zapier asks your site on a timer whether anything new was created, and keeps only the nodes it has not seen yet. New Content works so.
- Instant trigger
- A trigger the app reports itself as soon as the event happens, with no timer. The Drupal app on Zapier has none of these.
- Filter
- A checkpoint after the trigger: only the nodes that meet your condition go further, the others end the run right there.
- Multi-step Zap
- A Zap with more than one trigger and one action. Filtering articles or adding a second step makes one, and it needs a paid plan.
What a Drupal Zap really costs
Drupal is not a premium app, so it works on the free plan. The bill is counted in tasks, not in checks.
- Tasks on the free plan100 per month
- Steps per Zap on the free plan2 (one trigger, one action)
- Premium appNo
The New Content trigger never costs a task, however often Zapier looks at your site. Each action that goes through counts once; one that fails counts nothing. The free plan gives 100 tasks a month and two steps per Zap: New Content plus one action. Add a filter or a second action and the Zap needs a paid plan. Your plan also sets how often Zapier looks at your site for new content: every 15 minutes on Free, down to one minute on Team and Enterprise.
Connect your Drupal site to Zapier
- 01
Open the connections page
In your Zapier account, go to Apps and click + Add connection. A connection is your Drupal account linked once, then reused by every step of every Zap that touches the site.
- 02
Pick Drupal
Type Drupal in the search box of the dialog, select it, then click Add connection. Have a Drupal account ready on the site you want to automate: without one, there is nothing to link.
- 03
Sign in and allow access
A tab opens on the Drupal side. Sign in, then grant Zapier access to the account. If some content belongs to colleagues, the account needs read or write rights on it, or the Zap will not see or touch it.
Your first Zap: tell the team when an article goes live
GoalEach new Drupal article that matters to the newsroom lands in a Slack channel, and nothing else does.
- 01
Build: choose the trigger
Create a Zap, pick Drupal as the app and New Content as the event, then select your connection. Specify the content type to watch, such as your articles.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of that type from your site, so you set the rest of the Zap on a real one, not on a guess.
- 03
Add a filter
From the plus icon, add Filter. In the sample, spot the value that marks the articles the team wants, then set the field, the rule and that value. This makes the Zap multi-step, so a paid plan.
- 04
Add the Slack action
Add Slack with Send Channel Message, choose the channel and map the title and link from the Drupal step into the message.
- 05
Test, then publish
Test each step and read what came back. When the message looks right, click Publish: from then on, each new article that passes the filter is posted.
The Drupal trigger
1 event starts a Zap when something happens in Drupal. Zapier checks for them at the interval your plan allows.
New Content
Polling triggerIn Zapier“Triggers when new content is created for any content type you specify.”
Starts your Zap each time a piece of content is created on your site, for the content type you name in the step. Pick articles, basic pages or any custom type your site defines, and only those will set the Zap off.
The Drupal actions
Drupal gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Content
ActionIn Zapier“Creates new content for any content type you specify.”
Adds a new node to your site, in whichever content type you specify, filled with what earlier steps carried. A form answer can become an event page; a row in a spreadsheet, a product sheet.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced step that sends your own request to Drupal, with the connection's login already included. You choose the method and the address, and decide whether an error from the site should stop the step.
When a Drupal Zap breaks
Zapier ties no help article to Drupal, so the traps below are the general ones. They still catch most people.
None of these shows up as an error on day one. They show up as a missing post, an empty task counter or a channel flooded with messages.
Old content is never picked up
A Zap only reacts to what is created after you switch it on. The articles already on your site stay where they are; moving that backlog is a separate job.The Zap that feeds itself
Create Content writing into the content type that New Content watches on the same site starts the Zap again each time, and burns through your tasks fast.A bulk import gets held back
Publish hundreds of nodes at once after a migration and the trigger returns a huge batch. Zapier's flood protection can hold it back rather than run it all.No duplicate runs
Zapier remembers which items it has already seen on this polling trigger, so a node that was picked up once does not start the Zap a second time.
Need help automating Drupal with Zapier?
A person reads every message.



