HappyFox Integrations, and the Systems No App on the List Reaches
A customer writes in saying they were charged twice. HappyFox's Stripe app shows their billing details right in the ticket. Whether someone upgraded the account, paused it or flagged it last week lives in your own admin panel, and no app reads that. HappyFox's directory runs to dozens of apps across dev tools, billing, stores, CRMs, phones, devices and sign-in. What matters is which of your systems made the list, and how to reach the ones that didn't.
HappyFox apps, grouped by what the agent needs in the ticket
From HappyFox's integrations directory. Each one is switched on from the Apps area of the help desk.
Reaching a system that has no HappyFox app
Your own product database, an ERP, a warehouse system: the help desk gives any of them the same two hooks, an API and webhooks.
- 1
Create the API key and auth code
Apps › Goodies › APIHappyFox's REST API takes the key and auth code together as HTTP Basic credentials, on your own account's domain. EU-hosted accounts sit on happyfox.net instead of happyfox.com. Ticket lists page with
sizeandpage. - 2
Register a webhook
Apps › Goodies › WebhooksWebhooks fire when a ticket is created, when one is edited and when a Smart Rule triggers. Note the webhook key HappyFox shows you. Its classic webhook guide uses that key to sign each payload, so your receiver can tell the call really came from your help desk.
- 3
Look the customer up in the other system
The webhook says which ticket changed. Your service takes the requester's email or account ID, asks the system with no app about them, and decides what an agent should see: plan, account status, last order, open balance.
- 4
Write the answer where HappyFox can use it
Store it in ticket or contact custom fields through the API, where the API allows. Agents read it on the ticket, and Smart Rules can match on it like any other field.
Watch for: agents hand-editing a field the sync overwrites. Agree which fields belong to the integration before it goes live.
HappyFox integration questions, app by app
Does HappyFox integrate with Slack?
Yes, through HappyFox's own Slack app. It sends ticket notifications to the channel or DM you pick, and agents can create, reply to and update tickets without leaving Slack. Zapier also has a template that opens a HappyFox ticket when someone adds a reaction to a Slack message.
Does HappyFox work with Zapier?
Yes. HappyFox has a Zapier app, and Make is in its directory too. Zapier works from a set list of HappyFox triggers, such as a new ticket, and actions, such as creating or updating one. When the event or field you need isn't on that list, the REST API is the next stop.
Does HappyFox have a public API?
Yes. It's a REST API covering tickets, categories, custom fields and more, authenticated with an API key and auth code sent as Basic credentials. Webhooks cover the other direction, telling your service when a ticket is created or edited or a Smart Rule fires.
Does HappyFox integrate with Jira?
Yes. The Jira app creates an issue from a ticket and shows the issue's status inside the ticket, so an agent can tell the customer where a fix stands. Carrying priority, customer tier or account value into custom Jira fields is usually built on top.
Who connects HappyFox to a system that isn't in its directory?
n-frames, as a custom build. We write the service behind a HappyFox webhook that looks the customer up in your product database, ERP or warehouse system and writes the answer onto the ticket, and we move ticket history into or out of HappyFox through the API, with custom fields kept where the API allows.
Moving years of tickets in or out of HappyFox
A CSV export from an old help desk tends to arrive flat: replies merged into one blob, custom fields dropped, attachments left behind. Moving history through the APIs on both sides keeps each ticket's replies, custom fields and requester together where both APIs allow it, in batches you can check and rerun. Whether original reply dates carry over depends on what HappyFox's API accepts, so test that on a sample first.
The reverse job comes up too: ticket data copied out to a warehouse so support numbers sit beside revenue and churn. HappyFox lists its own Business Intelligence app for help desk reporting, so a copy through the API earns its keep when the numbers have to join data from other systems.