import_job_alerts
Import job-alert emails from LinkedIn, Built In, and Indeed to track matching roles, filter out irrelevant jobs, and avoid duplicates in your jobwatch digest.
Instructions
Track the jobs in job-alert emails (LinkedIn, Built In, Indeed; other senders with a generic reader). Search the person's mail for them first, e.g. from:jobalerts-noreply@linkedin.com, from:builtin.com, from:jobalert.indeed.com, from:match.indeed.com (Indeed's job matches, as its app notifies them), and pass each message in; jobwatch never needs a mail password. Links lose their tracking parameters. Each job whose title, place and pay pass the watchlist's filters is looked for on the company's own board (a link to a supported board is read from there); job sites' pages are read only when their robots.txt allows (LinkedIn's and Indeed's don't, so the email's details are used). Jobs already tracked are left alone (known); new ones show up in get_digest, with via saying where they came from. Returns counts and each job: key, result (new, known, duplicate: twice in these emails), how (board, posting, page or email), filtered (why the filters leave it out of the digest, or null) and duplicate_of (the job applied to, queued or skipped that it's maybe the same opening as, as get_job gives it, or null). For emails about the person's applications (confirmations, rejections, interviews), use read_status_emails.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| emails | Yes | The alert emails, one string each: the raw message (RFC822, as a mail connector's raw format gives it, base64url-encoded as from Gmail's API is fine too; best, since it names the sender) or just its HTML or plain-text body. | |
| dry_run | No | Say what would be tracked, and record nothing. | |
| follow_links | No | Look for each job that passes the filters on the company's own board, and read links robots.txt allows. False tracks each job as the email has it, with no requests. |