Move application to stage
BetaChanges data
Moves a Teamtailor application to another stage, or rejects it.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Teamtailor connection the step signs in with. |
| Application idRequired | The List job applications node gives you the id. |
| Stage id | The List stages node, filtered on this job, gives you the id. A stage belongs to one job — a stage id from another job is refused. |
| Reject the application | A Teamtailor rejection can send the candidate an automated e-mail, depending on the job's triggers. |
| Reject reason id | The List reject reasons node gives you the ids. |
| Rejected at | Leave empty to use the moment this step runs. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `teamtailor`) |
jobApplicationId | text |
stageId | text |
reject | true/false, by default false |
rejectReasonId | textused when `reject` is true |
rejectedAt | textused when `reject` is true |
Output
| Field | Type |
|---|---|
jobApplicationIdApplication id | string |
jobApplicationApplication | object |
rawThe untouched JSON:API answer | object |
Sample output, and the expression for each field
- jobApplication
- id"app-1"
- type"job-applications"
- jobApplicationId"app-1"
- raw
- data{}
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": {
"connection": "<connection id>",
"jobApplicationId": "<application id>",
"reject": false,
"rejectReasonId": "",
"rejectedAt": "",
"stageId": ""
},
"label": "Move application to stage",
"type": "teamtailor.moveJobApplication",
"version": 1
}