hivein for Dolibarr
Follow the proposal, order and invoice chain in Dolibarr without clicking through every third party.
hivein will call Dolibarr's REST API with a DOLAPIKEY token taken from a dedicated user record, which means only the endpoints belonging to your enabled modules are reachable.
- Follow the quote-to-cash chain
- Read the third-party file
- Check products and stock per warehouse
- Cover the buying side too
- Filter on the server, not in memory
What the Dolibarr connector will do.
Follow the quote-to-cash chain
Proposals, customer orders and invoices each have their own endpoint and link back to the document they came from. A question can start at a signed proposal and finish at whether the invoice was ever paid.
Read the third-party file
A thirdparty in Dolibarr can be a prospect, a customer, a supplier or several at once, with contacts and categories hanging off it. That record is the anchor for most questions about who owes what.
Check products and stock per warehouse
Product records carry reference, price and stock, and asking for a product with its stock data included breaks the quantity down by warehouse, with stock movements behind each change.
Cover the buying side too
Supplier orders and supplier invoices sit on their own endpoints, so purchasing and payables questions are answered over the same connection as sales.
Filter on the server, not in memory
Dolibarr's sqlfilters syntax together with sortfield, limit and page keeps a query narrow at the API. That matters on an install that has been collecting invoices for years.
It will read your Dolibarr data model, not a generic one.
The schema is read first, so a question that spans two of these is one question, not two lookups.
“Which customer invoices are unpaid and how many days late are they?”
“Which proposals were signed last month but never turned into an order?”
“How much of this product reference is left in each warehouse?”
“Which supplier invoices fall due in the next two weeks?”
Dolibarr questions.
What has to be switched on in Dolibarr?
The REST API module has to be enabled in module setup, and the connecting user needs an API key on their user record. hivein will send that key as the DOLAPIKEY header on every call.
We only run a few modules, does that matter?
Dolibarr exposes endpoints only for the modules you have enabled, so an install without the ticket module simply has no ticket data to ask about. The connector works with whatever is switched on.
Do the user's permissions still apply?
Yes, the API key belongs to a Dolibarr user and every call is checked against that user's permissions. Grant the connection user read rights on the modules you want to ask about and nothing more.
More templates like this one.
Salesforce
Closed sourceAsk your org questions and get answers from SOQL, SOSL and the standard objects, no report builder needed.
29 actionsOpen template → — Salesforce
Odoo
Open sourceAsk across Odoo's models — sales orders, invoices, stock moves and leads — in plain language.
TemplateOpen template → — Odoo
ERPNext
Open sourceQuery ERPNext DocTypes, from Sales Order to Stock Entry, without building a report for each question.
In developmentSee the plan → — ERPNextSuSuiteCRM
Open sourceAsk about accounts, opportunities and cases in SuiteCRM, and follow the links between them.
In developmentSee the plan → — SuiteCRMWant Dolibarr next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.