Update application
update_applicationUpdate fields of an application (get the id from list_applications). Status changes are logged to the timeline automatically. Example: update_application({id: "…", status: "interview", next_action: "prepare system design", next_action_due: "2026-07-20"}).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| url | No | Link to the job posting | |
| role | No | ||
| remote | No | ||
| source | No | LinkedIn, referral, recruiter, Easy Apply… | |
| status | No | ||
| company | No | ||
| location | No | ||
| priority | No | A = top priority | |
| applied_at | No | ISO date YYYY-MM-DD | |
| cv_variant | No | Which CV was sent: DE, EN, AI-focused… | |
| match_notes | No | Markdown match assessment: why the candidate fits this role — strengths vs requirements, gaps, level/salary advice, process notes. Save your vacancy analysis here so it is not lost; shown as an expandable section in the dashboard. | |
| next_action | No | e.g. "follow-up", "thank-you email" | |
| remote_note | No | e.g. "2 days office" | |
| salary_asked | No | What the candidate asked for — yearly gross EUR as a plain number, e.g. 110000 | |
| salary_range | No | Posting salary range upper bound — yearly gross EUR, plain number | |
| next_action_due | No | ISO date YYYY-MM-DD | |
| salary_range_min | No | Posting salary range lower bound — yearly gross EUR, plain number | |
| next_interview_at | No | ISO datetime, e.g. 2026-07-20T14:00:00+02:00 |