Plate Integration on Zapier

Overview

In this document you will find all the information needed to get started with the Plate Integration on Zapier. Zapier is used to connect a wide range of applications with each other in the easiest way and from now on a Plate integration is available on Zapier as well!

Zapier is fairly easy to use, you create zaps which consist of triggers and actions. The trigger makes the action get executed, as the creator of the zap you define the trigger and action. An example of a fully working zap is the scenario where if something gets posted on Facebook, a post in Plate will be created with the same title. This is a very straightforward zap but Zapier is very modular, it can be used for the most complex workflows. Get creative!

Getting started

After creating an account on http://www.zapier.com your first zap can be created. This guide will only cover the Plate integration, to learn more about Zapier and how to set up zaps it’s best to check out their Zapier page.

Connecting Plate and Zapier

In step 2 you will be asked to connect Plate with Zapier, this is done by creating an API integration and a key pair. Connections created before can be reused. To make a new connection a private and public key is needed, these can be created in the Plate dashboard under the tab “API Integrations”.

Notes:

• The tab “API Integrations” is only visible if your Plate account is set to advanced.

• Don’t forget to set your integration authorities correctly.

• Don’t forget to activate your key pair.

Search Action

These actions are used to filter posts/sections/elements. It has the input fields “Field on which to filter” and “Value where to filter by”, if filled in correctly it will return a list of the filtered posts/sections/elements. The options “Should This Step Be Considered A "success" When Nothing Is Found?” and “Create … if it doesn’t exist yet?” are both optional and are selected at your own choice.

Update Action

This action is not very different from the Create Action, it has an extra field where the ID(s) of the to be updated posts/sections/elements has to be filled in.

This action can be combined with the Search Action. To do this create a multi-step zap with the Search Action following the Update Action. After setting up the Search Action map the “Filtered … - Filtered … Array - ID” data from the Search Action to the … ID(s) field in the Update Action. Now the ID(s) will get filled in automatically by the Search Action.

Releases

Statuses: To do / In progress / Blocked / Waiting for feedback / Done

Constraints

Other documents

• https://docs.google.com/document/d/1OlNKF4FzhToAHqqdh0KJedFD-OigT4PXRwgKaH2Wu1g/edit?usp=sharing