hivein for SuiteCRM
Ask about accounts, opportunities and cases in SuiteCRM, and follow the links between them.
hivein will connect through the SuiteCRM V8 REST API, taking an OAuth 2.0 token from the access_token endpoint using a client created on the OAuth2 clients screen in the admin panel.
- Query modules with JSON:API parameters
- Follow the relationships
- Report on the pipeline
- Keep track of support cases
- Pick up Studio fields
What the SuiteCRM connector will do.
Query modules with JSON:API parameters
The V8 API takes filter, sort, page and sparse fieldsets, so Accounts, Contacts, Leads, Opportunities and Cases are narrowed before anything is read. Only the fields a question needs come back.
Follow the relationships
Relationship routes return the contacts on an account, the opportunities on a contact or the cases raised against a customer. An answer can walk that graph instead of stopping at one record.
Report on the pipeline
Opportunities carry sales_stage, amount, date_closed and assigned_user_id, which covers stage-by-stage and close-date questions without building an AOR report first.
Keep track of support cases
Cases carry state, status and priority alongside their account and contact links, so backlog, ownership and ageing questions come from the same connection as the sales data.
Pick up Studio fields
The V8 metadata routes list the fields on each module, including the _c fields added in Studio, so the bespoke fields your team relies on are readable next to the stock ones.
It will read your SuiteCRM 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 opportunities are due to close this month and what stage are they in?”
“Show the open high-priority cases for this account and who owns each one.”
“Who are the contacts at our largest accounts by open opportunity value?”
“Which leads from the last campaign have had no call or meeting logged?”
SuiteCRM questions.
Is this the old V4.1 API?
No, hivein targets the V8 REST API, the JSON:API-style interface that uses OAuth 2.0 tokens. The legacy V4.1 endpoint is left alone.
What has to be set up on our SuiteCRM first?
The V8 API needs its OAuth2 key pair generated on the server and a client created in the admin panel. hivein will then use those credentials, and nothing else about the install has to change.
Does it respect our roles and security groups?
When the token is issued for a specific SuiteCRM user, that user's roles and security-group rules decide which records come back. Give the connection user the access you would give a person in the same job.
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
Dolibarr
Open sourceFollow the proposal, order and invoice chain in Dolibarr without clicking through every third party.
In developmentSee the plan → — Dolibarr
ERPNext
Open sourceQuery ERPNext DocTypes, from Sales Order to Stock Entry, without building a report for each question.
In developmentSee the plan → — ERPNextWant SuiteCRM next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.