Bring every lead in from anywhere
you have data

The bulk import supports standard comma separated values files and Microsoft Excel files. The column mapping step lets you tell the importer which column in your file is the email, the company, the source, the score, or any custom field your workspace has defined. Mappings can be saved as templates and reused for the next import, so a recurring data onboarding job stops needing fresh configuration every time.

No, imports run on a background processing queue that is isolated from the live application. While the file is being processed, the rest of your team continues working in the platform with no impact on performance. The progress tracker keeps the user who started the import informed in real time, and the import completes in the background even if the user closes their tab.

The public lead application programming interface covers create, update, search, and retrieve operations on the full lead schema, including every custom field your workspace has defined. External systems can use it to add new leads, update existing records, search by any field, or pull back a single lead for display elsewhere. The full endpoint reference lives in the in app application programming interface documentation, next to the workspace data developers will be working against.

Open the settings panel, find the application programming interface key you want to rotate, and click regenerate. The old key is invalidated immediately, the new key is displayed once for you to copy into your integration, and the activity log records the rotation with a timestamp and the user who performed it. Best practice is to swap the new key into the integration first and then revoke the old one, with the activity log providing a clean audit trail of the change.

You create a webhook receiver in the integration settings and point your external system at the resulting endpoint. Each request is authenticated, the payload is validated against the expected schema, and the event is processed as a new lead, an update to an existing lead, or a trigger for an automation rule, depending on the receiver's configuration. Common patterns include form submissions from a marketing site, deal events from a billing platform, and lead handoffs from another system.

The in app application programming interface documentation lives inside the platform and always reflects the current version of the application programming interface. There is no separate documentation portal to keep in sync, no PDF being emailed around, no stale reference page on a marketing site. When an endpoint changes or a new field is added, the documentation updates with the deployment, so your developers always have the right reference open next to the data they are integrating with.