Real-time
Two-way sync
Changes in Hibob or Insightly instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Hibob to Insightly integration — real-time, two-way sync
Keep Hibob and Insightly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Hibob and Insightly
Keep the people who own accounts in Insightly in step with the workforce records in Hibob, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.
Insightly runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Hibob. Hibob is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Organizations, Leads, Opportunities, Projects in Insightly with Documents, Named lists, People (Employees), Employment in Hibob field by field, in real time, and in both directions. You decide which system owns which fields, so Hibob stays authoritative on roles and org structure while Insightly keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Two-way sync of Insightly contacts and organizations with a marketing automation platform
- 02 Replicate opportunities into Postgres or a warehouse so RevOps can report on pipeline with SQL
- 03 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.
- 04 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
Common sync patterns
One directory of people
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Where Hibob tracks people the business also engages: contacts stay in sync
A person recorded in Hibob, such as a candidate or applicant, can create or update the matching contact in Insightly, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
New team members provisioned when they are hired
When Hibob records a new hire, a matching user or owner is created in Insightly, so a new rep can start working accounts without waiting on a manual setup ticket.
What you can sync between Hibob and Insightly
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Hibob objects | Insightly objects | How this pairing syncs | |
|---|---|---|---|
| Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Products Product catalog entries support line-item syncing on opportunities and quotes. | Lifecycle is specific to Hibob and Products to Insightly — each maps to any object or custom field on the other side. | |
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Custom Fields Per-object custom fields carry enrichment and billing data written from external systems. | Documents is specific to Hibob and Custom Fields to Insightly — each maps to any object or custom field on the other side. | |
| Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | Contacts Person records sync with marketing and support tools to keep one contact list. | Named lists is specific to Hibob and Contacts to Insightly — each maps to any object or custom field on the other side. | |
| People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. | Organizations Company records map to accounts in ERPs and other CRMs. | People (Employees) is specific to Hibob and Organizations to Insightly — each maps to any object or custom field on the other side. | |
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Leads Unqualified prospects sync in from forms and enrichment sources before conversion. | Employment is specific to Hibob and Leads to Insightly — each maps to any object or custom field on the other side. | |
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Opportunities Pipeline records feed forecasting and warehouse-based reporting. | Work is specific to Hibob and Opportunities to Insightly — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Insightly
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Hibob Insightly Sub-second propagation
DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.
DeliveryEach detected change is written to Insightly through its API, with automatic retries and rate-limit backoff.
Insightly Hibob Interval-based propagation
DetectionStacksync polls Insightly for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record updated-date fields.
DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
- Insightly: Daily API request caps vary by Insightly plan.
What ships with Hibob ⇄ Insightly
Connect Hibob and Insightly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Insightly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Insightly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Hibob or Insightly record.
Observability
Monitoring
Track your Hibob ⇄ Insightly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Hibob and Insightly.
How the Hibob and Insightly connectors work
Hibob
- Integration surface
- REST API (the Bob API)
- Authentication
- Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
- Change detection
- Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
- Capabilities
- read · write · webhooks
- Rate limits
- Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Insightly
- Integration surface
- REST API (versioned)
- Authentication
- API key sent via HTTP Basic authentication
- Change detection
- Polling on record updated-date fields
- Capabilities
- read · write
- Rate limits
- Daily API request caps vary by Insightly plan
How it works
How to connect Hibob to Insightly — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Hibob and Insightly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Hibob
connected
Insightly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Insightly objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Hibob ⇄ InsightlyCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Hibob InsightlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Insightly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Insightly: authenticate both systems, choose the objects to sync (such as Hibob's Lifecycle and Documents), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Hibob: Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event). On Insightly: Polling on record updated-date fields. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Insightly side: Organizations, Leads, Opportunities, Projects, plus custom fields where Insightly exposes them. On the Hibob side: Documents, Named lists, People (Employees), Employment. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Hibob and Insightly: One directory of people; Where Hibob tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired. A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
-
Hibob: REST API (the Bob API). Authentication: Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin. Insightly: REST API (versioned). Authentication: API key sent via HTTP Basic authentication. Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 516 integrations available for Hibob and Insightly.
Popular · 7 of 516
-
Hibob ⇄ Salesloft -
Hibob ⇄ SAP Sales Cloud -
Hibob ⇄ Streak CRM -
Insightly ⇄ Greenhouse -
Insightly ⇄ Jobvite -
Insightly ⇄ Lever -
Insightly ⇄ Namely
No integrations match .
