How do I connect my document repository to my ERP or CRM?
Link each business record to FormKiQ document/site identifiers, then synchronize approved metadata through APIs and document events. A separately scoped Integration Framework can provide the agreed ERP or CRM integration. Define ownership, mappings, permissions, retries, and reconciliation explicitly. An event notification alone does not create reliable two-way synchronization or a connector for every vendor and version.
Establish the record contract
Choose the source of truth for each field. An ERP may own vendor identity while FormKiQ owns source documents and processing state. Store the ERP record identifier in a defined attribute and the FormKiQ document/site identifiers in the ERP or integration store.
Define which changes travel in each direction and which require human approval. Protect credentials, constrain destinations, and use a site-scoped integration identity. Keep a business metadata change separate from permission to send a document outside the repository.
Handle uncertainty
Persist an operation/source key so repeated events do not create duplicate records. Re-read current state instead of assuming an older event contains the final metadata. Bound retries, monitor exhausted failures, and periodically reconcile both systems with complete pagination.
Test a timed-out successful write, source deletion, a retained or held document, and revoked integration access. Confirm what data the external system stores and how its retention and processing geography affect the deployment's controls.
Edition and configuration
Core supports APIs and events for custom adapters. Integration Frameworks are separately scoped for Advanced/Enterprise; vendor/version support, mappings, external licenses, and implementation are agreed.