One-click multipost Odoo vacancies to LinkedIn, Indeed, Bayt and Naukri, then auto-import applicants back into Recruitment. One-time license from $299.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

One-click multipost Odoo vacancies to LinkedIn, Indeed, Bayt and Naukri, then auto-import applicants back into Recruitment.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
One-click multipost: publish any hr.job vacancy to every selected board from a single action on the vacancy form, no tab-switching or re-typing
LinkedIn connector: push vacancies to LinkedIn via its official jobs API / partner feed with your company page and location targeting
Indeed connector: distribute roles to Indeed through its indexing/API feed, including sponsored vs organic handling where your account supports it
Bayt connector: post to Bayt for Gulf and MENA hiring, with Arabic/English title and description fields per posting
Naukri connector: publish to Naukri for India-region recruitment through your employer account integration
Applicant auto-import: an ir.cron poll plus a per-vacancy inbound email alias creates hr.applicant records in the right job and stage automatically
If your recruiters live in Odoo Recruitment but still open LinkedIn, Indeed, Bayt and Naukri in separate tabs to re-type every job — and then manually key each applicant back into a hr.applicant record — you are paying skilled people to do clipboard work. The Job Board Multiposting Connector is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for your database. It turns any published hr.job vacancy into a one-click, multi-channel campaign and pulls applicants back into your pipeline automatically, with the source attribution you need to prove which board actually delivers hires.
This is not an off-the-shelf apps.odoo.com download. We engineer it against your exact stack — Odoo 17, 18 or 19, Community or Enterprise — and the specific job boards, credentials and hiring workflow you use.
A new "Multipost" action sits on the vacancy form. Pick your target boards, adjust the per-board title/description if you want, hit publish, and the module fans the job out through each board's API (or your official partner feed for boards that require one). Every board becomes a tracked line on the vacancy with its own status — Queued, Live, Rejected, Expired — so a recruiter can see at a glance where the role is actually running. When candidates apply, an inbound pipeline (board API poll plus a per-vacancy email alias) creates hr.applicant records in the correct job and stage, de-duplicated by email, with the CV attached and the originating board stamped on source_id / medium_id / campaign_id so your recruitment analytics finally reflect reality.
We do this the Odoo-native way, not with bolt-on scripts. New models (models.Model) hold board credentials, posting lines and applicant-source mappings; computed fields with @api.depends keep live/expired counts current; access is locked down with ir.model.access.csv plus record rules so agencies only see their own clients' boards. Outbound posting and inbound polling run through automated actions / ir.cron using each board's REST API via authenticated XML-RPC / JSON-RPC-style service layers, with retry and error logging. UTM tracking reuses Odoo's own utm.source / utm.medium / utm.campaign so attribution flows straight into the built-in Recruitment reporting. Views are standard XML/OWL, and we can add a QWeb report for a per-campaign posting summary. Everything ships as a clean, upgrade-safe addon with its own __manifest__.py, version-pinned to your Odoo release.
Job boards change their APIs, deprecate feeds, and vary by region — a static marketplace module rots fast and rarely covers Bayt or Naukri properly. Because ECOSIRE builds this for you, we implement exactly the boards you hire on, in your language and currency, wired to your credentials, and we keep it working through Odoo upgrades and board API changes during your support window. You get the convenience of a product with the fit of a custom build.
A corporate recruiting function that runs Odoo Recruitment as its ATS and hires across several boards at once. They want to publish a vacancy everywhere in one click and see every applicant land in the right pipeline automatically, so recruiters spend time on candidates instead of clipboard work.
An agency placing candidates for many clients that needs strict separation of boards, credentials and applicants per client. Record-rule isolation and per-board content overrides let each desk multipost without stepping on another client's postings or data.
The person accountable for cost-per-hire and channel ROI. They need reliable source attribution — which board produced which hire — flowing into Odoo's Recruitment analytics via utm.source/medium/campaign, not guessed from spreadsheets.
Buy the license on ecosire.com and download the Job Board Multiposting Connector module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Job Board Multiposting Connector, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Multipost to LinkedIn, Indeed, Bayt, Naukri in one click | ||||
| Applicants auto-imported to hr.applicant (API poll + email alias) | ||||
| Duplicate detection across boards by email | ||||
| Per-board source & UTM attribution into Recruitment analytics | ||||
| Region-specific boards (Bayt / Naukri) with bilingual overrides | ||||
| Kept working through board API changes and Odoo upgrades | ||||
| Built for your exact boards, credentials and workflow | ||||
| Agency multi-client isolation via record rules |
This is a build-to-order module, not an instant apps.odoo.com download. Typical lead time is 2 to 4 weeks from kickoff, depending on how many boards you need and how each board's API access is set up on your accounts. You get a UAT build to review first, then we deploy to production. If you only need two boards on a clean Odoo.sh instance it can land toward the shorter end; adding region-specific boards like Bayt or Naukri that require employer-account onboarding pushes it later.
Every engagement includes a defined post-go-live support window covering bug fixes and, critically, break-fixes when a job board changes or deprecates its API — the main reason generic marketplace connectors rot. During the window we keep the connectors working, respond within the agreed SLA, and assist with the Odoo point releases you run. Extended support and adding new boards later are available as a follow-on; we scope those before your window ends so there is no gap.
Out of the seed set we cover LinkedIn, Indeed, Bayt and Naukri, and we regularly add others (Monster, Glassdoor, GulfTalent, regional and niche boards) depending on where you hire. Each connector depends on that board offering an API, indexing feed, or official partner program and on you holding the appropriate employer account — we confirm feasibility per board during scoping before committing to it.
Yes. We build and version-pin the addon to Odoo 17, 18 or 19, and it works on both Community and Enterprise since it builds on the standard Recruitment app (hr.job, hr.applicant) and core UTM models. If you later upgrade Odoo, keeping the module compatible with the new major version is handled as an upgrade engagement.
Applicants return two ways: a scheduled ir.cron job polls each board's API for new applications, and each vacancy also gets an inbound email alias that captures applications forwarded by boards that email you. Both paths create hr.applicant records in the correct job and stage with the CV attached. We de-duplicate by candidate email, so someone who applies on two boards becomes a single record, and every applicant is stamped with the source board via source_id / medium_id / campaign_id.
Yes. Board API keys and tokens live on dedicated models protected by ir.model.access.csv and record rules, so only authorized configuration users can see or edit them — standard recruiters never touch raw credentials. For agencies, record rules isolate each client's boards and applicants. All outbound calls go over authenticated, encrypted connections, and failed calls are logged with the board's response rather than exposing secrets in tracebacks.
Yes. You can override the title, description, salary display and category mapping for a specific board without changing the master vacancy, which matters for bilingual MENA postings or region-specific formatting. On the reporting side, because we reuse Odoo's native utm.source/medium/campaign, source attribution flows straight into the built-in Recruitment analytics; we can also deliver a QWeb per-campaign summary or a cost-per-hire-by-board dashboard as a scoped add-on.
One-click multipost Odoo vacancies to LinkedIn, Indeed, Bayt and Naukri, then auto-import applicants back into Recruitment.