Recruitment to HR
Greenhouse to Remote integration: foreign hires as EOR employment with the country's form
With an integration between Greenhouse and Remote, a foreign hire in Greenhouse becomes an employment at Remote as employer of record, with name, job title, country, start date and the fields Remote requires for that country. KoppelHet also takes the pay and the country fields from the offer across.
What the integration does
Organisations that recruit in Greenhouse and hire through Remote in countries without an own entity often still retype salary and country fields from the offer into Remote.
- The recruiter marks the candidate as hired in Greenhouse after acceptance.
- KoppelHet determines the country from office or country field and fetches that country's current form from Remote.
- KoppelHet fills the form from candidate and offer and creates the employment.
- HR checks the employment in Remote and sends the invitation.
- If the recruiter reverses the hire, KoppelHet cancels the onboarding while that is allowed, and otherwise it goes to HR.
What to watch for with Greenhouse and Remote
- KoppelHet reads the country from a country field on the offer or from the job's office.
- KoppelHet fills the form Remote asks for per country, with pay and other fields from the offer.
- Greenhouse removed Harvest v1 and v2 on 31 August 2026. KoppelHet reacts to hire_candidate and reads the offer with Harvest v3 and OAuth.
- A hire can come in twice, for example after a changed email address. KoppelHet first searches by application number whether an employment exists and updates it as long as the invitation has not gone out.
- Through the API Remote only creates employments of type employee. KoppelHet therefore only takes over EOR hires; contractors fall outside this integration.
- For an EOR hire Remote requires a start date in the future. An offer in Greenhouse that was filled in retroactively is not left to fail silently by KoppelHet but passed to the recruiter with the reason.
- On unhire_candidate KoppelHet cancels the onboarding at Remote, which is only possible while the contract has not been signed. If it has been signed, it is a termination, and KoppelHet leaves that to HR.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Who sends the invitation to the new employee?
HR, from Remote. After the invitation an employment can only be changed to a limited extent, so HR checks first.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Greenhouse through the hire_candidate and unhire_candidate webhooks (HMAC-SHA256 in the Signature header; up to seven attempts) and Harvest v3 with OAuth 2.0 for offer and custom fields. Currency fields with amount and unit.
- To Remote through the Remote API with a company-scoped token - first the country's form schema, then create employment with company_id, country_code, type employee, external_id and basic_information (name, email, job_title, provisional_start_date). Cancelling through POST /v1/cancel-onboarding/{employment_id} for an unsigned contract.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Greenhouse | Field in Remote | Notes |
|---|---|---|
first_name en last_name | basic_information.name | |
email_addresses (personal) | basic_information.email | |
jobs[].name | basic_information.job_title | |
offer.starts_at | basic_information.provisional_start_date | |
Land (eigen veld in het aanbod) of jobs[].offices | country_code | |
Valutaveld in het aanbod (amount, unit) | Beloning in het landformulier | |
application_id | external_id |
Related
Greenhouse → ADP Workforce Now
Greenhouse to ADP Workforce Now integration: accepted offer as an in-progress hire in ADP
Greenhouse → AFAS Profit
Greenhouse to AFAS integration: an accepted offer starts onboarding in AFAS Profit
Greenhouse → BambooHR
Greenhouse to BambooHR integration: hired candidates in BambooHR automatically and completely
Greenhouse → Dayforce
Greenhouse to Dayforce integration: accepted offer as a validated new employee in Dayforce