TeamtailorCreate candidate
BetaChanges data
Adds a candidate to Teamtailor, or merges into the one with that e-mail.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Teamtailor connection the step signs in with. |
| Required unless Sourced is on — Teamtailor keys candidates by e-mail. | |
| First name | text |
| Last name | text |
| Phone | text |
| Pitch | The one-line summary Teamtailor shows under the name. |
| Update the person if they already exist | When a candidate with this e-mail already exists, update them instead of creating a second record. Leaving this off means a second run of this flow creates a duplicate. |
| Sourced, not applied | The candidate did not apply — you found them. Teamtailor then allows a candidate without an e-mail. |
| An internal candidate | true/false |
| Unsubscribed from mailings | true/false |
| CV address | A publicly reachable address. Teamtailor downloads the file and hosts it. For bytes you hold, use the Upload candidate file node instead. |
| LinkedIn address | text |
| Tags | text |
| Referring site | text |
| Referring address | text |
| Consented to be kept for future jobs | true/false |
| Department id | The List departments node gives you the id. |
| Role id | text |
| Division id | text |
| Location ids | text |
| Region ids | text |
| Anything else | Any other Teamtailor candidate attribute, spelled the way Teamtailor spells it — kebab-case, for example linkedin-uid. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `teamtailor`) |
email | text |
firstName | text |
lastName | text |
phone | text |
pitch | text |
merge | true/false, by default true |
sourced | true/false, by default false |
internal | true/false, by default false |
unsubscribed | true/false, by default false |
resumeUrl | text |
linkedinUrl | text |
tags | text |
referringSite | text |
referringUrl | text |
consentGivenFutureJobs | true/false, by default false |
departmentId | texta value from the vendor's own list |
roleId | text |
divisionId | text |
locationIds | text |
regionIds | text |
attributes | object (any keys), by default {} |
Output
| Field | Type |
|---|---|
candidateId | string |
candidate | object |
rawThe untouched JSON:API answer | object |
Sample output, and the expression for each field
- candidate
- id"c-1"
- type"candidates"
- candidateId"c-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": {
"attributes": {},
"connection": "<connection id>",
"consentGivenFutureJobs": false,
"departmentId": "",
"divisionId": "",
"email": "",
"firstName": "",
"internal": false,
"lastName": "",
"linkedinUrl": "",
"locationIds": "",
"merge": true,
"phone": "",
"pitch": "",
"referringSite": "",
"referringUrl": "",
"regionIds": "",
"resumeUrl": "",
"roleId": "",
"sourced": false,
"tags": "",
"unsubscribed": false
},
"label": "Create candidate",
"type": "teamtailor.createCandidate",
"version": 1
}