How do I use Shared Zaps?

Here is an example of how you can use Shared Zaps with Trainerize. All of the Shared Zaps will follow steps similar to those outlined below.

Step 1

Choose the shared Zap that you wish to setup. In this example we're using the Stripe payment to Trainerize active client Zap. 

Click on "Use This Zap"

Step 2

A window will pop-up with a more detailed description of what this Zap will do. At the very bottom is a button to continue and "Make This Zap". Click on "Make This Zap" to continue.

Step 3

The next step will be to connect your Stripe account. Click on "Connect". Using your Stripe username and password, login to Stripe. 

 

Step 4

Using the provided link to Stripe, find your API key given in your Stripe account. Copy and paste the API key into the available text field and click "Yes, continue". 

 

 

Step 5

If you have a Trainerize account already connected you can click "Use this one" or if you don't you will be prompted to connect a Trainerize account by adding in the account owner username and password. You must be the account owner to create or use Zaps.

 

 

Step 6

In this step, all of the fields are pre-populated for you. There is no need to change the fields. Click "Save and finish" to complete the Zap.

 

Step 7

You have now completed setting up your first shared Zap! Now you can begin testing to ensure it is working properly. Click "Test out my new Zap". 

 

 

Step 8

Following the directions in this window, open Stripe, create and save a new customer, then return to the window shown below and click on "Continue and fetch the customer".

 

Step 9

In the final step, as long as all of the client information has been entered into Stripe correctly this will succeed. The client username from the client credit card is required to create the account in Trainerize. it does not pass the client credit card payment information to Trainerize!

Your shared Zap has now been enabled. Stripe payments will now create an active client in Trainerize!! 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.