Apply to a job listing
applyToJobApply to a job for the candidate: Clera fills in the employer's form from their profile and sends it with the resume tailored to that role when generateApplicationDocuments made one, otherwise their primary resume. Run it when the candidate says to apply to this specific role. Give either jobId with position and companyName exactly as searchJobs or readJobListing (kind board) gave them (a mismatch is refused), or the applicationId of a tracked job that has a posting link (listApplications). Returns { runId } straight away; the form takes about 10-30 seconds, so call getApplicationRun with that runId next. For several listings at once use applyToJobs.
The candidate gets one confirmation before anything is sent. It only sends when every required field is filled; otherwise the run comes back needing input and nothing is sent. mode dry_run fills the form without sending, only when the candidate asks to see it first.
Workday sites (myworkdayjobs.com) need a candidate account: the run creates one with the candidate's email, or signs in to the one it made before, with a password Clera keeps. The candidate can take the account over with "Forgot your password?" there. Some Workday sites first email a "Verify your candidate account" link; getApplicationRun then reports verificationCodeRequested, and enterApplicationCode takes it.
If a run came back needing input, ask the candidate those exact questions and start again with answers. To change something getApplicationRun lists under editable, start again with that question as the answers key and the candidate's new answer. Never make up an answer. A sent application lands on their tracker as applied.
Clera privately records this tool's inputs and results for usage tracking and support.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "applyToJob"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | submit (default) sends it after the candidate confirms; dry_run only fills the form. | submit |
| jobId | No | The jobId from a searchJobs result, or a readJobListing result with kind board. | |
| answers | No | Replies to questions an earlier run asked, or replacements for answers it filled in, as { <needsInput key, or the question>: <the candidate's words> }. At most 30 answers; each key and each answer up to 4,000 characters. | |
| position | No | With jobId: the position exactly as the result gave it. | |
| companyName | No | With jobId: the company name exactly as the result gave it, null when the result had none. | |
| applicationId | No | Instead of jobId: the id of a listApplications entry that has a posting link. | |
| confirmSubmit | No | Only when your client cannot show the confirmation prompt: "submit" once the candidate has said yes to sending this specific application, "cancel" otherwise. Never set it on your own. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | ||
| runId | Yes | ||
| position | Yes | ||
| companyName | Yes |