FlowmageDocs

Update vacancy

BetaChanges data

Changes a Carerix vacancy that already exists.

Settings

SettingWhat it is
ConnectionRequiredThe Carerix connection the step signs in with.
Vacancy idThe _id of the vacancy to change. Fields left empty are left alone. Carerix does not support patch semantics: a list field you send — attachments, skills, educations, phone numbers — REPLACES that whole list with what you send. Leave a list field out to leave it alone.
Job titletext
Company idtext
Owner idtext
StartsCarerix dates are yyyy-MM-dd HH:mm:ss in Amsterdam time, never ISO-8601.
Endstext
Deadlinetext
Work citytext
Requirementstext
What you offertext
The vacancy texttext
Other fieldsAny other CRVacancyRequest field, by name — docs.carerix.io/graphql has the full list. Dates are yyyy-MM-dd HH:mm:ss in Amsterdam time, and a list value is set by its code with a _lookup.
Technical details
KeyValue
connectiontexta connection id from `requires.connections` (provider `carerix`)
vacancyIdtext
jobTitletext
companyIdtext
ownerUserIdtext
startDatetext
endDatetext
deadlinetext
workCitytext
requirementstext
offerInformationtext
vacancyInformationtext
extraFieldsobject (any keys), by default {}

Output

FieldType
vacancyobject
Sample output, and the expression for each field
  • vacancy
    • _id"88"
    • _kind"CRVacancy"
    • jobTitle"Developer"
    • vacancyNo"V-88"

Errors

When a step of this node stops a run, the run page shows a code. Look it up:

Example step

The step as a flow file holds it. Replace each value in <…>.

{
  "config": {
    "companyId": "",
    "connection": "<connection id>",
    "deadline": "",
    "endDate": "",
    "extraFields": {},
    "jobTitle": "",
    "offerInformation": "",
    "ownerUserId": "",
    "requirements": "",
    "startDate": "",
    "vacancyId": "",
    "vacancyInformation": "",
    "workCity": ""
  },
  "label": "Update vacancy",
  "type": "carerix.updateVacancy",
  "version": 1
}