# Supportbee AI integration on Definable

> SupportBee is a web-based email support tool that helps businesses organize their customer support emails efficiently.

## What this connects

SupportBee is a web-based email support tool that helps businesses organize their customer support emails efficiently.

Vendor: https://supportbee.com/

## Tools available

**41** tools available. First 12:

- `SUPPORTBEE_ADD_LABEL_TO_TICKET` — Add Label to Ticket — Tool to add a label to a ticket. Use when you need to categorize or tag a ticket with a specific label. The label must already exist in your SupportBee account before adding it to a ticket.
- `SUPPORTBEE_ARCHIVE_TICKET` — Archive SupportBee Ticket — Tool to archive a SupportBee ticket by its ID. Use when you want to move resolved tickets to the archive.
- `SUPPORTBEE_ASSIGN_TICKET_TO_TEAM` — Assign Ticket to Team — Assigns a ticket to a team in SupportBee. Use when you need to route a support ticket to a specific team for handling. Note: If the ticket is already assigned to a team and a user, reassigning to another team will remove the user assignee.
- `SUPPORTBEE_CREATE_COMMENT` — Create Ticket Comment — Creates an internal comment on a ticket in SupportBee. Comments are private notes visible only to agents, not to customers. Use this to add internal notes, observations, or collaborate with team members on a ticket.
- `SUPPORTBEE_CREATE_CONSEQUENCE` — Create Consequence — Creates a new consequence for rules automation in SupportBee. Use when setting up automated actions that should be triggered by rules (e.g., auto-assign tickets, archive, or mark as spam).
- `SUPPORTBEE_CREATE_EMAIL` — Create Forwarding Email — Create a new forwarding email address for the company in SupportBee. Use this to add new support email addresses that will forward incoming emails to your SupportBee account as tickets.
- `SUPPORTBEE_CREATE_FILTER` — Create Filter — Creates a filter in SupportBee by linking a rule with a consequence. Use this after creating both a rule (defining match conditions) and a consequence (defining actions to perform).
- `SUPPORTBEE_CREATE_RULE` — Create Rule — Creates a new automation rule in SupportBee to automatically process tickets based on conditions. Rules allow you to automate ticket workflows by: - Matching tickets based on field conditions (subject, sender, body, etc.) - Automatically applying actions like labeling, archiving, assigning, or setting priority Use this after fetching available labels/teams to get valid IDs for actions. The rule will be evaluated for all new and existing tickets matching the conditions. Returns the created rule's unique ID.
- `SUPPORTBEE_CREATE_SNIPPET` — Create Snippet — Create a reusable snippet (canned response) in SupportBee. Snippets are pre-written text templates that agents can quickly insert into ticket replies. Use this to create standard responses for common customer inquiries like refunds, FAQs, or welcome messages.
- `SUPPORTBEE_CREATE_TICKET` — Create SupportBee Ticket — Creates a new support ticket in SupportBee with a subject, content, and requester details. Use this action to: - Create tickets from customer inquiries or issues - Assign tickets to specific agents or teams during creation - Add tags and labels for better ticket organization - Include CC recipients to keep stakeholders informed The ticket will be created in an unanswered state and will appear in the inbox unless marked as spam.
- `SUPPORTBEE_CREATE_TICKET_REPLY` — Create Ticket Reply — Create a reply to a support ticket in SupportBee. Replies are sent to customers via email and are visible to them. Use this when you need to respond to a customer's ticket with information, updates, or solutions. Provide the ticket ID and HTML-formatted content for your reply.
- `SUPPORTBEE_CREATE_USER_OR_CUSTOMER_GROUP` — Create SupportBee User — Invites a new user to your SupportBee account. The user will receive an email invitation and can be assigned as an agent (handles tickets), admin (full access), or collaborator (view/comment only). Use this when you need to add team members to your helpdesk programmatically.

## Auth

Auth schemes: `API_KEY`.

## How agents use Supportbee

Inside a Definable workflow, Supportbee is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Supportbee** — the Researcher (GPT-5.5) pulls context from Supportbee (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Supportbee** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Supportbee (create record, post message, draft email).
- **Designer / Engineer → Distributor → Supportbee** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Supportbee (attach file, open PR comment, post status).

The Verifier checks every Supportbee call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- customer support — https://definable.ai/apps/category/customer-support/
- email — https://definable.ai/apps/category/email/

## Related

- HTML page: https://definable.ai/apps/supportbee/
- Same category (customer support): https://definable.ai/apps/category/customer-support/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt