HappyFox

Run HappyFox ticketing from AI agent workflows. Agents create tickets from inbound emails, forms, or chat, post staff and user replies, register contacts, and look up categories and staff to route and attribute tickets automatically.

9 actions Basic auth available

HappyFox website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A support request lands from a form, chat widget, or shared inbox that HappyFox does not watch on its own

List Categories resolves the right category ID from the request's topic so routing happens at creation, not after

Create Ticket raises the ticket on the requester's behalf, matching an existing contact by email or registering a new one

Get Ticket pulls the full conversation history and custom fields to assemble context for a response

The agent drafts a staff reply and flags anything involving refunds, outages, or contract terms

A support lead reviews the draft, because a staff reply posts publicly under the team's name

Add Ticket Update posts the approved reply with Reply As set to Staff

The support channel receives the ticket link, category, and time from arrival to first response

What This Integration Enables

A help desk earns its keep by being the single place support work lives, and it loses that status one side channel at a time: the form nobody wired up, the chat transcript nobody filed, the request that came through a personal inbox. FlowRunner agents defend the perimeter. They turn every inbound request into a HappyFox ticket with the right category and a matched contact, assemble conversation history before a human reads it, and draft the reply that a person then approves. - Create tickets automatically from inbound emails, form submissions, and chat messages - Route at creation by resolving categories and staff, instead of triaging after the fact - Draft staff replies from full ticket context, gated by [human-in-the-loop](/concepts/human-in-the-loop) review before posting - Pre-register requesters as contacts so tickets always attach to a real record - Sync ticket and requester data outward to the CRM and reporting sheets

Without FlowRunner

Side-channel requests evaporate Requests that arrive through forms, chat, and personal inboxes never become tickets, so they never get counted or answered on time

Triage eats the morning Someone reads every new ticket, guesses the category, and hunts for the requester's history before real work starts

Replies vary by author First responses range from excellent to improvised depending on who picked up the ticket and how their day was going

With FlowRunner

Every request becomes a ticket Whatever channel a request arrives through, it lands in HappyFox with a category, a matched contact, and a timestamp

Context arrives pre-assembled The full conversation, custom fields, and requester history are gathered before a human ever opens the ticket

Drafted replies, human-approved Agents write the first response from ticket context; a support lead approves it before it reaches the customer

Use Case Scenarios

The form that finally files its own tickets

Support requests arrive through a [Tally](/integrations/tally) form on the website. For each submission, the agent resolves the topic against List Categories, then calls Create Ticket with the requester's name, email, and message. HappyFox matches the contact by email or creates one. A [Slack](/integrations/slack) alert posts the subject and requester to the support channel. Requests that used to sit in a form-results table until Friday now enter the queue in seconds, with a category already set.

Support activity becomes CRM signal

On a schedule, the agent runs List Tickets across the open queue, pulls each requester, and syncs them into [HubSpot](/integrations/hubspot) as contacts with their ticket subject and status attached. Account owners see which of their customers are struggling this week without asking support for a report, and renewal conversations stop being surprised by a support history the CRM never knew about.

First response drafted by the agent, signed by a person

When a customer replies, Get Ticket fetches the complete conversation, updates, custom fields, and history. The agent drafts a response grounded in that thread and posts the draft to the support lead with the ticket context attached. On approval, Add Ticket Update publishes it as a staff reply. Every exchange also logs to [Google Sheets](/integrations/google-sheets), so response times and reopened tickets are measurable instead of anecdotal.

Human-in-Loop Highlight

Add Ticket Update with Reply As set to Staff is a publish button. The message posts to the ticket as your team, visible to the customer, quotable in their next escalation, and permanent in the conversation record. There is no unsend. An AI-drafted reply that misstates a refund policy or promises a fix date is not a bug report, it is a commitment your company just made in writing. So FlowRunner treats the staff reply as the gated step: the agent does the reading, the history assembly, and the drafting, and the support lead does the approving. The customer gets a fast, well-grounded response, and every word of it was signed off by a person who answers for it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

9 actions

Tickets

List Tickets Retrieves a paginated list of support tickets with keyword search across ticket content. Each ticket includes its ID, display ID, subject, status, priority, category, and requester details. Page and Page Size iterate through large result sets.
Get Ticket Retrieves the full details of a single ticket by numeric ID: subject, status, priority, category, requester, assigned staff, custom fields, and the complete conversation history. The context-assembly step before any drafted reply.
Create Ticket Creates a new support ticket on behalf of a contact. Provide the requester's Name and Email (existing contacts match by email; new ones are created), a Subject, and the message Text with HTML supported. Category must be an existing category ID; Priority is an optional account-defined ID or name.
Add Ticket Update Adds a reply or update to an existing ticket. Reply As "Staff" posts a staff response, public reply or private staff-pending note; "User" posts as the requesting contact. The operation this page's human gate exists for.

Contacts

List Contacts Retrieves a paginated list of end-user contacts with ID, name, email, and phone details.
Get Contact Retrieves the full details of a single contact by numeric ID, including custom contact fields configured in your account.
Create Contact Creates a new contact with a name and email address. Used to pre-register requesters before raising tickets on their behalf; an existing email may return the existing record.

Staff

List Staff Retrieves all staff members with ID, name, and email. Used to attribute a reply to the right agent when posting a staff update.

Frequently Asked Questions

What can FlowRunner do with HappyFox?

FlowRunner agents can run List Tickets, Get Ticket, and Create Ticket in HappyFox, plus 6 more actions.

Does connecting HappyFox to FlowRunner require OAuth?

No. HappyFox connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can HappyFox trigger a FlowRunner workflow automatically?

HappyFox doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with HappyFox

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us