KamoCRM

Arive as a second external LOS, and a provider seam that is real

Featurekamo-shared-library
Dikirim
24 September 2026 pukul 04.38 UTC
Penulis
Kamo
Commit
efd305f

Arive is reachable only through its invite-only Zapier app, so the connection is Zapier in both directions: Kamo posts commands (create loan, update loan stage, update lead, convert lead) to per-market Catch Hooks, and Arive's triggers post back to a per-connection inbound token. The adapter, field mapper (three Arive namings, read from the live app), stage map, encrypted secrets and the activity log live in integrations.arive / integrations.los. LeadService no longer runs MeridianLink code for every link. Pushes go to the link's own LosProviderAdapter; a provider without one is skipped and logged instead of receiving a SOAP envelope. Inbound applies take a provider-neutral LosLeadPatch (contact, mailing address, mortgage facts, status) and attribute history to the provider. The resolver looks up member credentials by the connection's provider, and a market save with an unknown MLOS value is a 400 instead of a silent NO_MLOS. The columns this maps already exist in Yugabyte (LosAriveSchemaMigration's statements were applied before this push).

Semua perubahan

Seperti apa yang Anda lihat pengiriman?

Semua itu tiba di ruang kerjamu sendiri. Mulailah dengan rencana gratis dan baca halaman ini lagi dalam sebulan.

Mulai Bebas SelamanyaTampilkan Harga