Zapier - Overview and Authentication

Modified on 01 October

TABLE OF CONTENTS


Overview

RunSignup has always supported an open API that is free to use to extract data from RunSignup in order to populate external systems such as CRMs and Donor Management platforms.  With the introduction of the RunSignup Zapier App, there is now a simpler approach to connect RunSignup to other popular applications. We have partnered with Sidekick Solutions as our recommended integration partner who can provide standard integration packages to meet your needs.  However, if you want to use our Zapier RunSignup app to connect your own integrations, this solution guide will get you started.  The RunSignup Zapier app is free to use (Zapier platform fees may apply).


The RunSignup Zapier app includes the following components:


Users may implement Zaps with any trigger, action, and/or search available in the app. The app is not task or Zap limited. Meaning, users may build as many Zaps and process as much data through the app as is allowed in the user’s Zapier plan (i.e., task and Zap count). 


The RunSignup Zapier app may be used by Partners and Event Directors. 

  • Partners will be able to authenticate and configure flows for any Race the Partner is provisioned access to. 

  • Race Directors will only be able to authenticate and configure flows for the single Race that access has been provisioned for.


RunSignup Pre-Requisites

In order to use Zapier you must be registered with RunSignup as an API Caller and have API keys that the RunSignup Zapier app will request during the authentication step.


First register as an API Caller

  1. Login to your RunSignup account and navigate to the API Caller Registration Page

  2. Review the API Developer Contract and click the box to acknowledge and agree with the terms.

  3. Click the Agree to Contract button

  4. Complete the form including a description of your intended usage (e.g. Zapier integration with CRM like Salesforce, Hubspot, etc) and click Create API Caller

  5. Obtain your  API caller token (`rsu_api_reg`) and registration secret (`X-RSU-API-REG-SECRET`)

  6. Record your API caller secret in a secure location, this is the only time it will be displayed.


Next obtain your API Keys


  • RACE DIRECTOR: To generate an API Key/Secret, go to the race Dashboard and click on Race > Secure Access/Info Sharing. Scroll to the bottom of the page to generate an API Key/Secret.

  • When an API Key is generated, the API Secret is displayed/accessible only until you log out. Once you log out, the API Secret will no longer be accessible. Save and store the API Key and Secret in a secure location.



Authentication

The RunSignup Zapier app is public in Zapier’s app directory. Users may search for and select the RunSignup application and do not need an invite URL. 


The RunSignup Zapier app may be used by Partners and Race Directors. 

  • Partners will be able to authenticate and configure flows for any Race the Partner is provisioned access to. 

  • Race Directors will only be able to authenticate and configure flows for the single Race that access has been provisioned for.


Follow the steps below to complete the authentication of the RunSignup application (only relevant for Private versions of the app):


  • After logging into Zapier, click the blue +Create Zap button. 


  • Search for and select RunSignup.


  • Select any trigger event and click Continue.


  • Click the blue Sign In button. 


  • A pop-up window will open and prompt entry of authentication credentials. 


  • Enter the API Key, API Secret, API Caller Token and API Caller Password as prompted


  • Click Yes, Continue.



Triggers


Zapier triggers are an easy way to allow you to get new data from your API.


We have overviews of three common triggers that may be useful for your event:

  • new participant registration triggers.
  • new registration add-on triggers 
  • new donation triggers
  • removed participant registration triggers


You can read more about these triggers here.