A test trigger is a regular trigger with a special responsibility. The test trigger is the trigger Zapier will use to verify the authentication credentials users provide when they first attempt to access your API through Zapier. If your API returns a
2XX status code, we will assume the credentials are valid. Anything else (or an empty response that isn't a
204), and we will assume the credentials are bad.
You can only mark one trigger as the test trigger. A test trigger can be made for any endpoint in your API that:
Some examples of good endpoints to use for the test trigger:
/pingthat is meant solely to test authentication
In your app, you'll need choose a trigger that performs a "simple test" when its Polling URL is used to access an endpoint that requires valid authorization/credentials.
If your trigger is intended to be solely used for authentication testing, then you can mark it hidden.
Important make sure that the test trigger doesn't have any "Required" trigger fields (because they'll be empty when we perform the auth test)
When your test trigger fails, a message will be displayed to the user "App returned (400) Error and said nothing" or something similar. This is constructed from the response status code and status message returned from your endpoint, along with a message from the response body, like so:
App return (
The message is interpreted from the response.body as such:
To select your test trigger, use the button "Manage Trigger Settings":
Scroll down to the bottom of the page, and select the appropriate trigger: