n8n-nodes-jia

This is an n8n community node. It lets you use JIA (Just Interview AI) in your n8n workflows.

JIA is an AI hiring platform. This node lets a workflow generate and manage job descriptions and screen resumes in your JIA organization.

n8n is a fair-code licensed workflow automation platform.

Installation ·
Credentials ·
Operations ·
Usage ·
Limits ·
Version history

Installation

Follow the installation guide in the n8n community nodes documentation, and install the package n8n-nodes-jia.

On self-hosted n8n, an instance owner or admin installs it once from Settings → Community nodes → Install; the node and credential are then available to every user of that instance. If the menu is missing, set N8N_COMMUNITY_PACKAGES_ENABLED=true. In queue mode, also set N8N_REINSTALL_MISSING_PACKAGES=true so workers install it too.

Credentials

The node uses a JIA API credential.

1. In JIA, open Settings → API Keys (organization owners only) and create a key. Copy it: JIA shows the full key only once.
2. In n8n, create a JIA API credential:
   • Base URL: the URL of your JIA backend API, without a trailing slash.
   • API Key: the key from step 1.
3. Click Test. n8n checks the key against JIA without using any credits.

A key acts as the JIA member who created it. It stops working as soon as it is revoked in JIA, that member is deactivated, or that member changes their password or signs out everywhere.

Setting up JIA for a team

Each key belongs to one JIA organization, so use one credential per organization (for example JIA – QA and JIA – Production).

1. A JIA organization owner creates one key per environment.
2. An n8n admin creates a project (for example JIA Hiring), adds the JIA API credential to it, and adds the people who build hiring workflows as project members.
3. Members pick the shared credential in the JIA node. They can run workflows with it but can't see the key.
4. To rotate a key, revoke it in JIA, create a new one, and update the single credential; every workflow keeps working.

Operations

Job Description

Every field accepts n8n expressions, so values can come from earlier nodes, for example {{ $json.role }}.

Output

Each job description is returned as one item:

{
  "job_id": 812,
  "public_jd_id": "1000812",
  "title": "Senior Backend Engineer",
  "description": "…",
  "skills": ["Python", "FastAPI", "PostgreSQL"],
  "experience": "3-5 years",
  "department": "Engineering",
  "employment_type": "FULL_TIME",
  "job_location": ["Bengaluru, Karnataka"],
  "salary_min": 1800000,
  "salary_max": 2600000,
  "application_deadline": "2026-11-30",
  "custom_interview_questions": [],
  "is_active": true,
  "saved": true
}

A draft that was not saved has "saved": false and "job_id": null.

Resume

Each input item is screened separately, so 10 resumes in give 10 results out. JIA accepts PDF and DOCX up to 10 MB; scanned (image-only) PDFs can't be read.

Screening output

{
  "score": 88,
  "composite_score": 85.7,
  "summary": "Strong fit for the Senior Backend Engineer role…",
  "strengths": ["Relevant experience", "Relevant projects", "Certifications", "Resume quality"],
  "gaps": [],
  "attributes": { "relevant_experience_score": 92, "relevant_projects_score": 85, "certifications_score": 80, "resume_quality_score": 95 },
  "experience_gap_months": 0,
  "candidate": { "name": "Aarav Test", "email": "aarav.test@example.com", "phone": "+919800000010", "years_of_experience": 6 },
  "job_id": 7980,
  "injection_detected": false,
  "credits_remaining": 2,
  "file_name": "resume.pdf"
}

score is top level so an IF node can branch on it, for example {{ $json.score >= 70 }}. composite_score uses the job's evaluation profile and is null when screening against pasted text. Turn on Include Input Binary to pass the resume file on to later steps.

Usage

Sheet row to published job: Google Sheets Trigger (new row) → JIA Job Description: Generate with Job Details set to {{ $json.role }}, {{ $json.experience }}, {{ $json.location }} → Slack message with the new job_id.

Screen inbound applications: Gmail Trigger (has attachment) → JIA Resume: Screen with Input Binary Field attachment_0 and an Existing Job → IF {{ $json.score >= 70 }} → notify the recruiter.

Draft for review: JIA Generate with Save to JIA off → send the draft for approval → JIA Create with the approved fields.

Limits

• Saving uses a JD credit. Generate (with Save on) and Create each use 1 JD credit. When the organization is out of credits, JIA returns an error and nothing is saved.
• Saved jobs are published immediately. JIA has no draft state for jobs; use Generate with Save off if you need a review step.
• Saves are not retried automatically, because a retry would create a duplicate job and use another credit. If you enable n8n's Retry On Fail, check JIA for duplicates.
• Generation takes time. AI generation typically takes a few seconds and up to about 20 seconds. The node waits up to 120 seconds per request.
• Past deadlines. JIA rejects deadlines in the past. A past deadline suggested by the AI is dropped; a past deadline you set yourself is sent, and JIA returns an error.
• Screening uses a resume-screening credit, only when a score is produced. Unreadable files and errors are not charged. Screens are not retried automatically.
• Rate limit. Each API key is limited to 60 requests per minute.

Errors from JIA appear in n8n with JIA's own message and HTTP status. With Continue On Fail on, a failed item returns { "error": "…", "httpCode": "…" } and the other items keep running.

Compatibility

Built with @n8n/node-cli and tested against n8n 2.x.

Resources

• n8n community nodes documentation

Releasing (maintainers)

main only accepts reviewed pull requests, so releases are cut by tag:

1. Open a PR that bumps version in package.json and package-lock.json and adds a CHANGELOG.md entry. Merge it after review.
2. Tag the merged commit and push only the tag:

   git switch main && git pull
   git tag 0.1.2
   git push origin 0.1.2
   

3. The tag runs .github/workflows/publish.yml, which lints, builds and publishes to npm with provenance through npm Trusted Publishing.

Version history

See CHANGELOG.md.