Job Dynamic Custom Fields

when enabling your integration for a job, custom fields may not always be enough you might need to request additional data that depends on previously submitted information this can be achieved with a two step flow first, set up the job custom fields docid\ nrlu8ie2ibr3r4z3kc7pf once that primary form is submitted, jobylon ats will forward them to you as per usual flow you can then process this data and build a secondary form that requests additional fields based on the information submitted from the first form please note that dynamic custom fields are not automatically available to start using them, you must first contact your jobylon contact workflow static form when using dynamic custom fields , once the user submits the first form, jobylon ats will immediately send a job webhook to the partner, as described in webhooks docid 5pnq0b83gzrhxrdqhk wl this webhook will include, among other fields, the following name content description event type job webhook type identifier action create/update webhook action settings object object containing the user answers to the first (static) form dynamic settings null object containing the user answers to the second (dynamic) form null in the first webhook jobylon expects an immediate response to this webhook the response must return a 200 status code and a json including a url where jobylon can access the dynamic fields response example { "dynamic config url" "https //www example com/dynamic form fields" } the ats will attempt to access the returned url up to 5 times , with a 3 second interval between each attempt once the form is available, jobylon ats will show it to the user if the form is still unavailable after the fifth attempt, an error message will be displayed to the user and the flow is interrupted dynamic form jobylon expects the dynamic form to be present in the returned url, in json format all the fields must be within the fields object and follow the exact same structure as shown in api reference/openapi docid\ h5isza0jmnesiexde3i5f for job config for example { "fields" \[ { "name" "string", "label" "string", "required" true, "type field" "number", "metadata" { "min value" 0, "max value" 0, "default value" 0 } } ] } once the user saves the secondary (dynamic) form, jobylon ats sends a second webhook to the partner with the following fields name content description event type job webhook type identifier action dynamic update webhook action settings null object containing the user answers to the first (static) form null in the second webhook dynamic settings object object containing the user answers to the second (dynamic) form