Zapier

use the zapier integration to connect ashby to a wide range of apps and create zaps that automate your workflows this article explains how to connect ashby to zapier and how to build a zap using ashby as either the trigger app or the action app permissions & prerequisites you must be an organization admin to access the zapier integrations tile and to generate api keys in ashby connect ashby to zapier in zapier, create a zap and select ashby as the trigger or action app a zap requires at least one trigger and one action when prompted to authenticate, provide an ashby api key you can create the key either from the zapier integration listing or the api keys page copy the key immediately ashby shows the full value only during setup and cannot display it again after the wizard closes paste the key into zapier and click connect api key permissions and endpoints below you'll find a list of ashby triggers and actions in zapier and the permissions required for the api key used to create the connection initial setup — required for every connection scope candidates\ read apikeys\ read triggers trigger scopes required application changed stage candidates\ read, apikeys\ write candidate applied candidates\ read, apikeys\ write candidate hired candidates\ read, offers\ read, apikeys\ write interview schedule created candidates\ read, interviews\ read, apikeys\ write interview schedule updated candidates\ read, interviews\ read, apikeys\ write job posting published jobs\ read, apikeys\ write job posting unpublished jobs\ read, apikeys\ write opening created jobs\ read, apikeys\ write offer created candidates\ read, offers\ read, apikeys\ write offer updated candidates\ read, offers\ read, apikeys\ write offer deleted candidates\ read, offers\ read, apikeys\ write searches / actions search or action scopes required create candidate candidates\ write, hiringprocessmetadata\ read, organization\ read update candidate candidates\ read, candidates\ write, hiringprocessmetadata\ read, organization\ read create candidate note candidates\ read, candidates\ write consider candidate for job candidates\ read, candidates\ write, jobs\ read change job consideration stage candidates\ read, candidates\ write, jobs\ read, hiringprocessmetadata\ read create opening jobs\ write, jobs\ read, organization\ read update opening jobs\ write, jobs\ read, organization\ read generate report on ashby reports\ read find candidate candidates\ read find job jobs\ read find opening jobs\ read find job consideration candidates\ read, jobs\ read create a zap with ashby create a zap with ashby as the trigger app to create a new zap, click create , then zap workflow in zapier a zap begins with the trigger, so click in the trigger field and select ashby as the trigger app select the trigger event this determines when the zap runs select your ashby connection, or connect your ashby account in the account field after you configure the trigger, you can test it the test fetches a record matching the conditions you set, which is useful for mapping data in the action step and for confirming you set the correct conditions creating a zap using ashby as the trigger app create a zap with ashby as the action app after you configure your trigger and any additional conditions on your zap, you can add ashby as the action app set the app field to ashby select the action event this determines what happens once the zap is triggered and any conditions you set are met select your ashby connection, or connect your ashby account in the account field when testing, you can map data from the trigger app where possible, then confirm the zap works as expected before you publish it creating an integration using zapier as the action app faqs if i create an api key in the zapier integrations tile in ashby, what permissions does that key come with? by default, the api key ashby generates does not have endpoint permissions allocated to adjust the api key permissions navigate to admin > integrations > api keys click your zapier api key to open the api key settings use the endpoint permissions and other permissions checkboxes to set the permissions for the api key click save to confirm