Integrations
Avocet CRM connects to two things today: CSV import from any CRM, and read-only Gmail. Live HubSpot and Salesforce connectors, Google Calendar, Slack and call transcripts are next, in that order, and only after paying customers ask for them. Everything else is not planned.
| Integration | Status | What it does |
|---|---|---|
| CSV import (any CRM) | Available | Companies, people and deals with field mapping, preview and dedupe review |
| Gmail | Available, read-only | Normalises messages into account and deal timelines |
| HubSpot (live, two-way) | Planned | Continuous sync instead of periodic CSV |
| Salesforce (live, two-way) | Planned | Continuous sync instead of periodic CSV |
| Google Calendar | Planned | Meeting attendance as a deal signal |
| Slack | Planned | Digest delivery where the team already reads |
| Call transcripts (Gong, Fireflies) | Planned | Commitments and risk from spoken conversation |
| Microsoft 365 / Outlook | Under consideration | — |
| Zapier, generic webhooks | Not planned | — |
| Marketing automation | Not planned | Use HubSpot or Marketo; we will not compete here |
Why start with CSV rather than a live connector?
Because CSV works on day one for every CRM at once, and a live connector works for one CRM after an OAuth review. Reading a real HubSpot export tells us more about your data than a beautifully engineered sync we cannot ship for six weeks.
CSV import is also the honest test of the wedge. If importing your pipeline and reading one mailbox does not produce something useful, a live connector would not have saved it.
Why is Gmail read-only, and what is the verification status?
Read-only because Avocet CRM has no reason to send or modify mail, and every additional permission is a larger blast radius in an incident. Reading message bodies is a restricted Google scope, which requires app verification plus an independent security assessment — we are in that process, and until it completes there is a cap on the number of accounts that can connect.
This is why the seeded demo workspace exists. You can see exactly what the output looks like without hitting an OAuth screen at all.
How large a file can I import?
Large enough for a real CRM export. Uploads go from your browser straight to storage using a signed URL, so they are not limited by an API request body size, and the import itself runs as a background job with durable steps and retries.
A 50,000-row import with deduplication and enrichment cannot complete inside an HTTP request, and pretending otherwise is how imports silently truncate. Avocet creates a job, returns immediately, and shows you progress.
Why no Zapier or generic webhooks?
Because a generic integration surface commits us to supporting every shape of data anyone sends, which is a permanent tax on a small team and produces records nobody can vouch for. We would rather support four integrations properly than four hundred nominally.