Integration · Roofing CRM

Roofbird leads, inside JobNimbus.

Your crew already opens JobNimbus every morning. That is where a lead should be waiting — not in another tab behind another login that nobody remembers to check.

JobNimbus is the CRM most roofing companies actually run their jobs in, and the honest problem with any lead tool is that it asks people to leave the system they live in. A list of good addresses in somebody else's dashboard is not a workflow. It is a browser tab that stops getting opened by Thursday.

So the integration is deliberately one-directional and boring: Roofbird scores the roofs, and the ones you choose land in JobNimbus as contacts. Your reps never have to know Roofbird exists. They open the CRM, they see a new contact tagged Roofbird, and the note tells them what the roof looks like and what to say at the door.

Connecting takes a key you generate yourself inside JobNimbus. There is no add-on to buy, no partner application, and no call with us.

How to connect JobNimbus to Roofbird

1
Make a key in JobNimbus
In JobNimbus, go to Settings → API → New API Key. Name it Roofbird and pick a profile that can read and create contacts. Copy the key.
2
Paste it into Roofbird
In Roofbird, open Integrations and paste the key. We make one read call to confirm it works, then read your account's custom fields so we can offer to map them. If anything is wrong with the key you are told immediately rather than at the first push.
3
Send a batch and look at it
Pick a scan area and send your best fifty. They arrive worst-roof-first — the same order Roofbird shows them in — as contacts with the address, the owner name where you have unlocked it, and Roofbird tags on the record. Look at one in JobNimbus before you send more.
4
Map the rank field, if you want to sort by it
Create a number field in JobNimbus called anything you like, then map Roofbird rank % to it. Sort that column ascending and the worst roof in the area is at the top of your JobNimbus list. This is the one mapping worth doing; everything else is already in the note.
5
Turn on automatic sending
Switch on auto-send and every future scan drops its new leads into JobNimbus on its own. You can cap it — send only leads in the worst-roof top twenty percent, for instance — so a big scan does not flood the CRM with midlife roofs.

What actually arrives on the contact

The notes field carries the whole assessment, because that is the one surface every JobNimbus account has and it needs no setup: the rank, whether the lead is hot, why this house is worth a knock today, a pre-written opening line, the roof condition and material, estimated squares, the estimated job value range, the date of the imagery the read came from, and links to the satellite and Street View frames so a rep can look before they drive. Address, city, state and ZIP go to the native address fields. Phone and email go to the native phone and email fields, on leads you have unlocked. Every lead is tagged Roofbird, plus tags for the things you would actually filter on — hot, active damage, already patched, and recently replaced so you can exclude the ones nobody should knock. We also set the JobNimbus external ID to the Roofbird lead id. That is not for you, it is for support: when something looks wrong on one record, it means the record can be traced back to the exact assessment that produced it.

Why nothing gets duplicated

Duplicates in a system of record are worse than no integration at all. A roofer with two of every contact stops trusting the whole list, and cleaning it up is manual work you inflicted on them. So sending the same lead twice updates the contact we already created rather than making a second one, and we track that from our side rather than by searching JobNimbus for a match. A search that flakes once creates a duplicate; a stored id does not. On top of that, a lead whose details have not changed since the last send is skipped entirely — which means pressing send again after a re-scan is safe, and does not bury your own edits to the record under ours.

The DNC rule, because it is a legal problem and not a data problem

Roughly half the phone numbers on any skip-traced list are on the Do Not Call registry. A number pushed into a CRM without that flag is a compliance exposure handed to whoever hits dial next. So a registry number never goes into the JobNimbus mobile field, which is the one a rep taps to call. Callable numbers take the mobile and home fields in that order; registry numbers go elsewhere or nowhere, and the note says plainly how many of the numbers on that lead are on the registry. If every number on a lead is listed, the note says do not cold call, in those words. Under CAN-SPAM, email does not require prior consent the way calls and texts do, which in practice makes it the workable cold channel on a list like this. The phone numbers are for the leads that come to you.

FAQ

›Do I need a paid add-on for the JobNimbus API?

No. JobNimbus lets any account create an API key from Settings → API. That is the only thing you need, and you create it yourself.

›Do leads arrive as contacts or as jobs?

Contacts. A lead is somebody you have not spoken to yet, and creating a job for a house nobody has knocked would put work in your pipeline that does not exist. When a lead becomes real, you make the job in JobNimbus the way you always have.

›What happens if I re-scan the area?

Nothing, unless something changed. Leads that already reached JobNimbus and have not changed are skipped, so your CRM does not churn and your own notes on the record are not overwritten.

›Can Roofbird read my JobNimbus data?

Only if you ask it to. The one feature that reads your CRM is scoring the leads already in it, and it runs a batch at a time when you press the button — there is no background sync. Sending leads out only ever writes.

›Does this cost extra on the Roofbird side?

No. Sending leads into your CRM does not consume scan quota or contact unlocks, because it moves leads you already have. Unlocking a homeowner's contact details is the only thing that costs per lead, and it stays a deliberate action in Roofbird — no integration can spend it.

Put your next fifty leads in JobNimbus

Start with the free trial, scan one neighbourhood, and send the best of it into the CRM you already use. No card, and the connection takes a key you make yourself.

Get started free →