Skip to main content

How to connect

Get your JobNimbus API key

1

Log into JobNimbus

Go to your JobNimbus account. You need to be an administrator to create an API key.
2

Navigate to API settings

Go to Settings > API and click New API Key.
3

Create the key

Name the key (for example Allo) and give it an access profile that can read and edit contacts and read account settings, such as Admin. Copy the key.

Connect in Allo

1

Open integrations

Go to web.withallo.com and navigate to Settings > Integrations.
2

Find JobNimbus

Locate JobNimbus in the integrations list and click Connect.
3

Paste your API key

Enter the API key you copied from JobNimbus.
4

Save and connect

Click Save & Connect and wait for confirmation.

What syncs

From JobNimbus to Allo:
  • Contacts
From Allo to JobNimbus:
  • Calls and SMS, logged on the matching contact
  • New contacts, only when Create lead for unknown calls is enabled
When Allo creates a contact, it lands in your first active contact workflow, at its first status (for example Customer > Lead). Allo only fills in empty fields on existing contacts and never overwrites a name, email or phone number already set in JobNimbus. Jobs are not synced.

How calls are synced

After each call, Allo logs it on the matching contact in JobNimbus as a Phone Call activity, with the call summary, tags, and a link to the recording. The activity is dated to when the call happened and assigned to the JobNimbus user whose email matches the Allo user.

How SMS are synced

Each SMS is logged on the matching contact in JobNimbus as a Text Message activity, with the message content.
If an admin has deactivated the Phone Call or Text Message activity type in JobNimbus, Allo logs the activity as a Note instead.

Troubleshooting

Check the sync status of any call from the call list on web.withallo.com — each call has an integration indicator showing its sync state.
Only admins and managers of an Allo workspace can connect integrations. If you don’t see the option, ask your workspace admin or manager to set it up.On the JobNimbus side, the API key must be created by a JobNimbus administrator. If the connection fails, check that the key has not been deleted and that its access profile can read contacts.
Check the integration indicator on the call in the web app. The error will be one of these:
  • Contact not found — The contact doesn’t exist in your CRM. By default, Allo only syncs calls to existing contacts. To auto-create contacts, go to your integration settings and enable Create lead for unknown calls.
  • Contact deleted — The contact was removed from your CRM. Allo is additive and won’t sync calls for deleted contacts. Re-create the contact in your CRM, then retry the sync.
  • Integration disconnected — Your API key was deleted or revoked in JobNimbus. Allo still appears connected but requests fail. Create a new key, then disconnect and reconnect the integration in Allo.
  • Call pending (spinner icon) — Allo is still matching the contact. This can take up to 24 hours before being marked as an error. Once the contact exists in your CRM, you can retry manually.
  • Contact is a favorite — By default, calls with a favorite contact are not synced to your CRM. Remove the contact from your favorites if you want these calls to sync.
The first sync can take up to 15 minutes for large contact databases. After that, contacts sync incrementally every 5 minutes — not in real time.Allo only syncs contacts that have at least one number in the Mobile, Home or Work phone field. Contacts without a phone number, and deleted contacts, will not appear in Allo.If contacts still don’t appear after 15 minutes, disconnect and reconnect the integration.
If your SMS are not appearing, verify the integration is connected in Settings > Integrations and check the integration indicator on the call list at web.withallo.com for error details.If SMS still don’t appear, disconnect and reconnect the integration.
Allo mirrors your integration exactly. If your CRM has duplicate contacts with the same phone number, they appear as separate contacts in Allo.Clean up duplicates in your CRM — Allo will reflect the change on the next sync.
When multiple contacts share the same phone number, Allo logs the call on the first matching contact. Before reporting a missing sync, check all contacts that share that phone number — the call may already be synced to another one. Click the integration indicator on any call in the web app to see exactly which contact it was synced to.