Recruiting teams running ERPNext HR already keep their pipeline in the Job Opening, Job Applicant, and Interview DocTypes, but the actual sourcing still happens on LinkedIn and Indeed. That means someone copies each opening into two job-board consoles by hand, then re-keys every inbound applicant back into ERPNext, losing which channel produced which hire along the way. ERPNext core ships a public Job Portal and a website Job Opening view, but it has no outbound connector to LinkedIn or Indeed, no Apply-Connect ingestion, and no cross-channel source attribution — so the multi-channel sourcing your recruiters actually do lives entirely outside the system of record.

ECOSIRE builds a proper Frappe app (its own app on the bench, versioned in git, with a dedicated module) that closes that loop. When a Job Opening is set to a publishable status, a hooks.py doc_events handler (on_update / on_submit) enqueues a background job via frappe.enqueue that maps the opening's title, description, location, and employment type to the LinkedIn and Indeed posting payloads and calls their APIs, storing the returned external posting IDs on the Job Opening so the ERPNext record stays the single source of truth. Inbound applicants flow the other way: a whitelisted endpoint (@frappe.whitelist(allow_guest=True)) receives LinkedIn Apply-Connect callbacks and Indeed applicant feeds, normalizes them, and creates Job Applicant records linked back to the correct opening — with the resume attached as a File and the originating board written into a source / channel field for reporting.

Under the hood we add configuration DocTypes (for API credentials, per-board field mappings, and sync settings), server scripts and controller methods for the transform logic, and a client script on Job Opening that surfaces posting status and a manual "re-sync" action for recruiters. Duplicate candidates are caught before insert by matching on email and phone against existing Job Applicant records, so the same person applying through both boards is merged rather than duplicated. A scheduler event (scheduler_events in hooks.py, hourly or daily to fit your API rate limits) reconciles status back to the boards — closing or pausing a posting on LinkedIn and Indeed when the ERPNext opening is filled or closed. Access is governed by ERPNext's permission system and a dedicated role / role profile so only HR and Recruiter users can trigger syncs or read board credentials. Everything targets Frappe/ERPNext v15 and v16 and is delivered against your bench, using the standard Frappe REST API and framework primitives rather than brittle scraping.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call to confirm which boards, which openings qualify for auto-posting, your field mappings, and how you want attribution reported. From confirmed scope, typical delivery is one working week: we build on a staging bench, run UAT with your recruiters, then install on your production bench with a rollback plan. You receive the full source in a git repository you own, plus documentation, training, and a post-go-live support window. LinkedIn and Indeed API access on the customer's own accounts (and any partner-program approval those boards require) is a prerequisite we help you navigate but do not resell.