Zapier is an integration platform that is used to glue APIs together. The primary objective of companies using Zapier is to allow business users to build workflows and actions across platforms that are disconnected from each other. One example is sales users who need an email platform like Hubspot to automate lead generation from a CRM like Salesforce. A current use case for Zapier would be to integrate 3rd party popup providers with ReSci.
On Zapier there are triggers and creates. A trigger is a source of data. A create destination of data from a trigger. A Zap is a mapping between sources and destinations.
This article covers:
The ReSci app is currently in Beta and is invite only. Please email firstname.lastname@example.org to request access. Please include the email of the person who will be creating the "Zap" in the request. We will respond with the ReSci API key (required below) after we have sent the invitation for access.
You need a trigger with user information to setup a Zap with ReSci. Please see the Usage section below for popular email capture providers that can connect to ReSci with Zapier.
After you have been invited to use the ReSci app and you have chosen a source for user capture, you can create a Zap (For details on creating a Zap, see this article):
- Select the ReSci app as an "Action."
- After setting up the trigger, choose the "Create User" Action in our app, then click Save + Continue.
- Click Connect.
- Paste in the ReSci API key then click Yes, Continue.
- Click Save + Continue.
- Map the fields from the trigger to ReSci
- Click Continue.
- Verify the test and click "Send Test to ReSci."
- Click Finish after the test succeeds.
- Name your Zap.
When you turn the Zap on you are done!
Data and APIs
Currently, the ReSci Zapier app will access our User create API. Below is a table of how the Zapier app leverages the ReSci API for the "Create User" action.
In addition to the fields below, Custom Attributes can also be passed. Please ensure your account is properly configured to support custom attributes before sending this data via Zapier.
|Zapier <> ReSci Create User||Required||Default Value||
|id||yes, but optional||md5 hash of email||
If the ID is not sent, the Zapier app will automatically set the ID to the MD5 hash of the email
User's full name (first and last).
The source of the user's registration typically used for user segmentation
|birthday||no||format must be YYYY-MM-DD|
|send_transactional_welcome||no||true||When true, an email is sent to new users when there is an available template in the Welcome stage. When false Welcome emails will not go to new users. The default for this setting is true.|
Currently, the primary use for the Zapier ReSci app is for email capture. Popular email capture forms that can be integrated with the ReSci app are:
To setup a Zap, please see the Setupsection above for a step by step walkthrough
Typically, when capturing emails for new users you will want to send a welcome email. ReSci supports this with our welcome stage. Please see this article for welcome stage setup.