With Defontana's REST API and an app connected to HubSpot: clients and won deals travel from HubSpot to Defontana, and invoices come back to HubSpot with their number and their status with the SII, Chile's tax authority. Defontana always issues the electronic invoice; HubSpot does not create tax documents in Chile. Before coding, define which system owns each piece of data and how you will know, the same day, if the sync stopped.
| Data | Direction | In Defontana |
|---|---|---|
| Client: legal name, tax ID and line of business | HubSpot → Defontana | Client record |
| Products and prices | Defontana → HubSpot | Products and price lists |
| Won deal | HubSpot → Defontana | Order or sales document |
| Invoice: number, status and amount | Defontana → HubSpot | Electronic document issued |
| Credit notes | Defontana → HubSpot | Adjustment to the invoiced amount |
Defontana publishes a REST API with documentation for Chile and a test environment separate from production. It authenticates with the client and company IDs Defontana assigns, plus a user and password, and returns a token. Every new token invalidates the same user's earlier tokens, so all the integration's processes must share one.
It covers what a HubSpot integration needs: clients with tax ID and line of business, products, price lists and stock, quotes, orders and sales documents, including credit and debit notes.
Usually HubSpot owns the sales stage and Defontana the accounting one. The client is born in HubSpot and, when the deal is won, it is looked up by tax ID in Defontana and created if it does not exist. Products and prices travel the other way, from Defontana, so HubSpot quotes use the same codes as the invoice.
The won deal triggers the order or the sale in Defontana with data already validated. On the way back, the invoice updates the deal and the company in HubSpot with the number, date, amount and SII status. Write these rules down before coding: that is what prevents duplicates.
Defontana issues it: for electronic documents, the API assigns the invoice number automatically from the company's authorized number ranges and lets you query the document's status with the SII. HubSpot has its own invoices, but they are not electronic tax documents; it only shows what the ERP issued.
Typical errors are data errors: a mistyped tax ID, an empty line of business, an incomplete tax address, products without a code in Defontana or different payment terms. Validate those fields in HubSpot before the deal is won and test first in the test environment, with real documents from your operation in Chile.
Since Defontana does not notify through webhooks, the integration polls periodically and leaves a trail. In HubSpot, the Record Source property shows which records the integration created, and the app keeps a log of its calls. A daily report by source shows whether invoices keep arriving.
Define a silence alert: if no invoice arrives on a business day, someone gets a notice that same morning. And leave an owner with access to the code, the Defontana credentials and the documentation. In companies across Chile and Latin America, an invoice that never reaches the CRM is usually discovered when collections calls the wrong salesperson.
Six steps, from the data agreement to the alert.
Ask Defontana for the API credentials and access to the sales modules you will use, and check that you have the test environment.
Client, product, price, deal, invoice and credit note: a table with the owner of each piece of data and when it travels.
On the company: tax ID, legal name, line of business and tax address. On the deal: payment terms, invoice number, SII status and invoiced amount. Require them in the stage before Closed won.
HubSpot stops allowing new legacy private apps on October 26, 2026 in existing accounts; the alternative is Service Keys or a projects-based private app.
In Defontana's test environment, with clients, products and terms from your operation: a won deal, an invoice and a credit note. Check every field in both systems.
An alert if no invoices arrive on a business day, a named owner, credentials and code in your company's name, and a document of what syncs, what does not and why.
Two processes with the same Defontana user invalidating each other's token.
Trying to issue the invoice from HubSpot instead of leaving it in Defontana.
Products with different codes in HubSpot and Defontana, which force manual fixes.
An integration without an alert: invoices stop arriving and nobody notices.
30 minutes with Roberto. No demo and no access to your CRM.
We integrated HubSpot with Defontana for a trade-show and events company: clients, quotes and electronic invoicing from the won deal. Before committing, we classify each point as confirmed, conditional or unsupported based on your Defontana plan, and we hand over code, credentials and manual in your name, with the silence alert active.
Clients, quotes and invoices in sync, with Chilean tax authority safeguards.
See the integrationERP, invoicing, WhatsApp and APIs, at a fixed price and with code in your name.
See IntegrationsThe alert is reviewed weekly in Managed HubSpot and daily in Dedicated HubSpot.
See operations plansThe guarantees that apply
An automatic alert tells you if an integration or form stops bringing in data. You hear it from us first.
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
We put them in writing because they are what we control.
You need to be a Defontana customer with access to the modules the integration uses, such as sales or inventory. That access is arranged with Defontana. Confirm what your plan includes before designing the integration.
HubSpot has its own invoices, but they are not SII electronic tax documents. Defontana issues the invoice with its numbering; HubSpot receives the number, status and amount so sales and collections can see them.
Not through webhooks: its API does not document notifications for ERP events. The integration queries documents periodically and updates HubSpot, which is why an alert for days when nothing arrives is worth having.
The API documents quotes and orders, and an order can reference the quote. If you quote in HubSpot, the usual approach is to create the order in Defontana when the deal is won. Confirm what your plan offers.
3 to 8 weeks depending on the objects synchronized, API access and data quality.
If the code, credentials and documentation are in your name, nothing: another team can maintain it. If they live on the provider's servers, ask for them before announcing the change.
Designs the CRM architecture, integrations and operation of each account. He writes these guides from what he sees every week in HubSpot portals of B2B companies across Chile and Latin America.
Meet the teamWe review one concrete problem, its impact and your starting point. No demo and no access to your CRM.
