Resources · Zapier integration

Plate Zapier integrationAutomate Plate with Zapier.

The Plate Zapier integration gives you 12 actions and 6 searches, with no trigger. Plate never starts a Zap on its own: another app does, and Plate receives the work, creating, updating or deleting posts, sections, elements and content objects.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Plate Zapier integration actually does

It lets your other tools write into Plate, the content management platform behind websites, shops, apps and portals. Plate is on the receiving end only: something happens elsewhere, and Zapier creates, changes, finds or removes content in your Plate account without anyone opening the editor.

Three results worth building. Posts that publish from a sheet: each new row in a planning file becomes a post through Create Post, so the editorial calendar and the site stop drifting apart. Content kept in sync: Search Post finds the right post and Update Post rewrites it when the source changes. Clean-up on cue: Delete Post or Delete Section removes content when another tool says it is retired.

Now what Zapier does not do here. Plate has no trigger, so a Zap (an automation on Zapier) can never start from something that happens in Plate: a new post, an edit or a deletion in Plate goes unnoticed. Every Plate Zap begins in another app. And most useful flows need a search before the update, which takes you past the free plan. Plan for that from the start rather than discovering it at publish time.

If you are comparing platforms, the n8n vs Zapier comparison is a good place to start, and the Zapier review gives the verdict on the tool itself.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, each explained once here.

Zap
The automation you build: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Plate has none, so the trigger always comes from another app.
Action
What the Zap does once it starts: the step that writes, sends or removes something for you, here in Plate.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items and keeping only what it has not seen yet.
Instant trigger
A trigger the app reports itself, calling Zapier when the event happens, so nothing waits for a scheduled check.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found, like an ID.
Cost

What a Plate Zap really costs

Plate is not a premium app (Zapier's label for apps kept for paid plans), so it runs on the free plan.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo

The trigger, from whatever app starts the Zap, never costs a task. Each Plate action that succeeds counts as one task; a failed one is not billed. The free plan gives 100 tasks a month and two-step Zaps: one trigger, one action. Add a search, a filter or a second action and the Zap turns multi-step, which needs a paid plan. How fast the Zap starts depends on the other app's trigger and, if it polls, on your plan.

Connect

Connect your Plate account in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Plate account linked once, then reused by every step that writes to Plate.

  2. 02

    Pick Plate

    Search for Plate in the dialog, select it, then click Add connection. You need an existing Plate account; Zapier will not create one. The same connection then serves all 18 Plate steps.

  3. 03

    Sign in and allow access

    Log in to Plate in the tab that opens and grant Zapier access. If the site belongs to someone else, check first that your login can read and edit the content the Zap will touch.

First Zap

Your first Plate Zap

GoalUpdate the matching Plate post whenever a row changes in your editorial sheet.

  1. 01

    Pick the starting app

    Create a Zap and choose the trigger in the app that holds your source content. Plate cannot start a Zap, so this first step always belongs to another tool.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of that account, so you map the next steps on real data.

  3. 03

    Find the post

    Add Search Post from Plate, connect your account and set the filter that points at the right post. Test it and check it found one.

  4. 04

    Update it

    Add Update Post, map the post ID returned by the search, then the new values from the trigger. Test the step and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. With a search in the middle it is multi-step, so it runs on a paid plan only. Change one row to confirm it works.

Actions

Plate actions

Plate gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Content Object

Action

In Zapier“Creates a new content object.”

Creates a content object in Plate from values handed over by the trigger app.

When to use it
push each new event from a registration tool into Plate as a reusable entry.
Watch out
map the values one by one on a real test item; a blank field from the trigger stays blank in Plate.
2

Delete Content Object

Action

In Zapier“Deletes a content object.”

Erases a content object, given its content object ID, the one required field.

When to use it
delete a cancelled event entry once the organiser cancels it at the source.
Watch out
placed after a search that returns several matches, it can remove more than one object.
3

Delete Element

Action

In Zapier“Deletes an element.”

Strips an element out of Plate, using its required element ID.

When to use it
pull a promotional banner when the offer ends in your marketing calendar.
Watch out
keep a record of what the Zap removed, in a sheet or a log, before trusting it alone.
4

Delete Post

Action

In Zapier“Deletes a post.”

Removes one or several posts from Plate, picked by post ID, the field the step cannot run without.

When to use it
take a job ad offline when the position is marked as filled in your hiring tool.
Watch out
a wrong ID deletes the wrong post; test with a throwaway post first.
5

Delete Section

Action

In Zapier“Deletes a section.”

Drops a section, found through the section ID you pass to it.

When to use it
retire a seasonal section when the season closes in your planning file.
Watch out
the field accepts several IDs, so one mapping mistake can clear more than intended.
6

Create Element

Action

In Zapier“Creates a new element.”

Inserts a fresh element into your Plate account, filled with values mapped from the step before.

When to use it
add a block of copy each time a new customer quote is approved in your CRM.
Watch out
a new element is easy to create and easy to forget; pair the flow with a clean-up rule.
7

Create Post

Action

In Zapier“Creates a new post.”

Adds a new post to your Plate account from data coming out of another tool. Zapier features it among the main Plate actions.

When to use it
turn each approved row of an editorial calendar into a draft post.
Watch out
the Zap creates a post on every run, so a trigger that fires twice gives you two posts.
8

Create Section

Action

In Zapier“Creates a new section.”

Builds a new section in Plate. Useful when the structure of your content grows with your activity rather than staying fixed.

When to use it
open a section for each new product line recorded in your catalogue tool.
Watch out
no field is flagged as required here, so read what the step asks in the editor before mapping.
9

Update Content Object

Action

In Zapier“Updates a content object.”

Amends a content object you already have, located by its content object ID.

When to use it
keep an event entry in Plate in step with changes made in the booking tool.
Watch out
the ID comes from somewhere: a Search Content Object step, or a value saved by an earlier Zap.
10

Update Element

Action

In Zapier“Updates an element.”

Edits an element in place, pointing at it through the element ID field, which is required.

When to use it
swap opening hours on a contact block when the team updates them in a shared sheet.
Watch out
an empty mapped value can overwrite good content, so check the test result before you publish.
11

Update Post

Action

In Zapier“Updates a post.”

Rewrites an existing post. It needs the post ID, and accepts one or several of them, which is why a Search Post step usually comes first.

When to use it
refresh a product page when the price changes in your shop back office.
Watch out
several IDs means several posts changed in one go, so test on a single one first.
12

Update Section

Action

In Zapier“Updates a section.”

Changes a section that already lives in Plate, identified by its section ID (one or more).

When to use it
rename a section when the matching category is renamed in your inventory tool.
Watch out
without a Search Section step before it, you need a stable ID stored somewhere else.
Searches

Plate searches

6 search steps look for data that already exists in Plate, so a later step can use it.

A search hands an existing item to the next step. In the editor, Plate's searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not the one you expected.

1

Search Authentication Object

Search

In Zapier“Search for an authentication object by a filter.”

Looks up an authentication object in Plate by a filter, so a later step can use what it returns.

When to use it
retrieve the access record a following step depends on, rather than hard-coding it.
Watch out
this one has no find-or-create variant, so a miss simply stops the Zap unless you allow empty results.
2

Search Content Object

SearchFind or create

In Zapier“Search for a content object by a filter.”

Finds a content object through a filter and passes its ID to the next step. The editor also shows Find or Create Content Object: same search, with the create box ticked.

When to use it
locate an event entry before updating it.
Watch out
the find-or-create line is not a separate step; it creates only when the search comes back empty.
3

Search Element

SearchFind or create

In Zapier“Search for an element by a filter.”

Tracks down an element by filter. Its find-or-create twin, Find or Create Element, builds the element when nothing matches.

When to use it
fetch the contact block you want to refresh before Update Element.
Watch out
whether the filter wants an exact value or something close is Plate's rule, not Zapier's; test a near miss.
4

Search Post

SearchFind or create

In Zapier“Search for a post by a filter.”

Returns the post that matches your filter, with the ID that Update Post or Delete Post need. Find or Create Post is the same search set to create the post when it is missing.

When to use it
any flow that edits an existing article.
Watch out
several matches keep the first by default, which may not be the one you meant.
5

Search Attachment

Search

In Zapier“Search attachment by id”

Fetches an attachment by its ID, the one required field. It is the only Plate search that works on an exact identifier rather than a filter.

When to use it
pull a file already stored in Plate to send it on to another tool.
Watch out
without the ID from an earlier step, it has nothing to look for.
6

Search Section

SearchFind or create

In Zapier“Search for a section by a filter.”

Spots a section through a filter. Ticking the create box turns it into Find or Create Section, which opens the section when none is found.

When to use it
make sure a category section exists before adding posts to it.
Watch out
a loose filter plus the create box can spawn duplicate sections.

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 and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing item.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass all matches on at once.
When it breaks

When a Plate Zap breaks

Zapier ties no help article and no rate limit to Plate. What fails is the general machinery, and it hits content flows in specific ways.

Four cases to check before publishing. If one already bit you, the Zapier troubleshooting page is the next stop.

  • The search finds nothing and the Zap stops

    On default settings, a Search Post that comes back empty halts the run and skips the update. Allow empty results or tick the create box.

  • Old content is never touched

    A Zap only reacts to what happens in the starting app after it is switched on. Rows or records from before stay unprocessed.

  • A bulk import gets held back

    When the starting app suddenly returns a huge batch, after a migration for instance, Zapier's flood protection can hold it back.

  • The search step is refused on free

    A search makes the Zap multi-step. On the free plan you only get one trigger and one action, so Search Post plus Update Post needs a paid plan.
Need help

Need help automating Plate with Zapier?

A person reads every message.

FAQ

Plate Zapier integration: FAQ

01Is the Plate Zapier integration free?
Yes, within the limits of the free plan. Plate is not a premium app, so you can connect it without paying. The free plan gives you 100 tasks a month and Zaps of two steps: a trigger from another app and one Plate action. That covers Create Post from a sheet. Anything that needs a search first, like updating an existing post, makes the Zap multi-step and requires a paid plan.
02How many tasks does a Plate Zap use?
One per successful action. The trigger, which always comes from another app, costs nothing, and a failed action is not billed. A Zap that only runs Create Post uses one task per run. A Zap that runs Update Post and then Delete Element uses two. So count your Plate actions per run and multiply by how often the starting app fires to estimate your monthly use against the 100 tasks of the free plan.
03Does the Plate integration work in real time?
It depends on the app that starts the Zap, because Plate has no trigger of its own. If that app has an instant trigger, it tells Zapier when the event happens and the Zap starts right away on any plan. If its trigger polls, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can also change that interval or run a check by hand from the editor. The Plate actions then run straight after the trigger.
04What does it take to connect Plate to Zapier?
A Plate account and access rights on the content the Zap will change. In Zapier you open Apps, click + Add connection, pick Plate, sign in and grant access. If you work on a site owned by someone else, check that your login can read and edit what the Zap will touch. Remember too that every update and delete action needs the ID of an item that already exists in Plate.
05Why does Update Post fail with no post to update?
Because it never got a valid post ID. Update Post requires one, and it usually comes from a Search Post step placed before it. If that search finds nothing, the default setting stops the Zap there. Check the filter on a real test item, decide whether an empty result should stop the run, or tick the create box to turn the step into Find or Create Post. Then test again.
06What if the Plate operation you need is missing?
Then the integration cannot do it directly. Zapier offers 12 Plate actions and 6 searches, all aimed at posts, sections, elements and content objects, and no trigger at all. Anything that should react to a change inside Plate is out of reach from Zapier today. For those cases, the change has to be detected in another tool, or the flow has to stay manual for now. A specialist can help map out that route.
07Zapier, Make or n8n for Plate?
Judge it on two criteria. First, the starting point: Zapier has no Plate trigger, so your flows always begin in another app. Second, the shape of the flow: on Zapier, the useful update scenarios need a search plus an action, which means a paid plan, and each successful action is billed as a task. Weigh those two points against what the other platforms offer for Plate before committing. Your volume decides the rest.
Same platform

Other docs you might need on this stack.

Browse all integrations