If you are interested, please drop us an email to receive a private invitation to the app. The aim of a private beta is to collect directional feedback from those of you who show an active interest.
For the initial release, we have set up triggers only. A trigger means that when something happens in Elastic Path, you can send that information to Zapier and then use it in another application. An example of this might be adding a Elastic Path customer to a MailChimp list when they pay for an order.
There are a relatively small number of triggers available in this release, but they cover the most popular use cases. If there’s a trigger you would find useful, that isn’t present, please let us know!
Let’s briefly run through how to set Zapier up, so you have a sense of the work involved. Zapier have a fantastic guide which we recommend reading before you begin.
First, once you have accepted your private invitation, you will be brought to the Zapier editor and Elastic Path will already have been selected as the trigger app.
You can then choose the actual trigger that you need to use, you have the choice of:
- New Order
- New Product
- Order Shipped
- Order Paid
- Order Refunded
You will then be asked to connect your Elastic Path account. For this you will need your client ID and client Secret. Both can be found by logging into your Elastic Path dashboard.
Zapier will then test the access to this account, and you can move on to testing the step itself. For whatever trigger you have selected, you should try and make sure that you already have some data in Elastic Path that meets the requirements of that trigger.
For example, if the trigger is Order Paid, you’ll want to have at least one order in Elastic Path that is already paid for. However, don’t worry if you don’t have an order, Zapier will fall back to some default fields and you can skip the test. Do be aware though, that it’s always best to use fresh data as it can pull in the most up to date fields.
You will then be prompted to add an action step. This is essentially the same process as the trigger step, with an extra step for setting up your template. This means that you map the data received by the trigger, into the fields available in your chosen action.
Once you have done so, you can test the action, and put the Zap live!