--- title: HappyFox API Integration on Truto slug: happyfox category: Helpdesk canonical: "https://truto.one/integrations/detail/happyfox/" --- # HappyFox API Integration on Truto **Category:** Helpdesk **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Groups** — Groups are a collection of users in the source application. In some applications, they might also be called Teams. - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. ### Unified Ticketing API - **Contacts** — Contact represent the external people you are in contact with. These could be customers, leads, etc. Contacts can be associated with an Account if the underlying product supports it. - **Fields** — Fields represent the attributes defined for various entities in the underlying product. Depending on the underlying product, custom attributes can be defined by a User on various entities like Ticket, Contact, etc. is_user_defined attribute within Field can be used to differentiate between custom and system defined Fields. - **Ticket Status** — Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status. - **Users** — Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc. ## MCP-ready AI tools Truto exposes 1 tools for HappyFox that AI agents can call directly. - **create_a_happyfox_user_reply** — Add a reply by a contact (called user on HappyFox) on a ticket. Requires the ticket_id. ## How it works 1. **Link your customer's HappyFox 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 HappyFox.** The Proxy API is a 1-to-1 mapping of the HappyFox 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 - **AI support agents that escalate seamlessly into HappyFox** — AI chatbot platforms can create HappyFox tickets on human handoff and use create_a_happyfox_user_reply to append follow-up messages to the same ticket thread, keeping agents in sync without duplicate tickets. - **CRM platforms surfacing support context for account health** — Revenue and CRM tools can pull open HappyFox tickets tied to specific contacts, giving account executives a complete view of customer support interactions alongside deal and renewal data. - **HR and identity platforms automating IT provisioning tickets** — Employee onboarding SaaS can create HappyFox contacts for new hires and generate equipment provisioning tickets routed to the correct IT group, with custom fields like laptop type and start date pre-filled. - **Workflow automation tools syncing ticket status across systems** — iPaaS and workflow platforms can read and update HappyFox ticket statuses in response to external events — like marking a support ticket resolved when a linked engineering task is closed. - **Internal service desk consolidation for multi-tool environments** — Operations platforms managing multiple helpdesks can normalize HappyFox users, groups, roles, and tickets into a single directory, enabling cross-tool reporting and routing logic. ## What you can build - **Two-way contact and user directory sync** — Keep HappyFox contacts, agents, groups, and roles in sync with your platform's user directory using the Unified User Directory API. - **Automated ticket creation with custom field mapping** — Generate HappyFox tickets from external events with dynamic custom fields like device type, account tier, or priority mapped via the Unified Ticketing API. - **Threaded customer reply injection** — Use create_a_happyfox_user_reply to append messages to existing tickets on behalf of the end customer, maintaining a single continuous conversation thread. - **Real-time ticket status dashboard** — Pull ticket statuses from HappyFox and display them inside your product so users can monitor open issues, escalations, and resolutions without switching tools. - **Group-based ticket routing engine** — Read HappyFox groups and roles to intelligently route new tickets to the right support team — like sending hardware requests to IT Operations and billing issues to Finance. - **Agent directory mapping for cross-platform mentions** — Sync HappyFox staff users into your platform's identity graph so ticket assignments and @mentions resolve correctly across systems. ## FAQs ### What Unified APIs does Truto support for HappyFox? Truto supports the Unified Ticketing API (Contacts, Fields, Ticket Status, Users) and the Unified User Directory API (Groups, Roles, Users) for HappyFox. ### Can I append replies to existing HappyFox tickets programmatically? Yes. The create_a_happyfox_user_reply tool lets you post a reply to an existing ticket as the contact, which is useful for AI chatbot handoffs or appending context from external systems without creating duplicate tickets. ### Does Truto handle HappyFox authentication and pagination? Yes. Truto manages OAuth or API key-based authentication flows and handles pagination automatically, so you don't need to deal with HappyFox's API-specific auth or cursor logic. ### Can I read and map HappyFox custom fields through Truto? Yes. The Unified Ticketing API exposes a Fields resource that lets you dynamically discover and map HappyFox custom fields like Device Type or Account Tier into your application. ### How do Groups and Roles work in the HappyFox integration? Through the Unified User Directory API, you can read HappyFox staff groups (e.g., L2 Support, IT Provisioning) and roles. This is useful for building routing logic that assigns tickets to the correct team automatically. ### Who connects their HappyFox account in this integration? Your end users — typically support managers or IT admins — connect their own HappyFox accounts through Truto's embedded auth flow. You build the integration once; each customer authorizes their own instance.