How does Hubhus integrate with e-conomic v2?

Modified on Tue, 5 May at 6:50 PM

How does Hubhus integrate with e-conomic?

Hubhus can send data to e-conomic in three different ways. Which one applies to you depends on how your setup is configured. This article explains all three, helps you identify which one you are using, and covers common issues for each.

TL;DR

Method 1 — Automatic JSON injection: Form page writes JSON to df_e_conomic before submit. A Make scenario reads it and creates the e-conomic document. Best for complex, dynamic pricing.

Method 2 — Action listener with placeholders: No custom JS needed. An action listener sends a JSON payload with Hubhus placeholders (e.g. %lead_name%) when a lead is created/updated. Best for simple, field-based invoices.

Method 3 — Manual product line in Billing: Staff manually add product lines in Hubhus Billing. Invoices are sent from e-conomic at month end. Used for time registration and consultant hours.

3 integration methods to know

Automatic JSON injection via df_e_conomic

A JavaScript block on the Hubhus page builds a JSON object (customer, product lines, pricing) and writes it to the Data Field df_e_conomic just before form submit. An external automation (typically Make) listens for new leads with this field populated and calls the e-conomic API. Use this when you need dynamic per-line pricing or complex calculations based on user input.

Action listener with Hubhus placeholders

No custom page code is required. An action or webhook listener sends a JSON payload with Hubhus placeholders (e.g. %lead_name%, %lead_email%) that Hubhus substitutes with real lead values before dispatching the request. Simpler to configure but less flexible for multi-line or computed invoices.

Manual product line in Hubhus Billing

Staff manually add billable product lines against a customer in Hubhus Billing — for example, consultant hours or development time. At month end (last day), all draft invoices are sent from e-conomic. This is an internal time registration process and does not involve any automated form trigger.

Read more⌄

Method 1: JSON structure for df_e_conomic

The df_e_conomic Data Field stores a single JSON object per submission. Minimal required structure:

{ "type": "order",
  "customer": { "name": "...", "email": "...", "address": "...", "zip": "...", "city": "..." },
  "lines": [
    { "product": { "productNumber": "600" }, "quantity": 1, "unitNetPrice": 1250.00, "description": "..." }
  ],
  "notes": { "heading": "Order ref", "textLine1": "Lead ID" }
}

Key rules: quantity must be positive (zero/negative is rejected). productNumber must exist in your e-conomic account. unitNetPrice is net (excl. VAT).

Deletion flow: To delete an existing draft, set "hubhusEconomicAction": "delete" in the JSON. Your Make scenario must check for this key before attempting to create a new order.

Method 2: Example payload with Hubhus placeholders

{ "type": "order",
  "customer": { "name": "%lead_name%", "email": "%lead_email%",
    "telephoneAndFaxNumber": "%lead_phone%", "address": "%lead_street_address%",
    "zip": "%lead_postal_code%", "city": "%lead_city_name%" },
  "lines": [ { "product": { "productNumber": "600" }, "quantity": 1,
    "unitNetPrice": 0, "description": "..." } ],
  "notes": { "heading": "Order — %lead_name%", "textLine1": "Lead ID: %lead_id%" }
}

Use Method 2 when the invoice content is straightforward and expressible with standard lead fields. Use Method 1 when pricing depends on form inputs or requires multiple dynamic lines.

Method 3: Adding a manual product line (step by step)

Go to the billing campaign. If the customer exists as a lead, skip to step 5. Otherwise click New order.
In the modal, click Select existing customer.
Search for the customer by name. If not found, check Billing → Edit e-conomic customer mappings.
Select the customer and click Create order. Wait for the order to appear.
On the customer page, click Add product in the centre panel.
Search for and select the relevant product (e.g. consultant hours).
Edit the description: today's date · requester at customer · brief task description · reference. Click the blue checkmark to save.
Repeat steps 5–7 for each billable item. On the last day of the month, send all draft invoices from e-conomic.

Common issues

Symptom	Likely cause
Nothing created in e-conomic	Make scenario not active, filter on wrong field, or `df_e_conomic` is empty / invalid JSON.
Error: product not found	`productNumber` does not exist in your e-conomic account, or wrong environment (test vs. production).
Error: invalid quantity	`quantity` is 0 or negative, or an empty line was included in `lines`.
Wrong price or VAT amount	`unitNetPrice` must be net. If the page shows VAT-inclusive prices, divide by the VAT factor in JS before writing.
Customer not found (Method 3)	Name differs between Hubhus and e-conomic. Check Billing → Edit e-conomic customer mappings.

When reporting an error: Include the raw JSON from df_e_conomic on the affected lead, the lead ID, timestamp, and the full error message from Make or e-conomic.

Common searches

e-conomic integration • df_e_conomic • send invoice from Hubhus • automatic invoice • Make integration • consultant hours billing • month-end invoicing • product line e-conomic • action listener invoice

How do I integrate with e-conomic? (v1 — webhook setup)
Hubhus integrations overview
How do I create automation rules?
API setup and authentication