CallPalConnect CallPal to Insightly
Sync your Insightly contacts, leads and organizations into CallPal, call them from the browser, and have every call written back to the record it came from. Setup takes about five minutes.
Deciding whether to use it at all? What the Insightly integration does.
Before you start
- A CallPal account. The 14-day trial is enough — no card required, and the integration is available on every plan.
- An Insightly user with API access. The API key is per-user, so the key you use decides which records CallPal can see.
- In CallPal, permission to manage integrations. Owners and admins have it by default.
Copy your API key and API URL from Insightly
In Insightly, open User Settings and find the API Key section. It shows two things you need.
The API key is personal to your user. The API URL is specific to the pod your account lives on — it looks like
https://api.na1.insightly.comorhttps://api.eu1.insightly.com, and the region in the middle differs per account. Copy the one Insightly shows you rather than assuming a format; a key that is correct against the wrong pod fails as if it were wrong.Treat the key like a password. Anyone holding it can read and write everything your Insightly user can.
API URL https://api.na1.insightly.com API Key a1b2c3d4-e5f6-...
Add the connection in CallPal
In CallPal, go to Settings → Integrations, find Insightly, and select it.
Paste the API URL and the API key into the two fields and save. CallPal checks them against your account immediately — if either is wrong, or the pod does not match, you find out now rather than at the first sync.
Choose what to import
Contacts is selected for you. Leads is there if your reps work an unqualified list, and Organizations if they call companies rather than named people.
Custom fields you have added in Insightly come across too — CallPal reads the field list from your own account.
Check the field mapping
CallPal maps the standard fields for you — name, phone numbers, email and owner. Review it and adjust anything your team uses differently.
Insightly carries several phone fields per contact, including a separate mobile. The mapping is where you decide which your reps should reach, and in what order.
Run the first sync
Start the sync. Records appear as they arrive, so a large Insightly account fills in progressively rather than showing nothing until it finishes.
After that CallPal re-syncs every 30 minutes, and you can trigger one by hand from the connection page.
Make a call
Open any synced record and select the phone number, or add records to a power-dialer campaign to work a list.
When the call ends, CallPal writes it back to the Insightly record as a note carrying the direction, duration, outcome and a link to the recording.
What syncs
- Insightly → CallPal
- Contacts, and optionally Leads and Organizations. Standard and custom fields alike, read from your own account.
- Calls → Insightly
- Every completed call is written to the matching record as a note: direction, duration, outcome, start time, whether a recording exists, and a link back to the call in CallPal.
What it does not do
Worth reading before you roll this out to a team — these are design decisions, not gaps we are about to close.
- Calls are logged as notes, because Insightly has no native call-activity object to write to. The first line of every note is a stable marker, so they are straightforward to search and filter.
- Opportunities are not imported. The object carries no phone field of any kind, so it could never become a callable list — the contact behind the opportunity syncs normally and is the record you would dial.
- CallPal reads your records and does not edit them. It never changes a field and never creates a record.
- CallPal is outbound only. No inbound routing, no IVR, no predictive dialing.
Questions
Where do I find my Insightly API key and API URL?
User Settings in Insightly, under API Key. Both are shown there. The API URL is specific to your account’s pod — copy the one displayed rather than assuming the region.
Why does my key fail even though I copied it correctly?
Almost always the API URL. The key is only valid against the pod your account lives on, so na1 against an eu1 account fails exactly as if the key were wrong.
Whose records will CallPal see?
The API key is per-user, so CallPal sees what that Insightly user can see. Use a key from a user with the visibility your team needs.
Why can’t I import Opportunities?
They carry no phone field, so an Opportunities tab could only hold rows nobody could dial. The contact behind the opportunity is importable and is the record you would call.
Which phone number does it call from?
Your own. CallPal is bring-your-own-carrier: you connect your own SIP trunk, calls are billed by your carrier at your rate, and outbound calls present your company number rather than a rep’s personal line.
What happens if I regenerate the API key?
The sync stops and the connection shows an error on the integrations page. Reconnect with the new key to resume. Records already synced into CallPal stay there.
Still stuck?
Write to [email protected] with your account name and what you saw. A person answers.