Integrations (HubSpot, Salesforce, Slack)
The integrations your sales team actually needs are gated behind Business, and even then field mapping is rigid and brittle.
What people actually say
✕Typeform's native integrations to CRMs like HubSpot have rigid field maps that require advance planning, and minor field changes can break the entire workflow downstream.
Source: Default, Typeform HubSpot integration guide ↗✕A form already wired to HubSpot via Typeform's native integration cannot simultaneously be connected to Salesforce through the native integration — you have to pick one CRM or route through Zapier.
Source: Default, Typeform HubSpot integration guide ↗✕HubSpot users report Typeform submissions being misattributed as direct traffic rather than the originating source, breaking ROI and channel reporting.
Source: HubSpot Community, Typeform source tracking ↗
Submissions hit a typed handler in your codebase that fans out to HubSpot, Salesforce, Slack and your warehouse in parallel — using each vendor's real API, not Typeform's middleware. Field mapping lives in code (one source of truth), retries are durable via Inngest, and source attribution is preserved end-to-end.