HUBSPOT N8N INTEGRATION: AUTOMATE HUBSPOT WITH N8N
Looking to automate HubSpot with n8n? You’re in the right place. The HubSpot n8n integration gives you access to 18 triggers and 31 actions to build powerful automations without writing a single line of code.
Whether you’re managing contacts, tracking deals, handling support tickets, or monitoring company activities, this integration lets you connect HubSpot to hundreds of other applications. You can automatically create contacts when forms are submitted, update deals when pipeline stages change, or trigger notifications when tickets are created—all running in the background while you focus on what matters.
In this guide, we’ll walk you through every trigger and action available, explain how to set up your connection, and show you exactly how to leverage this integration for your specific workflows.
Summary
WHY AUTOMATE HUBSPOT WITH N8N?
The HubSpot n8n integration gives you access to 18 triggers that monitor your CRM in real-time and 31 actions to manipulate your data automatically. This means you can build complete automation workflows that react instantly to changes in your HubSpot account and take action across your entire tech stack.
Significant time savings: No more manual data entry or copy-pasting between applications. Set up smart rules that automatically sync contacts, update deal stages, or create tickets based on specific conditions. What used to take hours of repetitive work now happens in milliseconds.
Improved responsiveness: Trigger instant actions as soon as a contact is created, a deal moves forward, or a support ticket comes in. Your team gets notified immediately, follow-ups happen faster, and nothing slips through the cracks.
Zero oversight: Triggers monitor your HubSpot account 24/7. Every new contact, every property change, every deleted record immediately triggers your workflow—even at 3 AM on a Sunday.
Concrete examples of what you can automate: sync new HubSpot contacts to your email marketing platform, create Slack notifications when high-value deals are created, automatically assign tickets based on priority, backup deleted records to Google Sheets, or enrich contact data using third-party APIs. The possibilities are virtually endless when you combine HubSpot’s robust CRM capabilities with n8n’s flexibility.
HOW TO CONNECT HUBSPOT TO N8N?
Basic configuration:
- Access your n8n credentials: Navigate to the Credentials section in your n8n instance and click “Add Credential.” Search for “HubSpot” and select the authentication method.
- Choose your authentication type: For most users, OAuth2 is the simplest option—click “Connect” and authorize n8n to access your HubSpot account. For developer accounts, you’ll need your API key from HubSpot’s settings.
- Configure your HubSpot Developer account (if using triggers): Some triggers require a HubSpot Developer account with webhook subscriptions. Create an app in your HubSpot developer portal and obtain the necessary credentials.
- Test the connection: Once configured, n8n will validate your credentials. You should see a success message confirming the connection is active.
- Start building: Your HubSpot nodes are now ready to use in any workflow. Drag them onto your canvas and select from available triggers or actions.
💡 TIP: If you’re using triggers extensively, make sure your HubSpot account has the appropriate subscription level—some webhook events require Professional or Enterprise plans. Also, consider creating a dedicated HubSpot app in your developer portal specifically for n8n integrations to keep your API usage organized and easier to monitor.
HUBSPOT TRIGGERS AVAILABLE IN N8N
HubSpot Trigger – Ticket Deleted
This trigger fires automatically whenever a ticket is deleted from your HubSpot account, allowing you to capture deletion events and respond accordingly. It’s essential for maintaining data integrity across your systems and ensuring you have a complete audit trail of support activities.
Configuration parameters: Select your HubSpot Developer account credentials from the dropdown (required). Specify the event type “Ticket Deleted” from a fixed list or use expressions. Optionally add multiple events or specify extra properties related to the deletion event.
Typical use cases: Automatically backup deleted ticket data to a spreadsheet before it’s permanently removed, send notifications to team managers when tickets are deleted unexpectedly, update external systems that track support metrics, or create audit logs for compliance purposes.
When to use it: Deploy this trigger when you need visibility into ticket deletions, whether for data backup, team oversight, or maintaining synchronized records across multiple platforms.
HubSpot Trigger – Deal Created
This trigger activates the moment a new deal is created in your HubSpot CRM, enabling instant follow-up workflows. It’s perfect for sales teams who want to automate their response to new opportunities without delay.
Configuration parameters: Select your HubSpot Developer credentials (required). Set the event name to “Deal Created” using fixed values or expressions (required). Optionally add additional events to monitor simultaneously or customize with extra data points.
Typical use cases: Automatically assign new deals to sales reps based on territory or deal size, send Slack notifications to the sales team when high-value deals enter the pipeline, create associated tasks or calendar events for follow-up, or sync new deals to external project management tools.
When to use it: Ideal for sales-driven organizations that want to accelerate their response time to new opportunities and ensure no deal goes unnoticed.
HubSpot Trigger – Ticket Created
This trigger monitors your HubSpot service hub and fires whenever a new support ticket is created. It enables your team to respond faster to customer issues and automate the initial triage process.
Configuration parameters: Select your HubSpot credentials via dropdown (required). Set the event name to “Ticket Created” using fixed values or dynamic expressions (required). Optionally add more event types or define custom fields for specific workflow requirements.
Typical use cases: Route tickets automatically based on category or priority, send instant notifications to support team channels, create related records in external ticketing systems, or trigger customer acknowledgment emails.
When to use it: Essential for customer support teams who want to minimize response times and automate the initial handling of incoming requests.
HubSpot Trigger – Conversation Deletion
This trigger activates when a conversation is deleted from HubSpot, helping you maintain records and audit trails for your customer communications.
Configuration parameters: Select your HubSpot Developer account credentials (required). Configure the event to “Conversation Deletion” (required). Optionally include additional event monitoring or define extra parameters for enhanced data capture.
Typical use cases: Archive deleted conversations to external storage before permanent removal, alert managers when conversations are deleted unexpectedly, maintain compliance records for regulated industries, or sync deletion events with CRM activity logs.
When to use it: Deploy when you need to track communication deletions for compliance, auditing, or data backup purposes.
HubSpot Trigger – Conversation Creation
This trigger fires when a new conversation begins in HubSpot, whether from live chat, email, or other channels. It’s your starting point for automating customer communication workflows.
Configuration parameters: Choose your authenticated HubSpot Developer account (required). Set the event to “Conversation Creation” using fixed or expression-based values (required). Optionally add more events to monitor or include custom properties as needed.
Typical use cases: Automatically assign conversations to available team members, trigger welcome messages or initial responses, log new conversations in external tracking systems, or alert specific teams based on conversation source.
When to use it: Perfect for businesses with high conversation volumes who want to automate routing and initial engagement.
HubSpot Trigger – Conversation Property Change
Monitor changes to conversation properties in HubSpot and trigger workflows when specific updates occur. This enables sophisticated automation based on conversation status changes.
Configuration parameters: Select your HubSpot Developer account via dropdown (required). Set the event to “Conversation Property Change” using fixed values or expressions (required). Optionally include additional event types or specify extra properties to capture with events.
Typical use cases: Trigger escalation workflows when conversation priority changes, update external dashboards when conversation status is modified, send notifications when conversations are reassigned, or sync property changes to analytics platforms.
When to use it: Use when you need granular control over conversation lifecycle management and want to automate responses to specific property changes.
HubSpot Trigger – Contact Deleted
This trigger activates when a contact is removed from your HubSpot database, ensuring you can maintain data integrity across all connected systems.
Configuration parameters: Select from your configured HubSpot Developer credentials (required). Configure the event to “Contact Deleted” (required). Optionally add additional events to monitor multiple types or include custom fields for additional context.
Typical use cases: Remove contacts from email lists in other marketing platforms, update CRM records in external systems, create deletion audit logs for compliance, or trigger GDPR compliance workflows.
When to use it: Essential for maintaining synchronized contact lists across your tech stack and ensuring compliance with data protection regulations.
HubSpot Trigger – Ticket Property Changed
This trigger fires when any property on a ticket is modified, giving you real-time visibility into support ticket updates.
Configuration parameters: Select HubSpot account credentials via dropdown (required). Set the event to “Ticket Property Changed” (required). Optionally include additional event monitoring or add custom parameters for specific workflow needs.
Typical use cases: Escalate tickets when priority is increased, notify team members when ticket status changes, update external project management tools, or trigger SLA monitoring workflows.
When to use it: Deploy for sophisticated support workflows that need to respond to specific ticket property changes in real-time.
HubSpot Trigger – Deal Deleted
Monitor deal deletions in your HubSpot CRM and trigger appropriate follow-up actions to maintain data consistency.
Configuration parameters: Select your HubSpot Developer account (required). Set the event to “Deal Deleted” for monitoring (required). Optionally add more event types if needed or customize with extra parameters.
Typical use cases: Backup deal data before permanent deletion, update sales forecasts in external tools, notify sales managers of unexpected deletions, or maintain audit trails for deal pipeline changes.
When to use it: Use when deal data integrity is critical and you need to track or respond to deal removals across your systems.
HubSpot Trigger – Conversation New Message
This trigger fires when a new message is received in a HubSpot conversation, enabling immediate response automation.
Configuration parameters: Select HubSpot Developer credentials (required). Configure for new message events via dropdown or expression (required). Optionally add more events to monitor or define additional properties as needed.
Typical use cases: Send instant notifications to support agents, auto-respond with relevant information based on message content, log messages to external systems, or trigger AI-powered response suggestions.
When to use it: Essential for teams wanting to minimize response times and automate initial message handling.
HubSpot Trigger – Conversation Privacy Deletion
This specialized trigger monitors privacy-related conversation deletions, crucial for GDPR and data privacy compliance workflows.
Configuration parameters: Select your HubSpot Developer account credentials (required). Set the event to “Conversation Privacy Deletion” (required). Optionally add additional events for comprehensive monitoring or include custom fields for compliance documentation.
Typical use cases: Document privacy deletions for compliance audits, update external consent management platforms, trigger data erasure across connected systems, or generate compliance reports automatically.
When to use it: Critical for organizations handling personal data who need to maintain comprehensive privacy deletion records.
HubSpot Trigger – Contact Privacy Deleted
This trigger activates when a contact is deleted for privacy reasons, supporting your data protection compliance efforts.
Configuration parameters: Select HubSpot Developer credentials via dropdown (required). Set the event to “Contact Privacy Deleted” for privacy-specific deletions (required). Optionally include additional event types or add custom parameters for compliance tracking.
Typical use cases: Execute right-to-be-forgotten requests across all systems, document privacy deletions for audit purposes, update consent records in external platforms, or trigger notification workflows for legal teams.
When to use it: Essential for GDPR compliance and organizations with strict data privacy requirements.
HubSpot Trigger – Deal Property Changed
Monitor changes to deal properties and trigger workflows based on specific updates—perfect for dynamic sales pipeline management.
Configuration parameters: Select your HubSpot Developer account (required). Set the event to “Deal Property Changed” (required). Optionally specify which property to monitor via the Property Name or ID field. Include additional event monitoring or customize with extra parameters as needed.
Typical use cases: Notify sales managers when deal amounts exceed thresholds, trigger follow-up tasks when deal stages change, update forecasting tools when close dates are modified, or sync deal changes to external reporting platforms.
When to use it: Ideal for sales operations that need granular visibility into pipeline changes and want to automate responses to specific deal updates.
HubSpot Trigger – Company Deleted
This trigger fires when a company record is deleted from HubSpot, enabling data cleanup workflows across your tech stack.
Configuration parameters: Select your HubSpot credentials (required). Configure the event to “Company Deleted” for company removal monitoring (required). Optionally add more events to monitor or include custom fields as needed.
Typical use cases: Remove company data from external databases, update account management systems, archive company information before final deletion, or trigger cleanup workflows in connected applications.
When to use it: Use when maintaining synchronized company records across multiple platforms is essential for your operations.
HubSpot Trigger – Company Property Changed
Monitor company property changes in real-time and trigger workflows based on specific field updates.
Configuration parameters: Select HubSpot Developer credentials (required). Set the event to “Company Property Changed” for update monitoring (required). Optionally specify the exact property to monitor via the Property Name or ID field. Add additional event types or customize with extra parameters as needed.
Typical use cases: Update account tiers in billing systems when company size changes, trigger outreach when company industry is updated, sync company data changes to external CRMs, or notify account managers of significant property updates.
When to use it: Perfect for account-based marketing and sales teams who need to respond dynamically to company profile changes.
HubSpot Trigger – Contact Property Changed
This trigger monitors changes to contact properties, enabling sophisticated contact lifecycle automation.
Configuration parameters: Select your HubSpot Developer credentials (required). Set the event to “Contact Property Changed” (required). Specify the exact property to track via the Property Name or ID field (required for precise monitoring). Optionally include additional events or add custom parameters for extended functionality.
Typical use cases: Trigger nurture campaigns when lead score reaches thresholds, update external marketing platforms when email preferences change, notify sales when contact lifecycle stage advances, or sync contact updates to customer success tools.
When to use it: Essential for marketing automation and lead management workflows that need to respond to specific contact attribute changes.
HubSpot Trigger – Company Created
This trigger activates when a new company is added to your HubSpot CRM, enabling immediate follow-up and data enrichment workflows.
Configuration parameters: Select your HubSpot Developer account (required). Set the event to “Company Created” to capture new company records (required). Optionally add additional event types if needed or include custom parameters for enrichment workflows.
Typical use cases: Automatically enrich new company data with third-party information, assign new companies to account executives based on territory, create associated tasks for account research, or sync new companies to external ABM platforms.
When to use it: Deploy when you want to automate the initial handling of new company records and ensure comprehensive account setup.
HubSpot Trigger – Contact Created
This trigger fires the moment a new contact enters your HubSpot database—the foundation for contact lifecycle automation.
Configuration parameters: Select your HubSpot Developer credentials (required). Set the event to “Contact Created” for new contact monitoring (required). Optionally add additional events for comprehensive monitoring or customize with extra parameters as needed.
Typical use cases: Automatically add new contacts to email sequences, enrich contact data using external APIs, trigger welcome communications, assign contacts to sales reps based on source or properties, or sync new contacts to other marketing platforms.
When to use it: This is often the most-used trigger for HubSpot automations—essential for any workflow that needs to respond to new leads or contacts entering your system.
NEED HELP AUTOMATING HUBSPOT WITH N8N?
We’ll get back to you in minutes ✔
HUBSPOT ACTIONS AVAILABLE IN N8N
Delete a ticket
This action removes a specific support ticket from your HubSpot account. Use it when you need to programmatically clean up resolved or duplicate tickets as part of your automation workflows.
Key parameters: Select your HubSpot authentication credentials (required). The resource is fixed to “Ticket” and the operation to “Delete”. Specify the ticket using “By ID” option—provide the ticket ID via text input or expression (required).
Use cases: Clean up spam or duplicate tickets automatically, remove test tickets after QA processes, archive and delete resolved tickets after backup, or maintain database hygiene through scheduled cleanups.
Delete a company
Remove a company record from HubSpot programmatically. This action is essential for maintaining clean company data and automating data management workflows.
Key parameters: Select HubSpot credentials (required). Resource is fixed to “Company” and operation to “Delete”. Identify the company using “By ID” option with the company’s unique identifier (required).
Use cases: Remove duplicate company records after merging, clean up test data from development workflows, process company deletion requests systematically, or maintain CRM hygiene through automated cleanup.
Create a company
Add new company records to your HubSpot CRM automatically. This action is fundamental for account-based marketing and sales workflows.
Key parameters: Select your HubSpot credentials (required). Resource is set to “Company” and operation to “Create”. Provide the company name via text input (required). Add custom properties like industry, size, website using “Add Property” (optional).
Use cases: Create company records from form submissions, import companies from external databases, auto-create companies when new domains are detected, or build company records from enrichment services.
Get Recently Created/Updated Companies
Retrieve company records that have been recently created or modified in HubSpot. Perfect for synchronization and monitoring workflows.
Key parameters: Select HubSpot credentials (required). Resource is set to “Company” and operation to “Get Recently Created/Updated”. Toggle “Return All” to retrieve all records or limit results (optional). Set the limit for maximum number of records (default: 100, required). Add specific properties to include in the response (optional).
Use cases: Sync recent company updates to external systems, monitor for new companies added by the sales team, build daily reports of company activity, or feed data warehouses with fresh company data.
Get a company
Retrieve detailed information about a specific company from HubSpot using its ID.
Key parameters: Select HubSpot authentication (required). Resource is set to “Company” and operation to “Get”. Identify via “By ID” with the company ID (required). Add specific properties to retrieve (optional).
Use cases: Fetch company details for enrichment workflows, retrieve company data for personalized communications, pull company information for reporting, or validate company records before updates.
Get many companies
Retrieve multiple company records from HubSpot in a single request. Ideal for bulk operations and reporting.
Key parameters: Select HubSpot credentials (required). Resource is set to “Company” and operation to “Get Many”. Toggle “Return All” for all records vs. limited set (optional). Set the limit for maximum records to retrieve (default: 100, required). Add filters or specific properties (optional).
Use cases: Export company lists for reporting, feed external analytics tools with company data, build bulk enrichment workflows, or create company segmentation analyses.
Update a company
Modify existing company records in HubSpot. Essential for keeping your company data current and accurate.
Key parameters: Select HubSpot credentials (required). Resource is set to “Company” and operation to “Update”. Identify using “By ID” with company ID, accepts expressions (required). Click “Add Field” to specify which properties to modify (optional but necessary for meaningful updates).
Use cases: Update company properties from enrichment sources, modify company stages in account pipelines, sync company data from external systems, or apply bulk updates based on business rules.
Create or update a contact
This powerful action creates a new contact or updates an existing one based on email address. It’s the most flexible way to manage contact data in HubSpot.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact” and operation to “Create or Update”. Provide the contact’s email address—used as the unique identifier (required). Add properties like name, phone, company (optional). Include additional configuration options (optional).
Use cases: Sync contacts from external forms without worrying about duplicates, update contact properties when new information is available, import contacts from other platforms with automatic deduplication, or process lead data from multiple sources.
Delete a contact
Remove a contact from your HubSpot database. Use carefully as part of data cleanup or compliance workflows.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact” and operation to “Delete”. Identify via “By ID” with the contact ID (required).
Use cases: Process unsubscribe requests with full deletion, remove bounced or invalid contacts, clean up test data, or handle GDPR erasure requests.
Get Recently Created/Updated Contacts
Fetch contacts that have been recently added or modified. Essential for keeping external systems synchronized with HubSpot.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact” and operation to “Get Recently Created/Updated”. Toggle “Return All” for complete vs. limited results (optional). Set the limit for maximum contacts to return (default: 100, required). Specify additional properties to include (optional).
Use cases: Sync new leads to email marketing platforms, update external databases with recent contact changes, build daily lead reports, or feed sales dashboards with fresh data.
Get many contacts
Retrieve multiple contacts from HubSpot in bulk. Perfect for exports, reporting, and large-scale data operations.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact” and operation to “Get Many”. Toggle “Return All” for all contacts vs. limited (optional). Set the limit for maximum records (default: 100, required). Add filters or property specifications (optional).
Use cases: Export contact lists for external campaigns, feed analytics platforms with contact data, build comprehensive contact reports, or create backup snapshots of contact database.
Get a contact
Retrieve detailed information about a specific contact using their ID.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact” and operation to “Get”. Identify via “By ID” with contact ID (required). Specify additional properties to retrieve (optional).
Use cases: Fetch contact details for personalization, retrieve contact data for enrichment workflows, pull contact information for customer communications, or validate contact records before processing.
Remove a contact from a list
Remove a specific contact from a HubSpot contact list. Essential for list management and segmentation workflows.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact List” and operation to “Remove”. Provide the contact identifier—email or ID (required). Specify the list ID from which to remove the contact (required).
Use cases: Remove unsubscribed contacts from marketing lists, clean up list segmentation based on new criteria, process opt-out requests automatically, or manage list membership dynamically.
Add a contact to a list
Add an existing contact to a specific HubSpot list. Key for segmentation and campaign targeting.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact List” and operation to “Add”. Choose how to identify the contact via “By” parameter, e.g., “Email” (required). Provide the contact’s email address (required). Specify the numeric ID of the target list (required).
Use cases: Add leads to nurture campaign lists, segment contacts based on behavior or properties, build targeted campaign audiences, or organize contacts for sales outreach.
Search contacts
Search for contacts in HubSpot using custom filter criteria. Powerful for finding specific contacts or segments.
Key parameters: Select HubSpot credentials (required). Resource is set to “Contact” and operation to “Search”. Toggle “Return All” for complete results (optional). Set the limit for maximum results (default: 100, optional). Define search criteria using filter groups (optional). Add additional search configuration (optional).
Use cases: Find contacts matching specific criteria for campaigns, search for contacts by custom property values, build dynamic segments based on multiple conditions, or locate contacts for targeted outreach.
Get a deal
Retrieve detailed information about a specific deal from your HubSpot pipeline.
Key parameters: Select HubSpot credentials (required). Resource is set to “Deal” and operation to “Get”. Identify via “By ID” with deal ID (required). Add specific conditions or property requests via filters (optional).
Use cases: Fetch deal details for reporting, retrieve deal data for external integrations, pull deal information for commission calculations, or validate deal records before processing.
Get many deals
Retrieve multiple deals from HubSpot in a single operation. Essential for pipeline reporting and analysis.
Key parameters: Select HubSpot credentials (required). Resource is set to “Deal” and operation to “Get Many”. Toggle “Return All” for complete data retrieval (optional). Set the limit for maximum deals to return (default: 100, required). Add custom configurations via options (optional).
Use cases: Export deals for sales reporting, feed forecasting tools with pipeline data, build deal analytics dashboards, or sync deals to external CRM systems.
Create a deal
Add new deals to your HubSpot sales pipeline programmatically.
Key parameters: Select HubSpot credentials (required). Resource is set to “Deal” and operation to “Create”. Provide the deal stage name or ID for the pipeline stage (optional but recommended). Add custom properties using “Add Field” (optional).
Use cases: Create deals from form submissions, auto-generate deals from qualified leads, import deals from external sources, or build deals from integration triggers.
Delete a deal
Remove a deal from your HubSpot pipeline. Use for cleanup and data management workflows.
Key parameters: Select HubSpot credentials (required). Resource is set to “Deal” and operation to “Delete”. Identify via “By ID” with deal ID (required).
Use cases: Remove duplicate deals after merging, clean up lost or cancelled deals, delete test deals from development, or process deal removal requests.
Update a deal
Modify existing deal properties in HubSpot. Critical for pipeline management automation.
Key parameters: Select HubSpot credentials (required). Resource is set to “Deal” and operation to “Update”. Identify via “By ID” with deal ID (required). Click “Add Update Field” to specify properties to change (optional but necessary for updates).
Use cases: Update deal stages based on external triggers, modify deal amounts from pricing integrations, change deal owners based on assignment rules, or sync deal updates from external systems.
Get Recently Created/Updated Deals
Fetch deals that have been recently created or modified. Perfect for pipeline monitoring and synchronization.
Key parameters: Select HubSpot credentials (required). Resource is set to “Deal” and operation to “Get Recently Created/Updated”. Toggle “Return All” for complete retrieval (optional). Set the limit for maximum deals (default: 100, required). Add property specifications via options (optional).
Use cases: Sync recent deal changes to reporting tools, monitor pipeline activity in real-time, feed sales dashboards with fresh data, or track deal movement for forecasting.
Search for deals
Search your HubSpot deals using custom filter criteria for targeted retrieval.
Key parameters: Select HubSpot credentials (required). Resource is set to “Deal” and operation to “Search”. Toggle “Return All” for complete results (optional). Set the limit for maximum results (default: 100, optional). Define search criteria via filter groups (optional). Add additional search parameters (optional).
Use cases: Find deals in specific stages for reporting, search for deals by amount or close date, build dynamic deal segments, or locate deals for targeted follow-up.
Get an engagement
Retrieve details about a specific engagement (call, email, meeting, etc.) from HubSpot.
Key parameters: Select HubSpot credentials (required). Resource is set to “Engagement” and operation to “Get”. Identify via “By ID” with engagement ID (required).
Use cases: Fetch engagement details for activity reporting, retrieve engagement data for customer history, pull engagement information for analytics, or validate engagement records.
Create an engagement
Log new engagements (calls, emails, meetings, tasks) in HubSpot programmatically.
Key parameters: Select HubSpot credentials (required). Resource is set to “Engagement” and operation to “Create”. Specify the engagement type like call, email, meeting (optional but recommended). Add specific properties using “Add Property” (optional).
Use cases: Log calls from external phone systems, create meeting records from calendar integrations, record email activities from external platforms, or build comprehensive activity timelines.
Delete an engagement
Remove an engagement record from HubSpot.
Key parameters: Select HubSpot credentials (required). Resource is set to “Engagement” and operation to “Delete”. Identify via “By ID” with engagement ID (required).
Use cases: Remove duplicate engagement records, clean up test engagements, delete erroneous activity logs, or process engagement removal requests.
Get many tickets
Retrieve multiple support tickets from HubSpot in bulk.
Key parameters: Select HubSpot credentials (required). Resource is set to “Ticket” and operation to “Get Many”. Toggle “Return All” for all tickets vs. limited (optional). Set the limit for maximum tickets (default: 100, required). Add custom configurations via options (optional).
Use cases: Export tickets for support reporting, feed external ticketing analytics, build support dashboard data, or sync tickets to external helpdesk systems.
Create a ticket
Add new support tickets to HubSpot programmatically.
Key parameters: Select HubSpot credentials (required). Resource is set to “Ticket” and operation to “Create”. Provide the pipeline name or ID for the support pipeline (required). Specify the stage name or ID for the initial stage (required). Enter the ticket name/title (required). Add custom properties using “Add Property” (optional).
Use cases: Create tickets from form submissions, generate tickets from external support channels, auto-create tickets from monitoring alerts, or import tickets from other helpdesk systems.
Get many engagements
Retrieve multiple engagement records from HubSpot.
Key parameters: Select HubSpot credentials (required). Resource is set to “Engagement” and operation to “Get Many”. Toggle “Return All” for complete retrieval (optional). Set the limit for maximum engagements (default: 100, optional).
Use cases: Export activity data for reporting, analyze engagement patterns, feed activity analytics platforms, or build comprehensive activity reports.
Search for a company by domain
Search for companies in HubSpot using their website domain—a powerful way to find and deduplicate company records.
Key parameters: Select HubSpot credentials (required). Resource is set to “Company” and operation to “Search”. Provide the website domain to search for (optional). Toggle “Return All” for all results (optional). Set the limit for maximum results (default: 100, required). Add additional search parameters via options (optional).
Use cases: Find companies by website during lead enrichment, check for existing companies before creation, deduplicate company records, or match companies from external data sources.
Update a ticket
Modify existing ticket properties in HubSpot.
Key parameters: Select HubSpot credentials (required). Resource is set to “Ticket” and operation to “Update”. Identify via “By ID” with ticket ID (required). Click “Add Field” to specify properties to modify (optional but necessary for updates).
Use cases: Update ticket status from external systems, modify ticket priority based on SLA rules, change ticket assignments automatically, or sync ticket updates from other helpdesk tools.
Get a ticket
Retrieve detailed information about a specific support ticket.
Key parameters: Select HubSpot credentials (required). Resource is set to “Ticket” and operation to “Get”. Identify via “By ID” with ticket ID (required). Add specific properties to retrieve via options (optional).
Use cases: Fetch ticket details for notifications, retrieve ticket data for reporting, pull ticket information for escalation workflows, or validate ticket records before processing.
NEED HELP AUTOMATING HUBSPOT WITH N8N?
We’ll get back to you in minutes ✔
FREQUENTLY ASKED QUESTIONS ABOUT HUBSPOT N8N INTEGRATION
Is the HubSpot n8n integration free?
The integration itself is free to use with both n8n cloud and self-hosted versions. However, you'll need an active HubSpot account, and some features—particularly certain webhook triggers—may require HubSpot Professional or Enterprise plans. For example, real-time event triggers using webhooks require a HubSpot Developer account and may have limitations based on your HubSpot subscription tier. The n8n cloud platform has its own pricing based on workflow executions, while self-hosted n8n is completely free. Always check your HubSpot plan's API limits to ensure your automation volume is supported.
What data can I sync between HubSpot and n8n?
You can sync virtually all core HubSpot data including contacts, companies, deals, tickets, and engagements. With 18 triggers monitoring events like contact creation, deal updates, ticket changes, and property modifications, plus 31 actions covering create, read, update, and delete operations, you have comprehensive access to your HubSpot data. You can also work with contact lists, search across records using filters, and retrieve recently modified data for efficient synchronization. This makes it possible to build two-way syncs with external CRMs, marketing platforms, helpdesks, spreadsheets, databases, and hundreds of other applications.
How long does it take to set up the HubSpot n8n integration?
Most users can connect HubSpot to n8n in under 5 minutes using OAuth2 authentication—simply click "Connect," authorize access, and you're ready to build workflows. For triggers using webhooks, you'll need a HubSpot Developer account which adds about 10-15 minutes for initial setup (creating an app, configuring webhook subscriptions). Building your first complete workflow typically takes 15-30 minutes depending on complexity. The visual workflow builder makes it easy to drag, drop, and configure nodes without any coding. More sophisticated automations with multiple conditions and branches might take a few hours to design and test properly.