--- title: Fireberry API Integration on Truto slug: fireberry category: CRM canonical: "https://truto.one/integrations/detail/fireberry/" --- # Fireberry API Integration on Truto **Category:** CRM **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Fireberry account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Fireberry.** The Proxy API is a 1-to-1 mapping of the Fireberry API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync Fireberry users into your SaaS for ownership mapping** — If your product assigns tasks, tickets, or leads to specific reps, you need to know who's who inside your customer's CRM. Pulling the Fireberry user directory via Truto's Unified User Directory API lets you map ownership accurately without asking end users to manually configure assignments. - **Power AI support tools with CRM user context** — An AI customer service platform can query Fireberry's user directory to identify the correct service agent for ticket routing or escalation. Knowing agent roles and team structure ensures automated workflows assign work to the right person. - **Enable sales dialers to route calls to the right rep** — Telephony SaaS products need to look up which Fireberry user owns a given account or lead so inbound calls can be routed correctly. Syncing the user directory via Truto gives your dialer the rep-level context it needs without custom API work per customer. - **Build role-aware dashboards for RevOps tools** — Revenue operations platforms can pull Fireberry's internal user list to build team-aware reporting views — grouping pipeline metrics by rep, manager, or department — so your customers see their CRM org structure reflected natively in your product. ## What you can build - **Automated rep directory sync** — Pull the full list of Fireberry users — names, emails, and roles — into your product on a recurring schedule so assignment dropdowns and ownership fields stay current. - **User-to-owner mapping for ticket or lead routing** — Match incoming records to the correct Fireberry user so your product can auto-assign tickets, tasks, or leads to the right rep without manual configuration. - **Team structure import for org-aware reporting** — Import Fireberry's user hierarchy to power team-level roll-ups, manager views, and permission scoping inside your analytics or enablement tool. - **Agent availability lookup for support platforms** — Query Fireberry's user directory to determine which service agents exist and can be assigned new cases, enabling smarter workload distribution from your support SaaS. - **CRM user onboarding wizard** — During your product's setup flow, let customers connect Fireberry and instantly see their user list populated — reducing time-to-value and eliminating CSV imports. ## FAQs ### What Unified APIs does Truto support for Fireberry today? Truto currently supports the Unified User Directory API (Users) for Fireberry. This lets you list and read Fireberry user records through a standardized schema. Additional unified APIs and tools can be built on request. ### Are there pre-built tools for Fireberry objects like Leads, Contacts, or Deals? Not yet. Fireberry tools for standard CRM objects are built on request. If your use case requires reading or writing Leads, Contacts, Accounts, Deals, or Tickets, reach out and Truto can scope and build the integration for you. ### How does authentication work for Fireberry integrations through Truto? Truto handles the authentication flow with Fireberry's REST API on behalf of your end users. Your customers connect their Fireberry accounts through Truto's embedded linking flow, and Truto manages token storage and refresh so you don't have to. ### Does Fireberry support custom fields and objects, and can Truto handle that? Yes, Fireberry is heavily customizable — customers frequently create custom objects, fields, and picklists. Fireberry's API supports dynamic schema discovery. When Truto builds additional tools for Fireberry, custom field support can be scoped into the integration. ### Can I get real-time updates from Fireberry through Truto? Fireberry supports webhooks for events like Lead Created or Deal Won. Webhook-based syncing can be part of a custom integration built by Truto on request. For the Unified User Directory API, data is fetched on demand via API calls. ### How quickly can Truto build new Fireberry tools if I need more than the User Directory API? Truto builds integrations on request and scopes them to your specific use case. Turnaround depends on complexity, but common CRM object CRUD and activity logging patterns are well-understood and typically fast to ship.