Firmao
BUSINESS · CRM & SUPPORT
Customers, contacts, projects, tasks, offers, and transactions in the CRM they connected.
Connect Firmao with Fabriq Developer
Your user pastes their Firmao credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Firmao in practice
Firmao’s API is switched off until someone enables it in the company settings tab, and the specification is published only as a PDF download — there is no HTML reference, no OpenAPI document and no endpoint list a tool can read, so the integration surface has to be transcribed by hand.
Who has to approve
The API is "activated with a single click in the company settings tab", so it is a company-level switch rather than a per-user consent: until whoever administers the Firmao account turns it on, no credential works at all.
Worth knowing
- The only published specification is a PDF on the API page, and Firmao points integrators at contact@firmao.io for anything it does not cover. Nothing about rate limits or authentication appears on a public page.
- The old firmao.net domain 301-redirects to firmao.io, so bookmarked documentation links and any hardcoded host from an older integration need rewriting.
Checked against Firmao API (2026-09-29), Firmao API (English) (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Firmao behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.