TeamtailorList job applications
Lists Teamtailor applications, filtered by stage type and dates.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Teamtailor connection the step signs in with. |
| Stage type | The four stage types Teamtailor groups every pipeline column under. |
| Applied from | text |
| Applied up to | text |
| Changed from | text |
| Changed up to | text |
| Moved stage from | The filter a reconciling sync reads — everything that moved since this moment. |
| Moved stage up to | text |
| Also fetch | Related records to fetch with each application, comma separated. Without them an application is three ids. |
| Sort by | A minus in front turns the order around. |
| Applications per call | 1 to 30 — Teamtailor's own maximum is 30. |
| Fetch every page | Follows Teamtailor's own next-page link, and refuses past 5,000 applications rather than answering a short list. |
| Cursor | Paste a previous run's Next cursor to read the page after it. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `teamtailor`) |
stageType | "" or "Inbox" or "In process" or "Hired" |
createdFrom | text |
createdTo | text |
updatedFrom | text |
updatedTo | text |
changedStageFrom | text |
changedStageTo | text |
include | text, by default "candidate,stage,job" |
sort | text, by default "-changed_stage_at" |
pageSize | number, by default 30 |
returnAll | true/false, by default false |
cursor | text |
Output
| Field | Type |
|---|---|
itemsApplications | array |
itemCountApplications in this answer | number |
recordCountApplications matching the filter (all pages) | number |
hasMoreMore applications are waiting behind this page | boolean |
nextUrlTeamtailor's own next-page address | string |
rawThe untouched JSON:API answer | object |
nextCursorCursor for the next page | string |
Sample output, and the expression for each field
- hasMorefalse
- itemCount0
- items[]
- nextUrl""
- raw
- data[]
- included[]
- linksnull
- metanull
- recordCount0
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": {
"changedStageFrom": "",
"changedStageTo": "",
"connection": "<connection id>",
"createdFrom": "",
"createdTo": "",
"cursor": "",
"include": "candidate,stage,job",
"pageSize": 30,
"returnAll": false,
"sort": "-changed_stage_at",
"stageType": "",
"updatedFrom": "",
"updatedTo": ""
},
"label": "List job applications",
"type": "teamtailor.listJobApplications",
"version": 2
}Older versions
A flow that already has this version keeps running it. A new step always gets the newest.
Version 1
| Setting | What it is |
|---|---|
| ConnectionRequired | The Teamtailor connection the step signs in with. |
| Stage type | The four stage types Teamtailor groups every pipeline column under. |
| Applied from | text |
| Applied up to | text |
| Changed from | text |
| Changed up to | text |
| Moved stage from | The filter a reconciling sync reads — everything that moved since this moment. |
| Moved stage up to | text |
| Also fetch | Related records to fetch with each application, comma separated. Without them an application is three ids. |
| Sort by | A minus in front turns the order around. |
| Applications per call | 1 to 30 — Teamtailor's own maximum is 30. |
| Fetch every page | Follows Teamtailor's own next-page link, and refuses past 5,000 applications rather than answering a short list. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `teamtailor`) |
stageType | "" or "Inbox" or "In process" or "Hired" |
createdFrom | text |
createdTo | text |
updatedFrom | text |
updatedTo | text |
changedStageFrom | text |
changedStageTo | text |
include | text, by default "candidate,stage,job" |
sort | text, by default "-changed_stage_at" |
pageSize | number, by default 30 |
returnAll | true/false, by default false |