HubSpot · CRM integrations
HubSpot CRM automation and integration work.
HubSpot is most useful when the record stays trustworthy while work moves around it. These examples show how I have connected HubSpot to lead sources, external data, routing logic, AI-assisted follow-up, and team handoffs.
What I focus on
Keep identity, lifecycle state, ownership, and the next action clear inside the CRM. Then use native workflows or external orchestration only where another system genuinely needs to participate.
The public workflow files below are evidence of the integration logic. They use placeholder credentials and resource identifiers so the implementation can be reviewed without exposing client data.
Workflow evidence
Real portfolio workflows that use HubSpot as part of the operating path.
Airtable to HubSpot two-way sync
Keeps reviewed Airtable leads and HubSpot records aligned, including company and contact creation plus sync-back status.
HubSpot · Airtable · n8n
Dynamic HubSpot lead distribution
Uses lead context and team data to qualify incoming HubSpot leads, check fit and capacity, and route the record to the right owner.
HubSpot · Airtable · AI · Slack · n8n
AI sales follow-up engine
Looks up CRM context in HubSpot, prepares follow-up support, and keeps the team aware of leads that still need attention.
HubSpot · OpenAI · Slack · n8n
Multi-source lead routing
Brings leads from several sources into one CRM path so qualification, ownership, follow-up, and record updates stay connected.
Typeform · HubSpot · Airtable · Google Sheets · Gmail · n8n
FAQ
What kind of HubSpot automation work is shown here?
The examples focus on CRM-connected operations: creating and updating records, keeping external data aligned with HubSpot, routing leads, using CRM context in follow-up, and moving information between HubSpot and the rest of the stack.
Are these HubSpot-native workflows or external integrations?
These examples are primarily integration workflows built around HubSpot as a CRM system of record. When a process can stay cleanly inside HubSpot, native automation is often simpler. External orchestration is useful when data or actions need to move across several systems.
Can the workflow JSON files be imported as-is?
They are portfolio examples for review and adaptation, not turnkey production deployments. Credentials, resource identifiers, field mappings, routing rules, permissions, and failure handling need to be configured for the real account before activation.
Related proof
Related guides