HappyFox logo HappyFox automation · runs daily

Reply to HappyFox tickets with canned actions

You keep canned actions for the answers that repeat, but each one still needs an agent to open the ticket, find the action in a list and apply it, ticket after ticket.

Cotlet does it in your own HappyFox account with list_canned_actions, search_tickets, get_ticket and apply_canned_action, called by your AI agent, an n8n workflow or a script.

Hosted · nothing to install or maintain

Can HappyFox do this on its own?

HappyFox applies a canned action when an agent chooses it in the Reply or Private Note editor, one ticket at a time (checked 20 Oct 2026). Merge fields in canned actions do not work with bulk actions. Nothing reads a ticket and picks the action that fits it.

How you do it in HappyFox today

  1. An admin builds canned actions under Automate >> Canned Actions, each with a predefined response, optional property changes and attachments.
  2. In a ticket the agent clicks Reply or Private Note and picks the canned action from the list inside the editor.
  3. The list shows only canned actions defined for the category of that ticket, so a ticket in another category needs a different action.
  4. The action fills in the response, changes properties such as status, priority and assignee, and adds its attachments, and the agent submits.
  5. Matching an action to a ticket is still a human read each time, and actions with similar names are easy to mix up.

How to reply to HappyFox tickets with canned actions

Prompt

Look at open HappyFox tickets with no reply. Where a canned action clearly fits, such as the password reset steps, apply it as a reply. Show me the ticket and the canned action for anything uncertain.
  1. 01

    Learn your actions

    list_canned_actions returns the names and categories once per run. The agent matches your rule ("password questions get Password reset steps") to an action that exists for the ticket's category.

  2. 02

    Find the candidates

    search_tickets lists open tickets that nobody has answered yet, so a ticket a colleague already replied to is not touched.

  3. 03

    Read before applying

    get_ticket gives the first message. An action is applied only if the ticket clearly fits it. Anything between two actions is listed for you with both names.

  4. 04

    Apply and report

    apply_canned_action applies the action as a reply or a private note, submits it and returns the changes it made. It asks for your OK first, because a reply emails the contact.

  5. 05

    Check the ticket first

    Right before applying, the agent reads the ticket again. If a colleague answered in the meantime, it skips the ticket and logs it.

What you get back

Example data

Open tickets with no reply: 12
Canned action applied 7:
- 4 x Password reset steps (login questions)
- 3 x Invoice copy (billing questions)
No clear action, left for you 5:
- #2090 mentions both billing and a bug
- #2096 is a refund request

Other ways to ask

  • Every morning, apply Out of office hours to tickets that arrived outside working hours and show me the list.
  • Suggest a canned action for each of today's new tickets as a table and apply nothing.
  • Apply the first-response action to unassigned tickets in the Sales category.

What HappyFox allows, and what to know first

  • A HappyFox canned action appears in the editor only if canned actions are defined for the ticket's category.
  • A canned action can change status, priority and assignee, and add predefined attachments, so one apply can also assign the ticket.
  • HappyFox canned actions work in a reply and in a private note, and a private note does not reach the contact.
  • Merge fields in canned actions do not work with bulk actions, so the agent applies them ticket by ticket.

apply_canned_action asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: HappyFox Support: Use Canned Actions for frequent replies · HappyFox Support: Using Canned Actions · HappyFox Support: Perform Bulk Actions on Tickets

Call apply_canned_action from a script

curl

curl -X POST https://cotlet.dev/api/v1/happyfox/tickets/2090/canned-actions/31/apply \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"mode":"reply"}'

Example response

{
  "ticket_id": 2090,
  "update_id": 88140,
  "mode": "reply",
  "canned_action": "Password reset steps",
  "changed": {
    "status": "Awaiting customer"
  },
  "created_at": "2026-10-20T09:03:00Z"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is happyfox_write → apply_canned_action. Example data.

Schedule it in n8n, Make, Zapier or cron

HappyFox tools this automation uses

Cotlet HappyFox tools used to reply to HappyFox tickets with canned actions
Tool Parameters
list_canned_actions category_id
search_tickets queue_id, query, limit, cursor
get_ticket ticket_id
apply_canned_action ticket_id, canned_action_id, mode
All 12 HappyFox tools with descriptions

Frequently asked questions

Is it safe to connect HappyFox to Cotlet?

Yes. You sign in to HappyFox yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get HappyFox once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

Give your agent access to HappyFox.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with HappyFox.