Zapier

connecting regpack to other tools with zapier zapier is a tool that connects apps together and automates tasks between them by connecting regpack to zapier, you can automatically send data between regpack and thousands of other tools your organization already uses with no code or low code common examples of what you can do automatically add a new registrant to a google sheet when they complete registration send a slack or email notification to your team when a payment is captured create or update a contact in your crm when someone registers add registrants to a mailchimp or constant contact audience automatically what you need before getting started api admin license on your regpack account required to connect regpack to zapier if you are not sure whether your account has this, contact support\@regpacks com your own zapier account you will need this to build and manage your zaps; regpack does not manage this on your behalf access to the regpack zapier app the regpack app on zapier is currently private; it is not publicly listed in zapier's app directory to get access, contact support\@regpacks com and request an invitation once your api admin license is confirmed, regpack will send you an invite, and you can begin building your zaps how to get set up step 1 — request access contact support\@regpacks com and ask to be invited to the regpack zapier app once confirmed, you will receive an invitation email from zapier step 2 — connect your regpack account in zapier when you add regpack as an app in zapier, you will be asked for three credentials from your regpack account you can find these in admin management by clicking on your api admin and opening up their profile field where to find it api id number on the top right (e g 12345) api admin email the email address of your api admin api token listed as api token (note if you update your token, you will need to reauthenticate wherever you are using it) enter these when prompted to authenticate zapier will verify the connection before letting you proceed step 3 — build your zap once connected, you can create zaps on your own in zapier a zap is initiated by a trigger (something that happens in regpack or your other software) see the sections below for the full list of available triggers and actions step 4 — turn your zap on after testing your zap confirms it is working correctly, turn it on from that point, the automation runs in the background without any action needed from you setting up a trigger (what starts your zap) for the purpose of this article, we will use the example of a zap triggering due to an action in regpack triggers in regpack are powered by webhooks when something happens in regpack, regpack sends a notification to zapier with the relevant data, which then starts your zap available triggers trigger when it runs example use case user registered when a new user is created in your project (before forms are filled out) for family projects, this is the parent/head unit only add new registrants to your crm the moment they sign up status update when any user's status is changed in the users tab send a slack notification when a registrant's status changes to "approved" form submitted when a user successfully submits a form create a task in asana when a specific form is submitted payment event when any payment related event occurs payments, refunds, cancellations, chargebacks the event type is included in the data zapier receives track refunds in a google sheet payment issued when a payment is actually made (by a user or processed by an admin) update another system when a payment clears cart event when a cart event happens send an internal notification when someone's cart changes how to connect a webhook trigger to regpack when you select a trigger in zapier, zapier will give you a webhook url here is how to activate it in regpack copy the webhook url from zapier in regpack, go to project settings → webhooks create a new webhook with the appropriate trigger and paste the zapier url perform the triggering action in regpack once (for example, submit a test form or change a user's status) zapier will receive the test data once it appears, you are ready to build the rest of your zap {% hint style="info" %} you won't see the webhooks tab in regpack unless your account has an api admin set up if it's missing, upgrade to a package with an api admin, purchase an a la carte api admin {% endhint %} setting up an action actions are steps in your zap that do something in regpack — typically later in the zap, after a trigger from another tool for example a new contact is added in your crm → create the user in regpack automatically available actions action what it does example use case create user creates a new user in a regpack project add a registrant to regpack when they fill out a form in another tool create child creates a child/sub unit under a parent user (requires the parent's email) add a student under an existing parent account automatically update updates values in a user's form fields change a field value when an event fires in another system set status adds or removes a status for a user mark a user as "trained" when they complete a course in your lms getinfo retrieves details for a single user look up a registrant's data to use later in your zap get user list retrieves all users in a project sync your full registrant list to a google sheet add email creates a new email in a project automatically create an email template in regpack from an external source what you will need for actions most actions require your project id , which you can find in the regpack backend next to your project name some actions (like create child and getinfo) also ask for a user id; this is a clogin id in regpack troubleshooting if a zap fails zapier logs all failed runs and can send you error notifications check your zapier account's task history for details most failures are caused by a change in account settings or a temporary issue in the connected app what regpack support can help with regpack support can assist with issues related to the regpack app within zapier — for example, if a trigger is not firing as expected, your api credentials are not authenticating, or you are not seeing the webhooks tab in your project settings regpack support cannot assist with the design of your zaps or with issues in third party apps you have connected for those, refer to zapier's own help documentation or the support resources for the other app if you need help with the regpack side of your setup, contact support\@regpacks com