Overview and Authentication of the TicketSignup Zapier App

Modified on 28 September

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


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.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article