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. From 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 in Beta, but you'll be able to find it by searching for Pico in the list of available apps.
Creating a Zap based on Pico Events
Now that you're connected, it's time to create a zap. When creating a Zap, you’ll be able to select Pico from a list of Apps, 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've selected "New Subscription".
- Search for Pico.
- Select Pico.
- Select the even type you want. We're moving forward with Payment Created
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 your integrations page.
If you have credentials already, they'll be listed in the Zapier section 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.
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, which could be 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, the first being 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, a Contact Updated event is fired shortly afterward 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 create user accounts on your site / landing pages, or by using the testing buttons on the integrations page of the publisher dashboard in the "webhooks" section.
Creating the Zap
Once you have sample data, you can choose the output, 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 CRM 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. These 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 has been added. These are then available to use in zaps.