Integrations
Vesso helps teams centralize GTM work across CRM records, calendars, campaigns, analytics, spreadsheets, and operational workflows.
- Records are matched first on the external record ID, so a second run recognizes everything the first run brought over.
- Accounts also match on an exact company name, and contacts on email address. A match is skipped, never overwritten. Edits you made in Vesso are safe.
- Each run reads up to 5,000 records per object. If a run is truncated, the summary says so.
- Re-running an import is safe at any time, and disconnecting leaves every imported record in Vesso.
Once a CRM is connected, the Customer Data Platform can keep it in step with Vesso. Sync is off until a workspace admin enables it for that connection, and it is configured per field rather than per object.
- Direction per field: two-way, inbound only, outbound only, or off.
- Conflict policy per field, for when both sides changed since the last pass: last write wins, Vesso wins, the CRM wins, or send it to the review queue.
- Vesso stores the value both systems last agreed on, so one-sided changes apply quietly and Vesso’s own write coming back is recognized rather than re-applied.
- Opportunity stage maps inbound only by default, because pushing a stage needs the other CRM’s own picklist vocabulary. Map it outbound deliberately.
- Computed values such as MRR, lifetime value and renewal date can be pushed out to a custom field or property you nominate.
- Scheduled syncs run every 15 minutes, and a change made in Vesso is queued for push immediately.
CSV and spreadsheet imports
Bring in accounts, contacts, and pipeline data from existing systems using structured imports.
Public API beta
Enabled workspaces can use API keys to read and write CRM records, update tasks, and send product events into Vesso.
Signed outbound webhooks
Subscribe HTTPS endpoints to Vesso activity and verify deliveries with HMAC signatures.
For one-time migrations from a CRM we do not connect to yet, start with CSV exports and the in-app import workflow. For recurring syncs, product events, or workflow handoffs, enabled workspaces can use the Public API v1 beta and outbound webhooks. If API access is not visible in your workspace yet, contact support@vesso.ai so we can review the integration and enable the right access model.
- Choose the source object and matching Vesso object.
- Map required fields first, then optional enrichment fields.
- Decide which fields should be maintained in Vesso after import.
- Test with a small sample before importing a full dataset.
Data hygiene tip
Normalize company domains, owner names, lifecycle stages, and email addresses before large imports. Clean source data makes reporting and routing more reliable.