How to configure a Zapier integration
Zapier connects Leat to more than 7,000 apps without writing code. When a contact is created or updated, a voucher is created or redeemed, or a contact receives points or a reward, we send the event to Zapier so your zap can act on it: add the contact to your CRM, write a row to a spreadsheet, send a message to your team, whatever the zap does next.
Note: this is no longer set up through a private app. Zapier is its own integration in the marketplace, and it uses client credentials rather than a personal access token. If you set this up before, see If you connected Zapier with a personal access token at the bottom.
Install the integration
- In the dashboard, go to Apps, then Integrations.
- On the Marketplace page, search for Zapier and open it.
- Click Install. You land on the Zapier integration page, which has three tabs: General, Auth and Triggers.
Create your client credentials
- Open the Auth tab.
- Click Create.
- Copy the Client ID and the Client Secret. The secret is shown once, so store it somewhere safe before you close the dialog. The client ID stays visible on the Auth tab afterwards.
Connect Leat in Zapier
- Log in to Zapier and add the Leat app. In Zapier the app may still be listed under its former name, Piggy.
- When Zapier asks for credentials, enter the client ID and client secret you just created.
- Build a zap with a Leat trigger and turn it on.
The triggers you can start a zap with
- Contact created
- Contact updated
- Voucher created
- Voucher redeemed
- Reward received, when a contact receives a loyalty reward
- Points received, when a contact receives loyalty points. In Zapier this trigger may still be called Credits received.
See what is running
The Triggers tab lists every Leat trigger a zap has subscribed to, with the event, the Zapier URL we send it to and when it was created. The tab stays empty until a zap with a Leat trigger is turned on in Zapier, so if you have built a zap and see nothing here, check that it is switched on.
Deleting a trigger stops us sending that event. The zap itself stays in Zapier until you turn it off there, so the tidy way round is to turn the zap off in Zapier first.
Rotate or revoke access
Both live on the Auth tab, next to the credentials:
- Rotate secret gives you a new client secret. The old one stops working immediately, so paste the new one into Zapier straight away or the zaps stop running.
- Revoke access blocks every incoming API request from this integration right away. Reinstate access undoes it. Use this if you think the credentials have leaked.
The Auth tab also shows when the credentials were last used, which is the quickest way to tell whether Zapier is actually reaching us.
If you connected Zapier with a personal access token
Older setups used a private app and a personal access token. Those keep working for now, but install the Zapier integration from the marketplace and switch the connection in Zapier over to the client ID and client secret. After that you can delete the private app you created for Zapier.
Still stuck
If a zap does not fire, check in this order: the zap is turned on in Zapier, the trigger shows up on the Triggers tab, and the status on the Auth tab is active rather than revoked. Problems with the zap itself, or with an app on the other side of it, are best taken to Zapier support.