Source ERP · 43 of 89
CRMPro → HubSpot — JobBOSS: what the shipped templates set up
This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-crmpro-hubspot/erps/jobboss". It extends the dlake-crmpro-hubspot skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/jobboss-hubspot/.
CRMPro → HubSpot — JobBOSS: what the shipped templates set up
This is a capability summary, not an operating guide. To receive the operational skill you must be a
registered, whitelisted Commercient customer. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-hubspot/erps/jobboss (or list_skills) against the Commercient
admin plane. Existing customers who need access or help: contact support@commercient.com. New
customers: contact sales@commercient.com to become a customer and be whitelisted.
dlake-crmpro is the parent skill and the authority for everything general: the CRMPro tools, process configuration and field list, the sync history, how source data is selected, and what a run that finds nothing does. Read it first; this page does not repeat it. dlake-crmpro-hubspot is the destination skill this page is a child of, and the authority for the HubSpot conventions that hold across every ERP: read it first, then come back here for what this source’s own templates set. This page grows as the catalogue does.
1. What the templates deliver
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| create order | The templates push deal to HubSpot | deal | sales order headers |
| create order detail | The templates push line item to HubSpot | line item | sales order details |
| create invoice | The templates push deal to HubSpot | deal | invoice headers |
| create invoice detail | The templates push line item to HubSpot | line item | invoice details |
| create opportunity | The templates push deal to HubSpot | deal | requests for quote |
| create opportunity detail | The templates push line item to HubSpot | line item | quotes, quote quantities |
| create customer | ERP customers, addresses data becomes company in HubSpot | company | customers, addresses |
| create item | The templates push products to HubSpot | products | materials |
| create contact | ERP contacts, addresses data becomes contact in HubSpot | contact | contacts, addresses |
2. The process rows the templates create
Each template’s setup writes one process configuration row. These are the values it sets; a column the inserts never set is not listed.
| Display name | Destination object | Run sequence |
|---|---|---|
| create customer | company | 5 |
| create contact | contact | 5 |
| create item | products | 10 |
| create order | deal | 11 |
| create order detail | line item | 12 |
| create invoice | deal | 13 |
| create invoice detail | line item | 14 |
| create opportunity | deal | 15 |
| create opportunity detail | line item | 16 |
Every one of these inserts the active setting as 0, so an imported process is inactive until an operator activates it.
3. The views
“Change detection” names which of the three kinds dlake-crmpro defines the view’s own filter makes it; where a view’s shape is not one of those three the column is left empty and the view’s own filter is the authority.
| View | Change detection | Source tables |
|---|---|---|
| new customer feed | insert only | customers, addresses |
| new contact feed | insert only | contacts, addresses |
| new item feed | insert only | materials |
| new order deal feed | insert only | sales order headers |
| new order line item feed | insert only | sales order details |
| new invoice deal feed | insert only | invoice headers |
| new invoice line item feed | insert only | invoice details |
| new opportunity deal feed | insert only | requests for quote |
| new opportunity line item feed | insert only | quotes, quote quantities |
4. Order of work
The templates set run sequence to 5, 10, 11, 12, 13, 14, 15, 16. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 5 — create customer, create contact
- 10 — create item
- 11 — create order
- 12 — create order detail
- 13 — create invoice
- 14 — create invoice detail
- 15 — create opportunity
- 16 — create opportunity detail
Several of these rows share a run sequence value: each template group carries its own numbering, so give the imported processes an order across the whole set rather than taking the template values as one.
These views read another process’s sync output, which is what makes the order a dependency order: the row appears in the view only once the process that writes that sync output has run, so a parent flows on one run and its children on the next.
- new order deal feed reads new customer sync output, Order; no template in this set writes Order
- new order line item feed reads new item sync output, Order; no template in this set writes Order
- new invoice deal feed reads new customer sync output, invoice record sync output (generic name); no template in this set writes invoice record sync output (generic name)
- new invoice line item feed reads new item sync output, invoice record sync output (generic name); no template in this set writes invoice record sync output (generic name)
- new opportunity deal feed reads new customer sync output, opportunity sync output (generic name); no template in this set writes opportunity sync output (generic name)
- new opportunity line item feed reads new item sync output, opportunity sync output (generic name); no template in this set writes opportunity sync output (generic name)
- new contact feed reads new customer sync output
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → HubSpot pairs |
|---|---|---|---|
| create customer | company | 9 | Customer → Commercient AR customer code, Name → name, Address line 1 → address, Address line 2 → address line 2 property, City → city property |
| create contact | contact | 13 | Contact key → external key property, Contact name field → first name property, Contact name field → last name property, Email address → email, Phone → phone |
| create item | products | 5 | Material → stock keeping unit property, Description → name, Extended description → description, Standard cost → cost of goods sold property, Selling price → price |
| create order | deal | 7 | Total price → amount, Trade date → close date property, Order date → create date property, Sales order (single record), Customer → deal name property, Customer → company association |
| create order detail | line item | 6 | Unit price → price, Order quantity → quantity, Material → product lookup property, Material → name, Sales order (single record) → deal association |
| create invoice | deal | 9 | Open invoice amount → amount, Due date → close date property, Document date → create date property, Document, Customer → deal name property, Customer → company association |
| create invoice detail | line item | 6 | Unit price → price, Order quantity → quantity, Part number → product lookup property, Part number → name, Document → deal association |
| create opportunity | deal | 9 | Trade date → close date property, Quote date → create date property, Request for quote, Customer → deal name property, Customer → company association, Request for quote → record key |
| create opportunity detail | line item | 5 | Part number → product lookup property, Quote → deal association, Quoted unit price → price, Quote quantity → quantity, Part number → name |
6. Community templates
The catalogue carries 56 community templates for this pair. A community template is authored in a tenant rather than shipped with the product, and it imports the same way as any other. Its own names, notes, field mapping and SQL are tenant content, so what this section states is what the set amounts to: how many templates there are, what they default to doing, which destination objects they write and which groups they fall in. They are not part of the shipped set described above.
- Templates: 56
- Default operations: insert on 56, update on 56, delete on 56
- Marked as circular sync: 0
- Licence groups they span: 6
- Destination objects: deal, line item, company, contact, products, Commercient Data Matching object, Commercient Contacts Data Matching object, Commercient HubSpot New Customer object, Commercient Remove All Details object, Commercient Sage 100 Account Matching object, Commercient Syspro 7 Account Matching object, product and 3 custom objects
- Object display names: upsert order, upsert customer, create customer, upsert contact, upsert order detail, upsert quote, create contact, create order detail, upsert invoice, upsert invoice detail, upsert item, create item, 16 more and 8 further templates
- Template groups: Account, Invoice, Product
7. Verifying
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-hubspot/erps/jobboss.
8. Where this sits
dlake-crmpro is the general operating surface — the CRMPro tools, the setup and transaction tables, field mapping, and the source view contract that applies to every destination. This page adds what the shipped JobBOSS → HubSpot templates set up. dlake-crmpro-hubspot is the destination skill this page sits under: its own text is the authority for the HubSpot conventions that hold across every ERP, and its ERP table lists this page alongside every sibling ERP page for this destination. For the extract leg that fills the source data, see dlake-normalsync; for the on-premises agent that runs it, dlake-syncagent; for the writeback leg, dlake-txdownloaderpro; for standing an integration up, dlake-integration-setup.
How to get started
- Already a customer: the operational skill tells you how to connect, choose what to sync and run it.
Fetch it with
dlake admin get_skill dlake-crmpro-hubspot/erps/jobboss, or ask support@commercient.com. - New to Commercient: contact sales@commercient.com. Becoming a customer includes registration and whitelisting, after which the operational skills and tools are available to you.
