Industry CRM
Beyond general-purpose CRMs (HubSpot), betool connects to industry CRMs. The same principle everywhere: your credentials (BYO), access scoped to your organization, exactly-once writes performed by nodes.
beTool Application
Connector for the beTool Application CRM: processes, records, tables and companies.
| Node | Effect |
|---|---|
betool_application_read | Reads a record, a table, a table's structure, or the organization's companies |
betool_application_create_record | Creates a record, exactly-once, then reads it back |
betool_application_update_record | Modifies an existing record, reading it before and after |
Agent tools (read): betool_application.list_processes, betool_application.process_tags (editable fields and their codes), betool_application.datatable, betool_application.datatable_schema, betool_application.get_record, betool_application.list_companies, betool_application.get_company. A single tool writes: betool_application.company_resolve, which looks up a company and only creates it if it does not exist.
Writing records is not entrusted to agents: it goes through the nodes, placed by a designer.
Connection: one API token per organization. A circuit breaker protects your account when the CRM returns a series of errors.
Qhare (Beta)
Beta. The Qhare connector has not yet been proven on a real customer account in production.
Connector for the Qhare CRM (lead management, notably in energy renovation).
| Node | Effect |
|---|---|
qhare_lead_read | Filtered search, details or count of leads |
qhare_lead_write | Creates or updates a lead |
qhare_appointment_write | Creates or updates an appointment in the schedule |
Both write nodes are exactly-once, and an uncertain result is never replayed.
Agent tools (read-only): qhare.search_leads, qhare.get_lead. No tool writes to Qhare. Third-party passwords stored in a record are never returned to the agent.
Connection: your Qhare API key (BYO).