Connect nCino

Bring every loan's collateral into CoverGuard so each property gets an insurability check without anyone re-typing an address. You connect the Salesforce org your nCino runs in once, CoverGuard reads your loans with their collateral address, and — if you choose — writes its findings back onto the Collateral record your team already works from.

Who this is for

Lenders — banks and credit unions — on a Pro plan or above who run nCino's banking platform. You'll need permission in Salesforce to create a connected app, or a Salesforce administrator who can.

You'll find it at Sys Admin → Integrations → Connect a new system → nCino.

Not seeing nCino in the list? It's enabled per account. Ask your CoverGuard contact to switch the connector on.

nCino Mortgage Suite is a different product. This connector reads nCino's banking platform, which runs inside Salesforce. nCino Mortgage Suite (formerly SimpleNexus) is a separate system and isn't covered here yet.

How to connect

nCino lives inside your Salesforce org, so you connect through a connected app in that org — the same way a Salesforce CRM connects.

1. In CoverGuard, open Sys Admin → Integrations and choose nCino. Pick what you want it to do, then copy the callback URL the connect screen shows.
2. In Salesforce, go to Setup → App Manager → New Connected App, enable OAuth, paste that callback URL, and add the api and refresh_token scopes.
3. Run the app as a user who can read Loans and Collateral. If you want findings written back, that user also needs edit access to Collateral.
4. Save, then open Manage Consumer Details and copy the Consumer Key and Consumer Secret.
5. Back in CoverGuard, paste both values and choose Production org or Sandbox org. Getting this wrong sends you to a login page your account isn't on.
6. Select Continue, sign in to Salesforce, and approve access.

CoverGuard never sees your password. It receives a grant you can revoke in Salesforce at any time.

What you get

Each loan and pledged collateral pair comes across as one loan in your CoverGuard portfolio, with the collateral address turned into a property and its risk check started automatically.

A loan with two pieces of collateral arrives as two portfolio entries — one per property — because each property has its own insurability.

nCino's field names vary with its version and with how your bank has configured it. If your org doesn't have one of these fields, CoverGuard leaves it out and tells you which one in the sync history, rather than stopping the whole sync. Map the field your org uses instead from the connection's page. Verify on the connection's page tells you the same thing before your first sync, so you can fix the mapping first.

Sending findings back to nCino

If you picked Also write CoverGuard findings back to the collateral record, CoverGuard puts these on the Collateral record:

When the home has a current CoverGuard Score on file, the insurability value also reflects which carriers will write it: if every carrier we checked has declined it, it reads UNINSURABLE, and if carriers will write it only on conditions, or only a last-resort market will, it reads DIFFICULT rather than INSURABLE. Without a current Score on file it reflects the hazard picture alone. The three possible values haven't changed.

Salesforce doesn't let an app add custom fields, so these arrive switched off and an administrator creates them once:

1. In Salesforce Setup, go to Object Manager → Collateral → Fields & Relationships.
2. Create each field you want with its CoverGuard_ API name — for example CoverGuard_Flood_Zone__c (Text) and CoverGuard_In_SFHA__c (Text).
3. In CoverGuard, open the connection's page and switch those fields on in the mapping.

If you switch one on before it exists, the sync stops and names the exact field and type to create.

What it means

• Findings go onto collateral you already have. CoverGuard only ever updates the Collateral record a loan came with. It never creates loans, collateral or any other record in your org.
• A property in an undetermined flood zone is never reported as safe. If FEMA has no determination for the property, the SFHA field stays empty rather than reading NO.
• Loans land in a staging area first. Synced loans wait for you to review and promote them, unless you tick Bring new records in automatically on the connection's page.
• The risk check runs on its own. Promoting a loan starts its collateral's assessment in the background. Findings go back to nCino on the next sync after the assessment finishes, not the same one that brought the loan in.
• "Closed" in nCino means funded. A loan nCino calls closed stays active in your CoverGuard portfolio. Only withdrawn, declined or cancelled loans are treated as closed.
• What CoverGuard writes back is modeled. The insurability verdict and premium are CoverGuard's estimates, not an offer of insurance or a quote. Each field's description in Salesforce says so.

Tips

• Start with pulling loans in. See real loans arrive and get checked before you turn on anything that writes to nCino.
• Use a sandbox first if your bank has one. Choose Sandbox org on the connect screen.
• A large portfolio takes more than one run. The first sync works through your loans in batches; later runs only fetch what changed.

Troubleshooting

Do this next

• Portfolio screening — check thousands of loans at once from a spreadsheet.
• Flood compliance — what to do with a loan whose collateral is in a Special Flood Hazard Area.
• Integrations (Sys Admin) — syncing, promoting records, and connection health.