Resources · Zapier integration

Agility CMS Zapier integrationAutomate Agility CMS with Zapier.

The Agility CMS Zapier integration gives you 3 triggers, 6 actions and 1 search. All three triggers are instant, so a saved draft, a published page or an approval in your content workflow reaches your other tools the moment it happens.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Agility CMS Zapier integration does for a content team

Agility CMS is a headless content platform: editors write once and developers send that content to sites and apps. Zapier reacts to what happens in it and acts for you. What you build there is a Zap: one event that starts it, then the steps that run each time it comes back.

The integration follows the life of a content item: saved, sent for approval, approved or declined, published, unpublished. Three triggers listen to that life, six actions push it forward and one search reads an item. Three outcomes stand out.

Approval that starts by itself. Save plus Request Approval for an Item sends a fresh draft to review without the writer clicking anything else. A marketing team with a legal check on every landing page stops losing drafts in limbo.

Publishing that follows the decision. Workflow plus Publish Item puts an item live once the approval comes through, so the editor-in-chief does not have to come back and press the button.

Content that can be pulled. Unpublish Item takes an item offline from a Zap, for example when a product page has to go dark quickly.

What Zapier does not do for Agility CMS: there is no delete action, and every action works on one item identified by its Content ID and Language Code. To compare with other tools, our n8n vs Zapier comparison is a good start.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this page. Here they are in plain English.

Zap
The automation you build on Zapier: one event that starts it, then the steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval and keeps only the ones it has not seen.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. All three Agility CMS triggers work this way.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set. Otherwise the run stops right there.
Search step
A step that looks up something that already exists in an app, so the steps after it can use it. Fetch a Content Item is one.
Cost

What an Agility CMS Zap costs you

Zapier bills tasks, not triggers. Listening to Agility CMS is free; only completed actions count.

  • Free plan tasks100 per month
  • Steps per Zap on Free2 (one trigger, one action)
  • Agility CMS triggers3, all instant
  • Premium appNo

The trigger never costs a task, however many times your editors hit save. Each action that succeeds counts once: a Zap with three actions uses three times more than a Zap with one, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps, one trigger and one action. Add a filter or the Fetch a Content Item search and the Zap becomes multi-step, which needs a paid plan. Agility CMS is not a premium app, and the polling grid below does not apply to its instant triggers.

Connect

Connect your Agility CMS account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Agility CMS account linked to Zapier once, then reused by every Agility CMS step.

  2. 02

    Pick Agility CMS

    Search for Agility CMS in the dialog, select it and click Add connection. You need an existing Agility CMS account; Zapier does not create one for you.

  3. 03

    Sign in and grant access

    Sign in to Agility CMS in the tab that opens and allow Zapier to use the account. Any content the Zap should approve, publish or save must be reachable with that account's rights.

First Zap

Your first Zap: send saved drafts to review

GoalWhen an Agility CMS item that matches your condition is saved, request approval for it automatically.

  1. 01

    Build: pick the trigger

    Start a new Zap, choose Agility CMS and the Save trigger, then pick your connection. The lightning bolt shows the trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent saved items of the account, so pick a real draft to map the next steps on.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then in Configure & test set the field, the rule and the value. Use a text rule on text values, or the filter never passes.

  4. 04

    Add Request Approval

    Add the Agility CMS action Request Approval for an Item. Map Content ID and Language Code from the tested item, so each run targets the draft that was just saved.

  5. 05

    Test, then Publish

    Test each step and check the item's status in Agility CMS. Then click Publish. With the filter, this Zap needs a paid plan.

Triggers

The 3 Agility CMS triggers

3 events start a Zap when something happens in Agility CMS, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Publish

Instant trigger

In Zapier“Triggers when a new item is published.”

An item has just gone live in Agility CMS: this trigger hands that newly published item to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a SaaS company announces each new help article in its product changelog as soon as the article is live.
Watch out
never pair it with Publish Item on the same item, or the Zap republishes what it just heard about and can loop.
2

Save

Instant trigger

In Zapier“Triggers when a new item is saved.”

Every time an item is saved, this trigger passes it to the Zap. It is the earliest point in the life of a piece of content.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a newsroom wants each saved draft routed to the right reviewer instead of waiting for someone to notice it.
Watch out
a Save Item action in the same Zap saves again and starts the trigger again; keep those two apart.
3

Workflow

Instant trigger

In Zapier“Triggers when a workflow action happens on an item, such as approvals.”

This one listens to the approval workflow itself: a workflow action on an item, such as an approval, starts the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
once legal approves a campaign page, the content lead wants it to go live without logging back in.
Watch out
it fires on workflow actions in general, so add a filter when only one kind of decision should move the item forward.
Actions

The 6 Agility CMS actions

Agility CMS gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Approve Item

Action

In Zapier“Approves a Content Item”

Approves an item waiting in the workflow, on behalf of the connected account.

When to use it
a sign-off given in another tool should count as the approval in Agility CMS too.
Watch out
Content ID and Language Code are required, and approving from a Zap skips the human look, so filter carefully.
2

Decline Item

Action

In Zapier“Declines a Content Item”

The counterpart of approval: the item is marked as declined in the workflow, from a Zap.

When to use it
a reviewer rejects a translation in a separate tool and the item in Agility CMS should reflect that decision.
Watch out
both Content ID and Language Code are required.
3

Publish Item

Action

In Zapier“Publishes a Content Item”

Puts a content item live, the natural last step of an approval flow.

When to use it
approved event pages should go live straight after the decision, not the next morning.
Watch out
Content ID and Language Code are required, and a Zap triggered by Publish should not call it on the same item.
4

Request Approval for an Item

Action

In Zapier“Requests Approval for a Content Item”

Sends an item into the approval workflow, exactly as if the author had asked for review.

When to use it
every draft for a regulated product page must go to compliance before anyone can publish it.
Watch out
it needs the Content ID and the Language Code of the item.
5

Save Item

Action

In Zapier“Saves a Content Item”

Writes a content item from your Zap, either a new one or an update to an existing one.

When to use it
product specs maintained elsewhere become draft items in Agility CMS without anyone copying them.
Watch out
Content ID, Language Code, Reference Name and Fields are required, and a Content ID of -1 creates a new item.
6

Unpublish Item

Action

In Zapier“Unpublishes a Content Item”

Takes a live item offline from inside a Zap, so nobody has to open the CMS to pull it.

When to use it
a limited offer ends and its page has to disappear from the site at once.
Watch out
as with every action here, Content ID and Language Code are required.
Searches

The Agility CMS search

1 search step looks for data that already exists in Agility CMS, so a later step can use it.

A search step reads something that already exists in Agility CMS and hands it to the next steps. It sits at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the lookup does not go as planned.

1

Fetch a Content Item

Search

In Zapier“Fetches a Content Item”

Reads one content item by its ID and language, so later steps can use its current values.

When to use it
after a Workflow trigger, fetch the item to check its latest content before the Zap publishes it.
Watch out
Language Code and Content ID are both required.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that relied on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Agility CMS offers no such variant on Fetch a Content Item, so you will not see it here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When an Agility CMS Zap breaks

Zapier attaches no help article to Agility CMS and lists no app-specific limit. What breaks is what breaks on any Zap, sharpened by triggers and actions that act on the same items.

None of these shows a clear error; the Zap simply does more, or less, than you meant. Before you blame the CMS, check the four cases below. If you are stuck, our Zapier troubleshooting page is the next stop.

  • Old content never shows up

    A Zap only reacts to what happens after you publish it. Items saved or published before that stay where they are; moving that backlog is a separate job.

  • Save triggers Save, forever

    A Zap that writes into the place its own trigger watches sets itself off again. Save with Save Item, or Publish with Publish Item, is the trap here.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.

  • The wrong language is touched

    Each action works on one Content ID in one Language Code. Map the language from the tested item, or the Zap acts on another version of the content.
Need help

Need help automating Agility CMS with Zapier?

A person reads every message.

FAQ

Agility CMS Zapier integration: common questions

01Is the Agility CMS Zapier integration free?
Yes, within the free plan's limits. Agility CMS is not a premium app, so it works on Zapier's free plan, which gives 100 tasks a month and unlimited Zaps. The catch is size: one trigger and one action per Zap. As soon as you add a filter or the Fetch a Content Item search, the Zap becomes multi-step and needs a paid plan. A plain Save to Request Approval for an Item Zap stays free, while the same Zap with its filter, described above, does not.
02How many tasks does an Agility CMS Zap use?
One per successful action and none for the trigger. Editors can save drafts all day without costing anything on the Zapier side until an action completes. In a Zap with three actions, each one that succeeds counts on its own, so one run can cost three tasks. An action that fails is not counted. Watching Agility CMS for saves, publications or workflow steps never costs anything, whatever your plan, so a busy publishing week only shows through the actions it runs.
03Is Agility CMS on Zapier real time?
Yes. All three Agility CMS triggers are instant: the CMS tells Zapier the moment an item is saved, published or moved through the workflow, and the Zap starts right away. The polling intervals of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, do not apply to them. In the editor you will see a lightning bolt on these triggers, which is how Zapier marks an instant one.
04What does it take to connect Agility CMS to Zapier?
An Agility CMS account with rights on the content the Zap will touch. You add the connection from the Apps page with + Add connection, search for Agility CMS, sign in in the tab that opens and grant access. Then every action asks for a Content ID and a Language Code, so map both from the trigger's tested item. The connection is made once and every Agility CMS step reuses it.
05Why does an Agility CMS Zap keep running on its own?
Because it writes where its own trigger listens. A Zap that starts on Save and ends with Save Item saves the item again, which starts the Zap again. The same goes for Publish and Publish Item. Each loop burns tasks quickly. Split those flows: start on Workflow and end on Publish Item, or start on Save and end on Request Approval for an Item, so the action never feeds the trigger.
06What if the Agility CMS operation you need does not exist?
Check first whether you need a trigger or an action. Zapier offers three triggers on save, publish and workflow, six actions covering save, approval, decline, publish and unpublish, and one search to fetch an item. There is no delete action and no search by title or reference name. If your process depends on one of those, the Zap alone will not cover it, so look at how other automation tools handle Agility CMS first.
07Zapier, Make or n8n for Agility CMS?
Decide on criteria, not on brand. Look at which Agility CMS events and actions each tool exposes, how each one bills a run with several steps, and who on your team will maintain the flows. On Zapier, Agility CMS has three instant triggers, six actions and one fetch, and a simple two-step Zap runs on the free plan. If your publishing process needs many steps or branches per item, compare the cost of those runs on each platform.
Same platform

Other docs you might need on this stack.

Browse all integrations