Two-way sync
Changes in Insightly or Lever instantly reflect in both systems. No stale data, no manual imports.
Keep Insightly and Lever in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Lever. Lever 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 Opportunities, Projects, Tasks, Events in Insightly with Feedback, Interviews, Notes and Contacts, Opportunities in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so Lever stays authoritative on roles and org structure while Insightly keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
When Lever 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.
When a person changes team, manager, or region in Lever, their accounts and territory assignments in Insightly update to match, so pipeline stays with the right owner.
When Lever marks a worker as departed, the matching user in Insightly is flagged or deactivated, so former employees do not keep CRM access after their last day.
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.
| Insightly objects | Lever objects | How this pairing syncs | |
|---|---|---|---|
| Opportunities Pipeline records feed forecasting and warehouse-based reporting. | Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Custom Fields Per-object custom fields carry enrichment and billing data written from external systems. | Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. | Custom Fields is specific to Insightly and Feedback to Lever — each maps to any object or custom field on the other side. | |
| Contacts Person records sync with marketing and support tools to keep one contact list. | Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. | Contacts is specific to Insightly and Interviews to Lever — each maps to any object or custom field on the other side. | |
| Organizations Company records map to accounts in ERPs and other CRMs. | Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. | Organizations is specific to Insightly and Notes and Contacts to Lever — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects sync in from forms and enrichment sources before conversion. | Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. | Leads is specific to Insightly and Postings to Lever — each maps to any object or custom field on the other side. | |
| Projects Delivery records created from won opportunities sync with PSA and task tools. | Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. | Projects is specific to Insightly and Requisitions to Lever — each maps to any object or custom field on the other side. |
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.
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 Lever through its API, with automatic retries and rate-limit backoff.
DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.
DeliveryEach detected change is written to Insightly through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Insightly–Lever connection.
Changes in Insightly or Lever instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Insightly or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Insightly or Lever record.
Track your Insightly ⇄ Lever sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Insightly and Lever.
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.
Authenticate Insightly and Lever with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Insightly and Lever 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Insightly and Lever: authenticate both systems, choose the objects to sync (such as Insightly's Opportunities and Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Insightly and Lever. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Insightly: Polling on record updated-date fields. On Lever: Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Insightly side: Opportunities, Projects, Tasks, Events, plus custom fields where Insightly exposes them. On the Lever side: Feedback, Interviews, Notes and Contacts, Opportunities. 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 Insightly and Lever: New team members provisioned when they are hired; Ownership and territory follow the org chart; Deactivate access when someone leaves. When Lever 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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 516 integrations available for Insightly and Lever.