Connect ARIVE to Loan Certifier in 4 simple steps. Loans, documents, and statuses sync automatically — no manual data entry.
Before You Start
1
ARIVE Broker Pro account with admin access
You need access to Admin → API Integrations tab in ARIVE.
2
A Zapier account
Free plan allows 100 tasks/month. For active pipelines, consider a paid plan (Starter: $19.99/mo = 750 tasks).
3
Company Admin access in Loan Certifier
Go to Integrations → ARIVE LOS → Configure.
Step 1: Connect Your ARIVE Account
Paste your ARIVE API key to activate the integration
Get your ARIVE Zapier API key:
Log into ARIVE → Admin → API Integrations
Find the Zapier API Key section
Copy the key
Paste it into Loan Certifier:
Go to Integrations → ARIVE LOS → Configure
Paste the key into the ARIVE Zapier API Key field
Click Connect
Your webhook URL is auto-generated — no need to manually create a secret.
Step 2: Copy Your Webhook URL
Loan Certifier generates this automatically — just copy it
In the ARIVE config dialog, your Webhook URL is shown and ready to copy. Click the Copy button — you'll paste this into Zapier in the next step.
The URL looks like: https://app.loancertifier.com/functions/ariveWebhook?company_id=...&secret=...
Step 3: Create Your Zapier Zap
Bridge ARIVE events to Loan Certifier
Trigger (When this happens):
App: ARIVE (connect using your ARIVE Zapier API key)
Event: Choose the trigger (e.g., "New Application", "Loan Status Changed", "Document Uploaded")
Action (Do this):
App: Webhooks by Zapier
Event: POST
URL: Paste your Loan Certifier Webhook URL from Step 2
Payload Type: JSON
Map these ARIVE fields to the webhook payload:
Loan Certifier Field
Map from ARIVE
Required
event_type
loan_created / status_updated / document_uploaded
✅
loan_number
ARIVE loan/file number
✅
borrower_name
Borrower full name
✅
borrower_email
Borrower email
—
borrower_phone
Borrower phone
—
loan_amount
Loan amount
—
interest_rate
Interest rate
—
property_address
Subject property address
—
loan_type
Loan program/type
—
lender_name
Lender name
—
status
ARIVE loan status (for status events)
—
document_name
Document file name
—
document_url
Document download URL
—
Tip: One Zap per event type (recommended)
Create a separate Zap for each ARIVE trigger and append the event type to the webhook URL so Loan Certifier always knows what happened — even if you forget to map event_type in the payload:
New Application → &event_type=loan_created
Loan Status Changed → &event_type=status_updated
Document Uploaded → &event_type=document_uploaded
If event_type is omitted entirely, Loan Certifier now auto-infers it from the payload shape (document fields → document_uploaded, a status field → status_updated, a loan number/borrower → loan_created), so loans still sync.
Step 4: Test & Publish
Verify everything works, then turn it on
In the ARIVE config dialog, click Test Connection to verify your webhook is live
In Zapier, click Test Trigger and send a test event
You should see a success response — then click Publish
Check your Loan Certifier Loans page — the test loan should appear
Optional: Outbound Sync (Push to ARIVE)
Send certification statuses back to ARIVE
Create a new Zapier Zap with trigger Webhooks by Zapier → Catch Hook
Copy the Zapier webhook URL
In Loan Certifier → ARIVE config → paste it into Zapier Catch Hook URL
When you certify a loan or resolve a condition, the update automatically pushes to ARIVE.
Troubleshooting
Webhook returns 403 Forbidden
The webhook secret in the URL doesn't match what's saved. Click "Regenerate" in the ARIVE config and update your Zapier URL.
Test succeeds but no loan appears
Make sure your Zap includes loan_number and a borrower name in the POST data. event_type is recommended but no longer required — if it's missing, Loan Certifier auto-infers it from the payload (or append &event_type=loan_created to your webhook URL).
Documents aren't transferring
In Zapier, select the file field (not just the URL text). The field should show a download icon. ARIVE documents are fetched and stored permanently in Loan Certifier.
Need help? Contact your company admin or submit a support ticket from the Improvement Center.