Overview and Authentication of the TicketSignup Zapier App

Modified on 10 December

TABLE OF CONTENTS


TicketSignup Zapier App

Solution Guide

Client: RunSignup (TicketSignup)

Developer: Sidekick Solutions LLC

Current Release: v1.1.1

Note: The app version presented in this guide includes the storage key to support trigger events that are caused by bulk import in TicketSignup

  • Includes branch for non-storage version

  • Can be copied to RSU repo on preference


Overview

The TicketSignup Zapier app includes the following components:

  • Triggers

    • New Event Ticket

  • Actions

    • None at this time.

  • Searches

    • None at this time.


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 TicketSignup Zapier app may be used by Partners and Event Directors. 

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

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


Authentication

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


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

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

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


Follow the steps below to complete the authentication of the TicketSignup application:


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


  • Search for and select TicketSignup.


  • 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 and API 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.



  • EVENT DIRECTOR: To generate an API Key/Secret, go to the event Dashboard and click on Event > Secure Access > API Keys to generate an API Key/Secret.


  • Click Yes, Continue.