--- title: "HubSpot Integration in 2 to 6 Weeks | JustAutomate" description: "We connect HubSpot to your forms, inbox, invoicing, orders and warehouse, and set which property is the system of record. Live in 2 to 6 weeks." url: "https://justautomate.ai/en/integrations/hubspot/" lang: en --- CRM and sales # HubSpot integration wired into what you already run HubSpot holds your contacts, companies and deals, and knows nothing about what happens in the inbox, in the invoicing system and in the orders spreadsheet. We connect it to those systems through the API and webhooks, decide which HubSpot property is the system of record for which piece of information, and split the logic between HubSpot workflows and an external orchestrator. Book a free consultation [See how the workshop works](https://justautomate.ai/en/services/process-workshop/) - 14 daysfrom the workshop to the first automation running in your own HubSpot account, on real data - 2 to 6 weeksfrom the workshop to a connected HubSpot, depending on how many systems are in scope and the state of the database - 5 to 10 secondshow long BOND takes to answer a question about HubSpot data, with no CRM login The problem ## Why does HubSpot know less about your customer than your inbox does? A rep finishes a call and types what was agreed into an email, because that is faster. The invoice sits in the invoicing system, the order in the e-commerce back office, the forecast in a spreadsheet, and the deal in HubSpot is still on the stage it reached last week. When the customer calls to ask about a payment, someone opens three tabs to work out which version of the truth is current. The reason is the same in every company. HubSpot was bought as a CRM for sales, and then nobody decided which piece of information lives in HubSpot and which one lives in the system next to it. Each system spells the same company differently, so there is no way to line them up without a shared identifier. Instead of an integration you end up with a social contract: the rep will retype it by hand when somebody needs it. The third thing is technical and it decides the rest. A HubSpot property has a label the rep sees, and an internal name every integration refers to. The label you can change whenever you like. The internal name you cannot change once the field exists, which is set out in [HubSpot's developer documentation](https://developers.hubspot.com/). So an "Industry" field created as plain text stays plain text, and every rule meant to branch on it inherits that mess. - A rep copies the invoice number and payment status out of the invoicing system into a HubSpot note - The same company sits in HubSpot twice, because each system spells its name differently - Nobody knows which campaign the deal you signed actually came from - A form submission waits until morning, when a webhook could have delivered it in a second - The forecast is built in a spreadsheet, because HubSpot data has to be pasted into it by hand Why now ## What changed, so that connecting HubSpot takes weeks rather than a quarter? HubSpot exposes a REST API and event webhooks, so a new contact or a stage change can be picked up a second after it happens. Nothing has to poll the system every 15 minutes and no connector has to be written from scratch. The technical layer, meaning endpoints, authentication and rate limits, is documented in [HubSpot's developer documentation](https://developers.hubspot.com/), and how we build against it is described on our [API integration services](https://justautomate.ai/en/services/api-integration/) page. This page is about what follows from all that for the process. The second change is about where the logic lives. A HubSpot workflow is the best place for rules that concern HubSpot alone: a task after a stage change, a reminder about a deal with no movement, an email sequence. When a rule has to ask the invoicing system about a payment status, check stock in the e-commerce back office and only then move the stage, that logic goes to [n8n](https://justautomate.ai/en/services/n8n-automation/) or Make, and HubSpot stays the place the result is written. Tier matters here too: custom objects start at Enterprise and workflows at Professional, so some companies have to keep logic outside HubSpot even when they would rather not. The third change is the AI agent. A rule does what it was told, but it will not answer the question of how many deals have sat at the quote stage for longer than 14 days. BOND, our company AI agent, answers that in a plain sentence in 5 to 10 seconds, reading from HubSpot, with no CRM login and no report request. What changes ## What do you get out of a connected HubSpot? - ### Data reaches HubSpot without retyping A form submission, an email, a meeting, an invoice and an order land on the record by themselves, a second after the event. The rep does not open a second tab to check whether the customer has paid. Webhooks and the API instead of copy and paste across three systems - ### Every piece of information has one system of record At the workshop we settle which HubSpot property is the system of record for which piece of information, and which system is allowed to overwrite it. Only then do two reports stop showing a different total. A property list with its source system and owner, written on one page - ### Invoice and order visible on the deal Invoice number, payment status and due date land as custom properties on the deal, not in a note. The person chasing the payment sees them on the record they already work in. Custom properties on the deal instead of a note nothing can filter on - ### Logic lives where it belongs A rule about HubSpot alone stays in a HubSpot workflow, because that is where you can change it without us. A rule that queries other systems goes to n8n or Make, where you can see which step it failed on. The split written down at the workshop, rule of thumb: one system means a workflow, several mean an orchestrator - ### A migration that leaves the mess behind Before the import we clean the data on a copy: duplicates by VAT number and email domain, closed value lists instead of text fields, property internal names settled once. What goes into HubSpot is what you can filter on. Import after the merge rules are approved, not before - ### A question about HubSpot without opening HubSpot The warehouse, finance and the board ask about a customer in a plain sentence and get an answer from current data. Nobody learns CRM views in order to check one number once a week. An answer from HubSpot in 5 to 10 seconds, with no report to build Proof ## Do you run HubSpot this way yourselves? Yes. Since March 2026 HubSpot in our founders' agency has been run by an AI agent, the same one behind the numbers on our AI automation agency page. Below is the scale of that work, together with what the number does NOT prove. Built for ourselves. These are not client deployments but implementations inside the founders' own companies. We say so plainly, because proof you cannot verify is not proof. - ![JustIdea Agency](https://justautomate.ai/klienci/justidea.png)![JustBot](https://justautomate.ai/agenci/justbot-80.webp)JustBottheir agent JustIdea Agency, a performance marketing agency of around 30 people 23 people from the company work with the agent 38 systems wired in permanently 112 processes run without a human 475 thousand lines of the agent’s code The agent is wired into HubSpot, the website forms, Slack and the data warehouse. Records are created from form submissions, from ads and from referrals. 8 of 38 systems it works in - Google Ads - Meta Ads - HubSpot - ActiveCollab - Ahrefs - GA4 - Search Console - BigQuery Before A person created the contact and the company in HubSpot: read the enquiry, retyped the details out of the email and checked by hand whether the company was already there. How complete the data was depended on who happened to have time. After The agent creates the contact and the company in HubSpot, checks for a duplicate by domain, fills in the company details and notifies the team on Slack. A person steps in at the conversation, not before. 3,432 operations on leads and 1,301 on form submissions in 30 days, with no human involved And in your company ## What if our HubSpot looks different? Four sentences come up most often, and this is how we answer them. If you are after something next to this, there are separate pages: [CRM automation](https://justautomate.ai/en/services/crm-automation/) when the problem is the way people work in the CRM, [CRM implementation](https://justautomate.ai/en/services/crm-implementation/) when there is no HubSpot yet, and [Pipedrive integration](https://justautomate.ai/en/integrations/pipedrive/) or [Salesforce integration](https://justautomate.ai/en/integrations/salesforce/) when you are comparing systems. Contact data is processed under [Regulation 2016/679](https://eur-lex.europa.eu/eli/reg/2016/679/oj), so we set the retention period for records that never entered the sales process together with you. - We are on free HubSpot and we are not buying Enterprise. Then we start by checking what your tier actually gives you, because HubSpot ties features to tiers: custom objects start at Enterprise, workflows at Professional. A free account and Starter are workable, the logic simply lives in n8n or Make and HubSpot is the place the result is written. We will tell you plainly whether a higher tier pays off for you or whether an external orchestrator does the same job for less. - We already have workflows in HubSpot and they work. Good, and most of them usually stay. We check what they stand on: a workflow that splits deals on a free-text field works exactly as well as that field is filled in. We rewrite only the rules that read fields with no closed list behind them, or that try to imitate an integration with a system HubSpot cannot reach on its own. - Our HubSpot is a mess after a migration from a spreadsheet. Almost every one is, so the cleanup comes before the integration rather than after it. We read the whole record set through the API and hand you a report: which properties are actually filled in, how many duplicates there are, which fields were created as text instead of a closed list. Merging follows rules you approve and runs on a copy first, because a property internal name cannot be changed after the fact. - We do not want customer data leaving HubSpot. We send the orchestrator only the fields a decision needs, and we agree that list at the workshop, field by field. If the condition is no processing outside HubSpot at all, we build as much as HubSpot workflows allow and say plainly what drops out of scope under that constraint. The workflow can also run on your own infrastructure, in which case the data never leaves your servers. HubSpot Contacts, companies, deals, tickets, custom properties, webhooks, workflows Forms and enquiries HubSpot forms, website form, Meta Lead Ads, LinkedIn Lead Gen Forms, live chat Invoicing and orders Xero, sevDesk, Fakturownia, Comarch Optima, BaseLinker, Shopify, WooCommerce, PrestaShop Team tools Google Workspace, Microsoft 365, Slack, Notion, ClickUp, Jira, Asana Data and warehouse BigQuery, Google Sheets, Google Analytics, SQL databases Automation layer Make, n8n, Zapier, custom API integrations ## What we connect to HubSpot most often, and where the result lands Seven connections we are asked about most. The third column matters most here, because the system of record settles every later argument about which number is true. | System | What moves across | Where it lands in HubSpot | | --------------------------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------------------------- | | HubSpot forms and the website form | the enquiry with its message, the channel and utm parameters | contact and company, source properties, a task for the owner | | Inbox and calendar: Google Workspace, Microsoft 365 | emails and meetings with the customer | on the record timeline as activity, a note on the deal | | Xero, sevDesk, Fakturownia, Comarch Optima | invoice number, payment status, due date | custom properties on the deal, a task once the due date passes | | BaseLinker, Shopify, WooCommerce, PrestaShop | orders, order value and purchase frequency | company and deal, a property holding total orders | | Google Sheets | the spreadsheet that quietly acts as a second CRM | a one-off import into contacts and companies, after which the sheet drops out of the process | | BigQuery and SQL databases | deal history for cohort analysis and forecasting | the other direction: an export out of HubSpot into the warehouse | | Slack and Microsoft Teams | a notification about a new deal and about a stage change | a webhook out of HubSpot to the orchestrator, the result comes back as a note | The rows are a starting point. In most companies the first phase covers two or three systems, and the order comes out of the workshop. The endpoints, authentication and rate limits behind all of this are covered on our API integration page. How we work ## Five steps from three open tabs to one record Each step ends with something you can judge before you decide on the next one. 1. ### Workshop We break the process into stages and ask the same question at each one: where does this information come from, who retypes it today and what is it needed for. We check which systems you already run, including the spreadsheet that quietly acts as a second CRM and the email thread where the real agreements live. 2. ### HubSpot account review We read properties, deal stages, workflows and permissions through the API and count the facts: what is filled in, what sits empty, how many duplicates there are. We check the tier as well, because it decides what can be done inside HubSpot at all. You get the report before anything changes on production. 3. ### System of record and the logic split We settle which HubSpot property is the system of record for which piece of information and which system may overwrite it. We split the rules: what stays in HubSpot workflows, what goes to n8n or Make. We create the missing custom properties with internal names that get set once. 4. ### Pilot on a test account The integration runs first on a free test account from a developer account, and on a sandbox for Enterprise. We push real enquiries and invoices from the last few weeks through it, including the ugly cases: a company with no VAT number, a duplicate, an order with no contact attached. 5. ### Production and measurement at 30 and 90 days We switch over with error monitoring in place and train the person who will maintain it. After 30 days we look at property completeness and the number of events that failed. After 90 days we look at whether anyone is still retyping anything by hand. Before and after ## How the day changes for the person working in HubSpot ### Before - Opens the invoicing system to check whether the customer paid for the last order - Types what was agreed at the meeting into an email, because HubSpot would take longer - Searches HubSpot for the company under three names, unsure which one a colleague used - Asks for a report, because no HubSpot view shows what the board is asking about ### After - Sees the payment status and invoice number as properties on the deal - Emails and meetings attach themselves to the record with no work from them - The company is in HubSpot once, because a rule catches duplicates by VAT number and domain - Asks the AI agent in a plain sentence and gets an answer from HubSpot in 5 to 10 seconds The first automation runs 14 days after the workshop. We judge property completeness at 30 days, and whether anyone still retypes data by hand at 90. For the person signing this off ## What the person paying for HubSpot gets out of it The HubSpot licence is a fixed cost, and until now how well it was used was a matter of faith. Once it is connected you can see it in numbers: how many records are created without a person, how many properties are filled in, how many events went through and how many failed. The renewal conversation stops being a conversation about how the team feels. The second thing takes the tier decision off your shoulders. Instead of buying high just in case, you know which features genuinely need Professional or Enterprise and what an external orchestrator does for less. We start with a [process workshop](https://justautomate.ai/en/services/process-workshop/), so your first decision rests on a document rather than a promise. - HubSpot licence usage visible as a number, not as an opinion - The tier decision based on a list of features you actually need - Data cleaned before the import, so the migration does not carry duplicates across - The integration run on a test account first, so production is not the testing ground What it costs ## The workshop has a fixed price, the integration is quoted after it The process workshop costs **EUR 3,500 net per week** and runs from one to seven weeks depending on scope. For a single CRM one week is usually enough, because the scope is narrow: what enters HubSpot, where from, and where inside it that gets written. The integration is quoted after the workshop, once we know how many systems are in play and what state the data is in. You pay HubSpot for the licence directly, and the same goes for running workflows in Make or n8n, or you pay nothing at all when the workflow sits on your own infrastructure. Where an AI agent is in scope, the model provider charges EUR 0.005 to 0.07 per query. No commission on top from us. On Marketing Hub it is worth counting your marketing contacts before you change tier, because that count drives the bill. - ### Process workshop EUR 3,500 net per week, usually one week for a single CRM A self-contained piece of work. It ends with a map of systems of record and a list of connections in order, which you can execute without us. - HubSpot account review: properties, stages, workflows, tier and limits - Map of systems of record: what lives in HubSpot and what lives next to it - The logic split between HubSpot workflows and an external orchestrator - Duplicate report and proposed merge rules to run before the import Start with the workshop - Most popular ### Workshop and HubSpot integration Quoted after the workshop scope follows from the number of systems and the state of the database The option most companies choose. A connected HubSpot 2 to 6 weeks after the workshop, tested on a test account before production. - Everything in the workshop - Integrations through the API and webhooks: forms, inbox, invoices, orders, spreadsheets - Custom properties and objects created against the agreed systems of record - Pilot on a test account, switchover with error monitoring - Training for the person who will change rules without us Talk about a rollout - ### HubSpot and an AI agent Quoted after the workshop for companies where the whole team asks about CRM data, not only sales Everything in the integration plus BOND, which answers questions about customers in a plain sentence, from HubSpot data. - Everything in the HubSpot integration - AI agent wired into HubSpot: customer record, stages, stalled deals, lead sources - Permissions scoped separately for reading and for writing - Access for people outside sales, an answer in 5 to 10 seconds Ask about the agent The workshop ends with a document that stands on its own without us: a map of systems of record, a list of connections in order and a duplicate report. If the account review shows the workflows you already have are enough, we say so, and the engagement ends at the workshop instead of at an integration you do not need. ## Frequently asked questions What exactly do you connect to HubSpot? Six things most often: forms and enquiry channels, the inbox and calendar from Google Workspace or Microsoft 365, the invoicing system (Xero, sevDesk, Fakturownia, Comarch Optima), orders from BaseLinker, Shopify, WooCommerce or PrestaShop, spreadsheets in Google Sheets and the warehouse in BigQuery. The order comes out of the workshop, because a different connection removes the most manual work in every company. Does a HubSpot integration require Professional or Enterprise? Reading and writing through the API works on every tier, so the integration itself rarely forces an upgrade. The tier decides what can be done inside HubSpot: custom objects start at Enterprise and workflows at Professional. On a free account and on Starter the logic lives in n8n or Make while HubSpot stays the place the result is written, and that often costs less than moving up a tier. When is a HubSpot workflow enough, and when do you need n8n or Make? Rule of thumb: if the rule concerns HubSpot alone it stays in a HubSpot workflow, because that is where you can change it yourselves. A task after a stage change, a reminder about a deal with no movement, an email sequence, all workflows. If the rule has to query a system next door, for example an invoice status or stock level, it goes to the orchestrator, where you can see which step it failed on and rerun it. Where in HubSpot does information from another system land? In a property on one of the objects: contact, company, deal or ticket. Invoice number and status go as custom properties on the deal, total orders on the company, source and utm parameters on the contact. Anything that is not used for filtering or for a rule stays as activity on the timeline, because a separate property for every piece of information only clutters the record. What does a migration into HubSpot from a spreadsheet or another CRM look like? Cleanup on a copy first, then the import. We catch duplicates by VAT number, email domain and fuzzy name match, turn text fields into closed value lists and settle the property internal names, which cannot be changed once the field exists. You approve the merge rules and we show you the result before the switchover, so nobody discovers afterwards that two companies became one. How long does a HubSpot integration take? One week of workshop and 2 to 6 weeks of work, depending on the number of systems and the state of the database. The first automation usually runs 14 days after the workshop, so the team sees an effect before the project ends. The longest item is often the data cleanup rather than the integration, because the ambiguous cases have to be reviewed record by record. Does customer data leave HubSpot? Only the fields a decision needs, and we agree that list at the workshop field by field. An n8n workflow can run on your own infrastructure, in which case the data never leaves your servers. We set the retention period for contacts that never entered the sales process together with you, because Regulation 2016/679 requires a defined period rather than an open-ended one. Can the AI agent write data into HubSpot? It can, but we scope permissions separately for reading and for writing, and we usually start with reading only. Writing is switched on after the pilot, on a narrow list of operations: a note, a task, a change to one property. Every agent operation is logged, so you can check who changed what and roll it back. There is more on this in our guide on integrating a CRM with AI. ## Let us look at what you retype into HubSpot by hand today The free consultation takes 30 minutes. You tell us which HubSpot tier you are on, how many people work in it and what you retype into it from other systems: invoices, orders, emails or a spreadsheet. We show you which connection removes the most manual work and what has to be cleaned up before it. You do not have to share access to the account at this stage. We run at most two rollouts at a time, so that someone is actually sitting on each of them. [Book a free consultation](https://justautomate.ai/en/contact/) **PS.** If somebody at your company opened the invoicing system this week to check whether a customer had paid, and then went back to HubSpot with the answer, that is exactly this problem. A connected HubSpot shows the payment status as a property on the deal, on the record that person already sits in. We start with the workshop, because with no agreed system of record an integration only spreads the mess faster. ## Related - [API integration](https://justautomate.ai/en/services/api-integration/) - [BOND, business AI agent](https://justautomate.ai/en/services/bond-business-ai-agent/) - [n8n automation](https://justautomate.ai/en/services/n8n-automation/) - [CRM automation](https://justautomate.ai/en/services/crm-automation/) - [Pipedrive integration](https://justautomate.ai/en/integrations/pipedrive/) - [How to integrate a CRM with AI](https://justautomate.ai/en/guides/how-to-integrate-crm-with-ai/) --- **JustAutomate** · contact: contact@justautomate.ai · form: https://justautomate.ai/en/contact/