Using Zapier, it is possible to trigger zaps that fire based on user events, including registration and payment updates. You can use this to be notified whenever a new user joins your community through Pico or to send payments to another platform you use that is also connected to Zapier.
There are separate events to subscribe to so that you can control the frequency of zaps according to your needs.
Pico sends two main event types to Zapier: Contacts and Payments. Within each of those, you can specify if you'd like to trigger zaps based on event type.
Connecting to Zapier
Our connection with Zapier is currently in Beta, but you'll be able to find it by searching for Pico in the list of available apps within Zapier.
If this is your first time creating a Zap with Pico, you’ll need to connect your account using the credentials we provide. You can generate your credentials by navigating to the Apps section of your Pico Dashboard. In order to do so, click the Apps icon on the navbar located on the left side of your screen.
Find Zapier on the Apps page and click Install.
A modal will appear as the result of this action. If you have credentials already, they will be listed in to copy. If not, generate an API key using the button that appears instead.
When connecting your account, you will use these credentials as your username and password to log in and connect the accounts.
Creating a Zap based on Pico Events
Now that you're connected, it's time to create a Zap. When creating a Zap, you can select Pico from a list of Apps, and then select the event. In this case, we’ll be demonstrating how to get a Zap for when a new payment is created.
Enter a name for the Zap. We named it "New Subscription."
Search for and select Pico.
Select the event type you want. We're moving forward with Payment Created.
Available Zap Options
New Contact Created (contact.created) - A free user has registered on your site.
Contact Updated (contact.updated) - A user made a change to their account, including changing selections on items like newsletter preferences.
Payment Created (payment.created) - A user has made a purchase through Pico such as a subscription purchase, a donation, a gift, etc.
Payment Failed (payment.updated) - Pico attempted to charge but was unable to. This is most common for recurring subscriptions where a credit card may have expired.
Payment Deleted (payment.deleted) - A user cancels a subscription. Note: This also fires when users switch plans because they are cancelling one plan to join another.
⚠️ Note: When a contact is created in Pico, it will fire two events. First, it will fire off the Contact Created event which sends over the basic information for the user so that a contact can be made in the connected application. Then, it will fire shortly afterword a Contact Updated event which carries the information for the user such as newsletters and additional information. Some systems require creating a contact before adding data. You can attempt to use the Contact Updated event to create and update the information on a user in one go if your connected application supports this.
Testing the Zap
To test the Zap, we need to configure this Zap with sample data. You can generate sample data by creating user accounts on your site and/or landing pages or by using the testing buttons on the Apps page in Zapier's dashboard.
Creating the Zap
Once you have sample data, you can choose the output by using any app connected to Zapier. Here's an example Slack notification:
We are only displaying a small section of the data available in Zapier that Pico has sent so the Slack notification is simple. The notification is a combination of typed values like "User" and data from Zapier like "Username," "Recurring," and "Membership."
For a complete list of the possible data values, review the Pico Merge Fields.
Here's how the message looks in Slack:
Available Zap Templates
Creating Zaps in ConvertKit
Pico has pre-built Zaps for ActiveCampaign, CampaignMonitor, and ConvertKit. They can update basic information for contacts including Email, Name, and Newsletter. Syncing other contact properties that Pico records will require that you first add the fields to your account. In the example below for ConvertKit, Registration Date, Membership, and Billing Period End were added. They are then available to use in Zaps.