Lusha integration.

Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Write-back support is not established for this connection. Review the Lusha records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup.

List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label.

Demonstrate how an existing record is found after a label change, and how a related record is resolved when its parent is missing. An update reaches the intended record, preserves its relationships, and performs each approved side effect once.

Estimate the number of Person Profiles, Company Profiles and Email Addresses records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades.