CallPal

Connect CallPal to noCRM.io

Sync your noCRM.io leads into CallPal, power-dial them from the browser, and have every call written back to the lead it came from. Setup takes about five minutes.

Deciding whether to use it at all? What the noCRM.io 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.
  • A noCRM.io account with admin access, so you can create an API key.
  • In CallPal, permission to manage integrations. Owners and admins have it by default.
  1. Create an API key in noCRM.io

    In noCRM.io, open Admin panel → Integrations → API keys and create a key.

    You also need your account URL — the address you use to reach noCRM.io, in the form https://yourcompany.nocrm.io. It is unique to your account, so copy the one in your address bar rather than typing a format you have seen elsewhere.

    Treat the key like a password. Anyone holding it can read and write your leads.

    Account URL   https://yourcompany.nocrm.io
    API key       a1b2c3d4e5f6...
  2. Add the connection in CallPal

    In CallPal, go to Settings → Integrations, find noCRM.io, and select it.

    Paste the account URL and the API key into the two fields and save. CallPal checks them against your account immediately — if either is wrong you find out now rather than at the first sync.

    The CallPal Integrations page, with the noCRM.io card among the available connectors.The Connect noCRM.io dialog in CallPal, with the account URL and API key fields filled in.
  3. Choose what to import

    noCRM.io is built around one object — leads — and so is this connector. There is nothing to choose here, which is the point: a lead in noCRM.io is already the thing your reps are meant to call.

    Custom fields you have added to your lead form come across too, under extended_info.fields, so anything your team captures is available for mapping and for showing as a column in CallPal.

    The noCRM.io connection page in CallPal, showing Leads with its full field mapping.
  4. Check the field mapping

    CallPal maps the standard fields for you — lead title, name, phone, mobile and email. Review it and adjust anything your team uses differently.

    noCRM.io carries both a phone and a mobile field. Map both if your reps should try either, and put them in the order you want them tried.

  5. Run the first sync

    Start the sync. Leads appear as they arrive, so a large pipeline 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.

  6. Make a call

    Open any synced lead and select the phone number, or add leads to a power-dialer campaign to work through your pipeline in order.

    When the call ends, CallPal writes it back to the noCRM.io lead as an activity carrying the direction, duration, outcome and a link to the recording.

What syncs

noCRM.io → CallPal
Leads, including the custom fields on your own lead form. Lead title, names, phone, mobile, email, job title, address, website and status all come across.
Calls → noCRM.io
Every completed call is written to the matching lead as an activity: 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.

  • CallPal reads your leads and does not edit them. It never changes a field, never moves a lead through your pipeline steps and never creates one.
  • Prospecting lists are not imported — only leads. A prospect that has been converted to a lead syncs normally.
  • CallPal is outbound only. No inbound routing, no IVR, no predictive dialing — which suits noCRM.io’s model, where a rep works a list one lead at a time.

Questions

Where do I find my noCRM.io API key?

Admin panel → Integrations → API keys. Create one there. You also need your account URL, which is the address you use to reach noCRM.io.

Why is there only one object to import?

Because noCRM.io has one that matters for calling. A lead is already the unit your reps work, so there is nothing to choose.

Will my custom lead fields come across?

Yes. They arrive under extended_info.fields and are available for mapping and for showing as columns in CallPal.

How are calls recorded?

As an activity on the matching lead, with direction, duration, outcome and a link back to the call in CallPal.

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 delete the API key?

The sync stops and the connection shows an error on the integrations page. Reconnect with a new key to resume. Leads already synced into CallPal stay there.

Still stuck?

Write to [email protected] with your account name and what you saw. A person answers.