capabilities.work

Send a Candidate Survey and Collect Submissions

A 4-step recipe with Ashby. We can help you get access.

Recipe · 4 steps

Send a Candidate Survey and Collect Submissions

with Ashby

Resolve a survey form, request it from a candidate, and list submissions.

  1. List the organization's survey form definitions so a real form id can be resolved rather than guessed.
  2. Read the chosen survey form definition to confirm it exists and to capture its structure before sending it to a candidate.
  3. Send the survey to the candidate against a specific application. All three ids are bound together here, which is what lets the response be attributed to the right hiring context later.
  4. Pull survey submissions of the requested type. Submissions arrive asynchronously as candidates respond, so this returns whatever has landed so far rather than the just-sent request's answer.
What you'll need to have ready
  • candidateId: The id of the candidate to survey.
  • applicationId: The id of the application the survey relates to.
  • surveyFormDefinitionId: The id of the survey form definition to send. Resolve this from the listSurveyForms step output.
  • surveyType: The type of survey submissions to fetch (CandidateExperience or Questionnaire).
For your developer

Arazzo workflow ashby-hq:survey-request, 4 operations: surveyFormDefinitionList → surveyFormDefinitionInfo → surveyRequestCreate → surveySubmissionList. Specs on APIs.io.

More recipes with Ashby

Advance an Application to a Named Interview StageArchive an Application with a ReasonCreate an Application on a JobCandidate Intake with DeduplicationAttach a Resume to a CandidateTag a Candidate by Tag TitleDefine a Custom Field and Set Its ValueRequest and Submit Interview FeedbackSchedule an Interview for an ApplicationCreate a Job and Open It