--- title: Front API Integration on Truto slug: front category: Helpdesk canonical: "https://truto.one/integrations/detail/front/" --- # Front 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. - **Users** — The User object represents a User. ### Unified Ticketing API - **Accounts** — Accounts represent the companies or organizations that you are in contact with. Accounts have one or more Contacts associated with them. - **Attachments** — Attachments are the files associated with a ticket or a comment. - **Collections** — Tickets and contacts can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. You can differentiate between these grouping systems using the type attribute of a Collection. - **Comments** — Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments. - **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. - **Tags** — Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them. - **Teams** — Teams represent the grouping system used for Users. These are usually called groups, teams, agent groups, etc. in the underlying products. A User can belong to one or more Teams. - **Ticket Status** — Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status. - **Tickets** — Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product. - **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 199 tools for Front that AI agents can call directly. - **list_all_front_teammates** — List teammates in Front. Returns id, email, username, first_name, last_name, license_type, is_admin, is_available, is_blocked, type, and custom_fields for each teammate. - **get_single_front_teammate_by_id** — Get a teammate in Front by id. Returns fields including id, email, username, first_name, last_name, license_type, is_admin, is_available, is_blocked, type, and custom_fields. - **update_a_front_teammate_by_id** — Update a teammate in Front. Requires id. Updates may include username, first_name, last_name, is_available, and custom_fields. Custom fields must be fully provided if updated, otherwise existing ones will be erased. - **list_all_front_teams** — List teams in Front. Returns an array of teams with id (unique identifier), name (team name), and _links.self (resource URL). - **get_single_front_team_by_id** — Get a specific team in Front by id. Returns id (unique identifier of the team), name (team name), inboxes (list of associated inboxes), and members (list of teammates with their details). - **create_a_front_team** — Add one or more teammates to a team in Front. Requires id. Takes teammate_ids in the request body. Returns no content on success. - **delete_a_front_team_by_id** — Remove one or more teammates from a team in Front. Requires id (team_id). No content is returned in the response. - **list_all_front_conversations** — List conversations in Front in reverse chronological order. Returns id, subject, status, assignee, recipient, tags, links, custom_fields, is_private, scheduled_reminders, and metadata. - **get_single_front_conversation_by_id** — Get a conversation in Front. Requires id. Returns fields including id (conversation identifier), subject (conversation subject), status (conversation status), assignee (assigned teammate), recipient (main recipient), tags (labels for classification), links (connected external resources), custom_fields (metadata), created_at (creation timestamp), waiting_since (oldest unreplied message), is_private, scheduled_reminders, and metadata (external_conversation_ids). - **update_a_front_conversation_by_id** — Update a conversation in Front. Requires id. Returns no content on success, 301 if merged (redirect to merged conversation), or 400 if invalid custom fields are provided. - **create_a_front_conversation** — Create a new discussion conversation in Front that only supports comments. Requires type, subject, and comment. Returns id, subject, status, assignee, recipient, tags, links, custom_fields, is_private, scheduled_reminders, and metadata in the response. - **front_conversations_update_assignee** — Update conversation assignee in Front. Requires id and assignee_id. Response returns no content on success and may redirect if conversation is merged. - **front_conversations_update_reminders** — Update conversation reminders in Front. Requires id. Snooze or unsnooze a conversation for a user. For private conversations, reminders can only be updated by the teammate who owns it. For shared conversations, reminders apply to all teammates in shared inboxes. Returns no content on success or a redirect if the conversation was merged. - **list_all_front_inboxes** — List inboxes in Front. Returns id, name, is_private, is_public, custom_fields, and related resource links for each inbox. - **get_single_front_inbox_by_id** — Get an inbox in Front. Requires id. Returns id (unique identifier), name (inbox name), is_private, is_public, custom_fields, and related links to teammates, conversations, channels, and owner. - **create_a_front_inbox** — Create an inbox in Front in the oldest active workspace accessible by the token. Requires name. Returns no content in the response. To specify a workspace, use the Create team inbox endpoint instead. - **list_all_front_events** — List events in Front. Returns events in reverse chronological order with fields including id (unique identifier), type (event type), emitted_at (timestamp), source, target, and conversation details. - **get_single_front_event_by_id** — Get a specific event in Front. Requires id. Returns event details including id (unique identifier), type (event type), emitted_at (timestamp), source (triggering resource), target (affected resource), and conversation (related conversation). - **list_all_front_accounts** — List accounts in Front. Returns id, name, logo_url, description, domains, external_id, custom_fields, created_at, and updated_at for each account. - **get_single_front_account_by_id** — Get account in Front by id. Returns id, name, logo_url, description, domains, external_id, custom_fields, created_at, updated_at, and related links. - **create_a_front_account** — Create a new account in Front. Requires name. Returns id, name, logo_url, description, domains, external_id, custom_fields, created_at, and updated_at. - **delete_a_front_account_by_id** — Delete an account in Front. Requires id. Returns no content in response. - **update_a_front_account_by_id** — Update account in Front using id. Returns id, name, logo_url, description, domains, external_id, custom_fields, created_at, and updated_at in the response. - **list_all_front_tags** — List all tags in Front. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at for each tag. - **get_single_front_tag_by_id** — Get a specific tag in Front using id. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at. - **create_a_front_tag** — Create a tag in Front using the legacy endpoint. Requires name. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at fields. - **update_a_front_tag_by_id** — Update a tag in Front. Requires id. Returns no content in response. - **delete_a_front_tag_by_id** — Delete a tag in Front. Requires id. Returns no content in the response. - **list_all_front_inbox_teammates** — List teammates with access to an inbox in Front. Requires inbox_id. Returns teammate id, email, username, first_name, last_name, license_type, is_admin, is_available, is_blocked, type, and custom_fields. - **create_a_front_inbox_teammate** — Add access for one or more teammates to a Front inbox. Requires id. Returns no content in the response. - **delete_a_front_inbox_teammate_by_id** — Remove one or more teammates from an inbox in Front. Requires inbox_id and teammate_ids. Returns no content on success. - **list_all_front_account_contacts** — List contacts for an account in Front. Requires account_id. Returns id, name, description, avatar_url, links, lists, handles, custom_fields, and is_private for each contact. - **create_a_front_account_contact** — Add contacts to an account in Front. Requires id. Returns no content in the response after successfully adding the specified contact_ids. - **delete_a_front_account_contact_by_id** — Delete contacts from a specific account in Front. Requires id for the account and contact_ids in the request body. Returns no content in the response. - **create_a_front_channel_message** — Create a new channel message in Front. Requires channel_id. Returns status indicating if the request was accepted and message_uid as the unique identifier for the created message. - **list_all_front_channels** — List channels in Front. Returns id (unique channel identifier), name, address, types (channel type), send_as, settings (undo_send_time, reply permissions), is_private, and is_valid fields for each channel. - **get_single_front_channel_by_id** — Get a specific channel in Front using id. Returns id, name, address, type, send_as, settings (undo_send_time, all_teammates_can_reply), is_private, and is_valid. - **create_a_front_channel** — Create a channel in an inbox in Front. Requires inbox_id and type. Returns no content on success. - **update_a_front_channel_by_id** — Update a channel in Front. Requires id. Returns no content in the response. - **front_channels_validate** — Validate an SMTP channel in Front using id. This asynchronously validates the SMTP settings and returns the status field indicating whether the request was accepted. - **list_all_front_contacts** — List contacts in Front. Returns id, name, description, avatar_url, links, lists, handles, custom_fields, and is_private for each contact. - **get_single_front_contact_by_id** — Get a specific contact in Front using id. Returns fields including id, name, description, avatar_url, links, lists, handles, custom_fields, and is_private. - **create_a_front_contact** — Create a new contact in Front. Requires handles. Returns id, name, description, avatar_url, links, lists, handles, custom_fields, and is_private. - **update_a_front_contact_by_id** — Update a contact in Front. Requires id. The response returns no content (204) on success. - **delete_a_front_contact_by_id** — Delete a specific contact in Front. Requires id. Returns no content in the response. - **create_a_front_custom_message** — Receive a custom message in Front. Requires channel_id. Returns status (accepted if successful) and message_uid for tracking the created message. - **create_a_front_import_message** — Import a message into Front for a specific inbox using inbox_id. Returns status indicating acceptance and message_uid to track the imported message. - **create_a_front_conversation_comment** — Create a comment in a conversation in Front. Requires conversation_id. Returns id as the comment identifier, author details (including id, email, username, and custom_fields), body of the comment, posted_at timestamp, attachments with metadata, and is_pinned status. - **list_all_front_conversation_comments** — List conversation comments in Front for a given conversation_id in reverse chronological order. Returns comments with id, author details, body, attachments, posted_at, and is_pinned fields. - **get_single_front_conversation_comment_by_id** — Get a specific comment in Front. Requires id. Returns id, author details (id, email, username, first_name, last_name), body, posted_at, attachments (id, url, filename, content_type, size, metadata), and is_pinned. - **update_a_front_conversation_comment_by_id** — Update a comment in Front. Requires id. Returns id, author details (id, email, username, name, type), body, posted_at, attachments with metadata, is_pinned, and related links. - **front_conversation_comments_replies** — Add a reply to a comment in Front. Requires id. Returns id, body, author details, posted_at, is_pinned, attachments, and related links. - **front_conversation_comments_mentions** — List teammates mentioned in a comment in Front. Requires id. Returns teammate details including id, email, username, first_name, last_name, is_admin, is_available, is_blocked, type, and custom_fields. - **list_all_front_team_inboxes** — List inboxes in a team in Front. Requires team_id. Returns id (unique inbox identifier), name (inbox name), is_private, is_public, and custom_fields. - **create_a_front_team_inbox** — Create a team inbox in Front. Requires team_id and name. Returns no content on success. - **list_all_front_inbox_conversations** — List inbox conversations in Front. Requires inbox_id. Returns conversation id, subject, status, assignee, recipient, tags, links, custom_fields, is_private, scheduled_reminders, and metadata. - **list_all_front_conversation_messages** — List messages in a conversation in Front. Requires conversation_id. Returns message id, type, created_at, subject, blurb, body, author, recipients, attachments, and metadata in reverse chronological order. - **get_single_front_conversation_message_by_id** — Get a specific conversation_message in Front using id. Returns id, type, subject, blurb, body, text, author details, recipients, attachments, signature, created_at timestamp, and metadata. - **list_all_front_download_attachment** — Download an attachment file in Front. Requires id. Response returns the binary content of the file along with Content-Type (MIME type) and Content-Length (file size in bytes). - **list_all_front_conversation_custom_fields** — List conversation custom fields in Front. Returns id, name, type, description for each field, and values if type is enum. - **list_all_front_contact_custom_fields** — List contact_custom_fields in Front. Returns id, name, description, type, and values for each custom field that can be attached to a Contact. - **list_all_front_me** — Get API token details in Front. Returns id (unique company id), name (company name), and _links.self (resource link). - **list_all_front_account_custom_fields** — List account custom fields in Front. Returns each custom field with id, name, description, type, and possible values if type is enum. - **list_all_front_conversation_search** — Search conversations in Front using query. Returns an array of conversations with fields such as id, subject, status, assignee, recipient, tags, links, custom_fields, created_at, waiting_since, is_private, scheduled_reminders, and metadata. Requires search_query. - **create_a_front_message_template** — Create a message template in Front. Requires name and body. Returns id, name, subject, body, attachments, is_available_for_all_inboxes, inbox_ids, and _links fields in the response. - **list_all_front_message_templates** — List message templates in Front. Returns id, name, subject, body, attachments, availability, and inbox_ids for each template. - **get_single_front_message_template_by_id** — Get a message template in Front by id. Returns id, name, subject, body, attachments, is_available_for_all_inboxes, inbox_ids, and related links in the response. - **update_a_front_message_template_by_id** — Update a specific message template in Front using id. Returns id, name, subject, body, attachments with metadata, is_available_for_all_inboxes, and inbox_ids. - **delete_a_front_message_template_by_id** — Delete a message template in Front. Requires id. The response confirms successful deletion with no content returned. - **list_all_front_company_ticket_statuses** — List company ticket statuses in Front. Returns id, name, category, description, created_at, and updated_at for each ticket status. - **get_single_front_company_ticket_status_by_id** — Get a specific company-ticket-status in Front using id. Returns id, name, category, description, created_at, updated_at, and link to the ticket status. - **list_all_front_teammate_conversations** — List conversations assigned to a teammate in Front using teammate_id. Returns id, subject, status, assignee details, recipient, tags, links, custom_fields, created_at, and metadata for each conversation. - **get_single_front_analytics_export_by_id** — Get an analytics export in Front. Requires id. Returns id, status, progress, created_at, filters, and if complete, url, filename, and size for downloading the export data. - **create_a_front_analytics_export** — Create a new analytics export in Front for messages or events between start and end. Returns id, status, progress, created_at, filters, and a link (_links.self) to check status and download the result. - **get_single_front_analytics_report_by_id** — Get an analytics report in Front using id. Returns uid of the report, status (running, done, failed), progress (0-100), and computed metrics with their id, type, and value. - **create_a_front_analytics_report** — Create a new analytics report in Front. Requires start, end, and metrics. The response includes uid (report identifier), status (running, done, failed), progress (0–100), metrics (computed values), and a _links.self URL to retrieve the report status and result. - **front_application_event_trigger** — Trigger an application-event in Front using application_uid. Requires event_type and app_object in the request. Returns no content on success. - **list_all_front_comment_download_attachment** — Download attachment for a specific comment in Front. Requires comment_id and id. Response returns the binary file along with Content-Type (MIME type) and Content-Length (file size in bytes). - **list_all_front_message_template_download_attachment** — Download an attachment for a message template in Front. Requires message_template_id and id. Returns binary file content along with Content-Type (MIME type) and Content-Length (file size in bytes). - **list_all_front_message_download_attachment** — Download attachment for a message in Front. Requires message_id and id. Returns binary content of the attachment file along with Content-Type (MIME type) and Content-Length (file size in bytes). - **list_all_front_teammate_channels** — List channels of a teammate in Front. Requires teammate_id. Returns id, name, address, types, send_as, settings, is_private, and is_valid for each channel. - **list_all_front_team_channels** — List team channels in Front. Requires team_id. Returns channel id for unique identifier, name for channel name, address for receiving messages, types for channel type, send_as for sender address, settings for configurations, and flags for privacy and validity. - **list_all_front_contact_conversations** — List conversations for a specific contact in Front. Requires contact_id. Returns id, subject, status, assignee, recipient, tags, links, custom_fields, created_at, and metadata for each conversation. - **list_all_front_teammate_contacts** — List teammate contacts in Front. Requires teammate_id. Returns contacts with id, name, description, avatar_url, links, lists, handles, custom_fields, and is_private. - **create_a_front_teammate_contact** — Create a teammate contact in Front. Requires teammate_id. Returns id (unique identifier), name, description, avatar_url, links, lists, handles, custom_fields, and is_private fields for the created contact. - **list_all_front_team_contact** — List contacts of a team in Front. Requires team_id. Returns id, name, description, avatar_url, links, lists, handles, custom_fields, and is_private for each contact. - **create_a_front_team_contact** — Create a team contact in Front. Requires team_id. Returns id (unique contact identifier), name, description, avatar_url, links, lists, handles, custom_fields, and is_private. - **create_a_front_contact_handle** — Create a new contact handle in Front for a specific contact. Requires contact_id. Returns 204 No Content on success, indicating the handle was successfully added. - **delete_a_front_contact_handle_by_id** — Delete a contact handle in Front. Requires contact_id, handle, and source. Returns no content. - **list_all_front_contact_lists** — List contact lists in Front. Returns id, name, is_private, and related links for each contact list. - **create_a_front_contact_list** — Create a contact list in Front using the oldest active workspace available to the token. Requires name. Returns no content in the response. - **delete_a_front_contact_list_by_id** — Delete a contact list in Front. Requires id. Returns no content in the response. - **list_all_front_contact_list_contacts** — List contacts in a contact list in Front. Requires contact_list_id. Returns id, name, description, avatar_url, links, lists, handles, custom_fields, and is_private for each contact. - **create_a_front_contact_list_contact** — Add contacts to a specific contact list in Front. Requires id. Returns no content in the response after successfully adding contacts. - **delete_a_front_contact_list_contact_by_id** — Remove contacts from a contact list in Front. Requires contact_list_id and contact_ids. Returns no content if successful. - **list_all_front_teammate_contact_lists** — List contact lists for a specific teammate in Front. Requires teammate_id. Returns id (unique list identifier), name (list name), and is_private (privacy status). - **create_a_front_teammate_contact_list** — Create a new teammate contact list in Front. Requires teammate_id. Returns 204 No Content on success. - **list_all_front_team_contact_lists** — List team contact lists in Front for a given team_id. Returns id (unique identifier), name (list name), and is_private (privacy status) along with related resource links. - **create_a_front_team_contact_list** — Create a new team contact list in Front. Requires team_id. Returns no content in the response. - **list_all_front_contact_notes** — List notes for a contact in Front. Requires contact_id. Returns author details (id, email, username, first_name, last_name, type), body of the note, created_at timestamp, and links to related resources. - **create_a_front_contact_note** — Create a new contact note in Front for a specific contact using contact_id. Returns author details (id, email, username, name, availability, type, custom_fields), body (content of the note), created_at (timestamp), and related links. - **list_all_front_conversation_events** — List conversation events in Front for a given conversation_id in reverse chronological order. Returns each event with id, type, emitted_at, source, target, and conversation details. - **list_all_front_conversation_followers** — List teammates following a conversation in Front. Requires conversation_id. Returns teammate fields including id, email, username, first_name, last_name, license_type, is_admin, is_available, is_blocked, type, and custom_fields. - **create_a_front_conversation_follower** — Add conversation followers in Front. Requires id and teammate_ids. Returns no content on success or a redirect if the conversation was merged. - **delete_a_front_conversation_follower_by_id** — Delete conversation followers in Front. Requires id for conversation and teammate_ids in request body. Removes specified teammates from the followers list. Returns 204 on success or 301 if conversation has been merged. - **list_all_front_conversation_inboxes** — List inboxes for a conversation in Front. Requires id. Returns id, name, is_private, is_public, custom_fields, and related links for each inbox. - **create_a_front_conversation_link** — Add conversation links in Front using id. Requires either link_ids or link_external_urls request parameter (not both). No content is returned in the response. - **delete_a_front_conversation_link_by_id** — Delete one or more links from a specific conversation in Front. Requires conversation_id and link_ids. Returns no content on success or a redirect if the conversation is merged. - **create_a_front_conversation_tag** — Add one or more tags to a conversation in Front. Requires id. The response returns 204 No Content on success or 301 if the conversation has been merged. - **delete_a_front_conversation_tag_by_id** — Remove one or more tags from a specific conversation in Front. Requires id. Returns no content on success, or a redirect if the conversation has been merged. - **list_all_front_inbox_custom_fields** — List inbox custom fields in Front. Returns id, name, description, type, and possible enum values for fields that can be attached to an inbox. - **list_all_front_links_custom_fields** — List Link's custom fields in Front. Returns id, name, description, type, and values for enum fields. - **list_all_front_teammates_custom_fields** — List teammate's custom fields in Front. Returns id (unique identifier), name (field name), description (field description), type (data type), and values (for enum types) for each custom field. - **list_all_front_drafts** — List drafts in a conversation in Front. Requires conversation_id. Returns draft details including id, type, subject, body, author, recipients, attachments, draft_mode, error_type, created_at, and metadata. - **create_a_front_draft** — Create a draft in Front for a given channel_id. Requires channel_id and body. Returns draft details including id, subject, body, recipients, author, draft_mode, created_at, and attachments. - **delete_a_front_draft_by_id** — Delete a draft in Front. Requires id and version. Returns no content in the response. - **update_a_front_draft_by_id** — Update a draft in Front using id. Returns fields including id (unique message identifier), message_uid (secondary identifier), type (message type), is_inbound (direction), draft_mode (visibility), version (current draft version), created_at (timestamp), subject, blurb (preview), author (teammate info), recipients, body, text (plain body), attachments, signature, and metadata. - **front_drafts_reply** — Create a draft reply in Front for the last message in a conversation using conversation_id. Returns message id, message_uid, type, is_inbound, draft_mode, subject, blurb, author, recipients, body, text, attachments, signature, and metadata. - **list_all_front_inbox_channels** — List inbox channels in Front for a given inbox_id. Returns id, name, address, types, send_as, settings, is_private, and is_valid for each channel. - **list_all_front_knowledge_bases** — List knowledge bases in Front. Returns id, type, locales, created_at, updated_at, and _links for each knowledge base. - **get_single_front_knowledge_base_by_id** — Get a knowledge base in Front. Requires id. Returns id, type, locales, created_at, updated_at, and links to related articles and categories. - **create_a_front_knowledge_base** — Create a knowledge base in Front. Requires name. Returns id (unique identifier), name, status (published or unpublished), type (internal or external), locale, created_at, updated_at, and related resource links in the response. - **update_a_front_knowledge_base_by_id** — Update knowledge base in Front using id. Will republish if currently published. Returns id, name, status, type, locale, created_at, updated_at, and related resource links. - **get_single_front_knowledge_base_content_by_id** — Get knowledge base content in Front by id. Requires id. Returns id, name, status, type, locale, created_at, updated_at, and links to related articles and categories. - **list_all_front_knowledge_base_categories** — List categories in a knowledge base in Front. Requires knowledge_base_id. Returns id, slug, is_hidden, locales, created_at, updated_at, and related links for each category. - **list_all_front_knowledge_base_articles** — List knowledge-base-articles in Front for a specific knowledge_base_id. Returns id (unique identifier), slug (article URL slug), locales (supported languages), created_at (creation timestamp), and updated_at (last updated timestamp). - **get_single_front_knowledge_base_article_by_id** — Get a knowledge base article in Front. Requires id. Returns id, slug, locales, created_at, updated_at, and links to related resources. - **delete_a_front_knowledge_base_article_by_id** — Delete a knowledge base article in Front. Requires id. Returns id, slug, locales, created_at, updated_at, and _links for the deleted article. - **get_single_front_knowledge_base_article_content_by_id** — Get knowledge base article content in Front using id. Returns id, slug, name, status, keywords, content, locale, attachments, and metadata about the article including creation, update, and last edit timestamps. - **update_a_front_knowledge_base_article_content_by_id** — Update knowledge base article content in Front using id. Returns id, slug, name, status, keywords, content, locale, attachments, and metadata such as created_at, updated_at, and last_edited_at. - **create_a_front_knowledge_base_article_content** — Create knowledge-base-article-content in Front within a knowledge base using knowledge_base_id. Returns id, slug, name, status, keywords, content, locale, attachments, created_at, updated_at, and last_edited_at. - **front_knowledge_base_article_content_download** — Download attachment from a knowledge-base article in Front. Requires article_id and id. Returns the binary file content along with Content-Type (MIME type) and Content-Length (file size in bytes) in the response. - **list_all_front_links** — List links in Front. Returns id (unique identifier), name (display name), type (link type), external_url (external reference), and custom_fields (custom metadata). - **get_single_front_link_by_id** — Get a specific link in Front using id. Returns id, name, type, external_url, custom_fields, and _links.self, which describe the external resource and its metadata. - **create_a_front_link** — Create a link in Front. Requires either pattern or external_url (but not both). Returns id, name, type, external_url, custom_fields, and _links for the created or updated link. - **update_a_front_link_by_id** — Update a link in Front by id. Requires id. Returns no content in the response. - **list_all_front_link_conversations** — List conversations linked to a specific link in Front. Requires id. Returns conversations with fields including id, subject, status, assignee, recipient, tags, links, custom_fields, created_at, and metadata. - **list_all_front_company_rules** — List company rules in Front. Returns id (unique identifier), name (rule name), actions (list of rule actions), and is_private (individual rule indicator). - **list_all_front_rules** — List rules in Front. Returns id, name, actions describing the rule behavior, is_private indicating rule scope, and related links including owner. - **get_single_front_rule_by_id** — Get a specific rule in Front using id. Returns id, name, actions (list of rule actions), is_private (whether individual), and _links (self and owner references). - **list_all_front_teammate_rules** — List teammate rules in Front. Requires teammate_id. Returns id (rule identifier), name (rule name), actions (list of actions), and is_private (rule visibility). - **list_all_front_team_rules** — List rules of a specific team in Front. Requires team_id. Returns id (rule identifier), name (rule name), actions (list of actions), and is_private (whether the rule is individual). - **list_all_front_child_message_templates** — Get child message templates in Front for a specific message_template_folder_id. Returns id, name, created_at, updated_at, and _links for each template. - **create_a_front_child_message_template** — Create a child message template in Front. Requires message_template_folder_id. Returns id, name, subject, body, attachments, is_available_for_all_inboxes, and inbox_ids of the created template. - **list_all_front_teammate_message_templates** — List message templates for a specific teammate in Front. Requires teammate_id. Returns id, name, subject, body, attachments, is_available_for_all_inboxes, and inbox_ids for each message template. - **create_a_front_teammate_message_template** — Create a message template for a teammate in Front. Requires teammate_id. Response returns id, name, subject, body, attachments, is_available_for_all_inboxes, and inbox_ids. - **list_all_front_team_message_templates** — List team message templates in Front for a specific team using team_id. Returns id (unique identifier), name (template name), subject, body, attachments (with metadata), is_available_for_all_inboxes, and inbox_ids. - **create_a_front_team_message_template** — Create a team message template in Front for the given team_id. Returns id, name, subject, body, attachments, is_available_for_all_inboxes, and inbox_ids. - **list_all_front_message_template_folders** — List message template folders in Front. Returns id, name, created_at, updated_at, and related links for each folder. - **get_single_front_message_template_folder_by_id** — Get a message template folder in Front by id. Returns id, name, created_at, updated_at, and related links for owner, parent_folder, child_folders, and child_answers. - **create_a_front_message_template_folder** — Create a new message template folder in Front in the oldest active workspace accessible by the token. Requires name. Returns id, name, created_at, updated_at, and related links in the response. - **update_a_front_message_template_folder_by_id** — Update a message template folder in Front. Requires id. Returns id, name, created_at, updated_at, and _links with related owner, parent_folder, child_folders, and child_answers. - **delete_a_front_message_template_folder_by_id** — Delete a message template folder in Front by id. This will also remove its child folders and templates. The response returns status indicating deletion acceptance and message_template_folder_id of the deleted folder. - **list_all_front_child_folders** — Get child message template folders in Front by providing id. Returns each folder's id, name, creation and update timestamps, and related links including parent, children, owner, and contained message templates. - **create_a_front_child_folder** — Create a child folder in Front under a parent message_template_folder_id. Returns id, name, _links, created_at, and updated_at for the new folder. - **list_all_front_teammate_folders** — List message template folders for a specific teammate in Front. Requires teammate_id. Returns id, name, created_at, updated_at, and resource links for each folder. - **create_a_front_teammate_folder** — Create a new message template folder for a teammate in Front. Requires teammate_id. Returns id, name, created_at, updated_at, and _links for navigation. - **list_all_front_team_folders** — List team folders in Front for the given team_id. Returns id, name, created_at, updated_at, and related links for each message template folder. - **create_a_front_team_folder** — Create a new team folder in Front for a given team_id. Returns id, name, created_at, updated_at, and related links for the folder. - **list_all_front_shifts** — List shifts in Front. Returns id, name, color, timezone, times (shift intervals per day), created_at, and updated_at for each shift. - **get_single_front_shift_by_id** — Get a specific shift in Front using id. Returns id, name, color, timezone, times for each day, created_at, updated_at, and related links for teammates and owner. - **create_a_front_shift** — Create a shift in Front. Requires name, color, timezone, times, and teammate_ids. Returns id (unique identifier), name, color, timezone, times (daily intervals), created_at, and updated_at. - **update_a_front_shift_by_id** — Update a shift in Front. Requires id. Returns no content in the response upon success. Key fields to update include name, color, timezone, times (with start and end per day), and teammate_ids. - **list_all_front_shift_teammates** — List teammates assigned to a shift in Front. Requires shift_id. Returns id, email, username, first_name, last_name, is_admin, is_available, is_blocked, type, and custom_fields for each teammate. - **create_a_front_shift_teammate** — Add teammates to a shift in Front. Requires id of the shift. The teammates must belong to the team that owns the shift. Returns no content on success. - **delete_a_front_shift_teammate_by_id** — Remove teammates from a shift in Front. Requires id. Returns no content in response. - **list_all_front_teammate_shifts** — List teammate shifts in Front. Requires teammate_id. Returns id, name, color, timezone, times, created_at, and updated_at for each shift. - **list_all_front_team_shifts** — List team-shifts in Front for a given team_id. Returns shift id, name, color, timezone, times per day, and created_at/updated_at timestamps. - **create_a_front_team_shift** — Create a team shift in Front. Requires team_id. Returns id (unique identifier of the shift), name, color, timezone, times (shift intervals), created_at, and updated_at. - **get_single_front_signature_by_id** — Get a specific signature in Front. Requires id. Returns id, name, body, sender_info, is_private, is_visible_for_all_teammate_channels, is_default, channel_ids, and related links. - **update_a_front_signature_by_id** — Update a signature in Front using id. Returns id, name, body, sender_info, is_private, is_visible_for_all_teammate_channels, is_default, and channel_ids in the response. - **delete_a_front_signature_by_id** — Delete a specific signature in Front. Requires id. Returns no content in the response upon successful deletion. - **list_all_front_teammate_signatures** — List teammate signatures in Front. Requires teammate_id. Returns id, name, body, sender_info, is_private, is_visible_for_all_teammate_channels, is_default, and channel_ids for each signature. - **create_a_front_teammate_signature** — Create a teammate signature in Front. Requires teammate_id, name, and body. Returns id, name, body, sender_info, is_private, is_visible_for_all_teammate_channels, is_default, channel_ids, and links in the response. - **list_all_front_team_signatures** — List team signatures in Front for a given team_id. Returns id, name, body, sender_info, is_private, is_visible_for_all_teammate_channels, is_default, and channel_ids for each signature. - **create_a_front_team_signature** — Create a new team signature in Front for a given team_id. Returns id, name, body, sender_info, is_visible_for_all_teammate_channels, is_default, is_private, channel_ids, and links to related resources. - **list_all_front_company_tags** — List company tags in Front. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at for each tag. - **create_a_front_company_tag** — Create a company tag in Front. Requires name. Returns id (unique identifier), name, description, highlight color, is_private, is_visible_in_conversation_lists, created_at, and updated_at. - **list_all_front_tag_children** — List child tags of a specific tag in Front. Requires id. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, updated_at, and related links. - **create_a_front_tag_child** — Create a child tag in Front under a specific tag using id. Returns tag fields including id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at. - **list_all_front_tagged_conversations** — List conversations tagged with a specific tag in Front. Requires id. Returns conversation id, subject, status, assignee, recipient, tags, links, custom_fields, is_private, scheduled_reminders, and metadata. - **list_all_front_teammate_tags** — List tags for a teammate in Front. Requires teammate_id. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at for each tag. - **create_a_front_teammate_tag** — Create a teammate tag in Front. Requires teammate_id. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at. - **list_all_front_team_tags** — List team tags in Front for a given team_id. Returns id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, and updated_at for each tag. - **create_a_front_team_tag** — Create a team tag in Front. Requires team_id. Returns tag id, name, description, highlight, is_private, is_visible_in_conversation_lists, created_at, updated_at, and related resource links in the response. - **list_all_front_teammate_groups** — List teammate groups in Front. Returns id, name, description, is_managed_by_scim, permissions, and related links for each teammate group. - **get_single_front_teammate_group_by_id** — Get a teammate group in Front by id. Returns id, name, description, is_managed_by_scim, permissions (with access and contact_list_ids), and related links to teammates, teams, and inboxes. - **create_a_front_teammate_group** — Create a new teammate group in Front. Requires name. Returns id (unique identifier), name, description, is_managed_by_scim, permissions, and links to related teammates, teams, and inboxes. - **update_a_front_teammate_group_by_id** — Update a teammate group in Front. Requires id. Returns no content. You cannot modify a teammate group managed by SCIM. - **delete_a_front_teammate_group_by_id** — Delete a teammate group in Front. Requires id. You cannot delete a teammate group that is managed by SCIM. Returns no content in the response. - **list_all_front_teammate_group_inboxes** — List inboxes for a teammate group in Front. Requires teammate_group_id. Returns inbox id, name, is_private, is_public, custom_fields, and related resource links. - **create_a_front_teammate_group_inbox** — Add teammate group inboxes in Front using teammate_group_id. Links non-public inboxes from teams already in the group. Returns no content in the response. - **delete_a_front_teammate_group_inbox_by_id** — Delete teammate group inboxes in Front. Requires teammate_group_id. Unlinks the specified non-public inboxes from the teammate group. Returns no content in the response. - **list_all_front_teammate_group_teammates** — List teammates in a specific teammate group in Front. Requires teammate_group_id. Returns id, email, username, first_name, last_name, is_admin, is_available, is_blocked, type, and custom_fields for each teammate. - **create_a_front_teammate_group_teammate** — Add teammates to a specific teammate group in Front using id. Returns no content. You cannot modify a teammate group that is managed by SCIM. - **delete_a_front_teammate_group_teammate_by_id** — Remove teammates from a teammate group in Front. Requires id (teammate_group_id). You must provide teammate_ids in the request body. Groups managed by SCIM cannot be modified. Returns no content on success. - **list_all_front_teammate_group_teams** — List teams added to the teammate group in Front. Requires teammate_group_id. Returns team id, name, and links to the team resource. - **create_a_front_teammate_group_team** — Add teams to a teammate group in Front. Requires teammate_group_id. Automatically links public inboxes; non-public inboxes must be added separately. Returns no content in the response. - **delete_a_front_teammate_group_team_by_id** — Remove teams from a teammate group in Front. Requires teammate_group_id. Unlinks associated team inboxes. Request must include team_ids to remove. Returns no content. ## How it works 1. **Link your customer's Front 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 Front.** The Proxy API is a 1-to-1 mapping of the Front 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-Powered Triage and Draft Generation for Support Teams** — AI support platforms can ingest inbound Front conversations, classify intent with tags, and inject pre-written draft replies directly into the agent's composer — cutting Level-1 response times dramatically while keeping humans in the loop. - **Bidirectional CRM-to-Front Contact and Account Sync** — Vertical CRMs and customer data platforms can mirror contacts, accounts, and custom fields between their system and Front so agents always see up-to-date customer context without switching tools. - **Customer Success Platforms Monitoring Communication Health** — CS and account health tools can pull conversation events, analytics exports, and response-time data from Front to surface churn signals like SLA breaches or stalled threads on high-value accounts. - **Cross-Platform Ticket Linking for Engineering Escalation** — Project management and bug-tracking SaaS products can attach external resource links to Front conversations, giving support agents real-time visibility into whether an escalated engineering issue has been resolved. - **Knowledge Base and Template Management from External Content Systems** — Documentation and content management platforms can push articles into Front's knowledge bases and sync message templates so agents have instant access to approved, up-to-date response content. ## What you can build - **AI Draft Injection** — Automatically generate and insert draft replies into Front conversations so agents review and send with one click, using create_a_front_draft and update_a_front_draft_by_id. - **Automated Conversation Routing and Tagging** — Classify inbound messages by intent or priority, apply tags via create_a_front_conversation_tag, and reassign to the right teammate with front_conversations_update_assignee based on shift schedules. - **Two-Way Contact and Account Sync** — Keep customer records consistent across your product and Front by syncing contacts and accounts bidirectionally using the Unified Ticketing API's Contacts and Accounts resources. - **Contextual Internal Notes on Conversations** — Post private comments on Front threads — such as billing alerts, order statuses, or account health scores — via create_a_front_conversation_comment so agents have context without leaving their inbox. - **External Link Attachment for Cross-Tool Traceability** — Permanently tie CRM deal IDs, bug tracker URLs, or internal case references to Front conversations using create_a_front_conversation_link for full cross-platform traceability. - **Analytics and SLA Monitoring Pipeline** — Export conversation analytics with create_a_front_analytics_export and track events via list_all_front_events to power SLA dashboards and churn-risk alerts in your product. ## FAQs ### How does Truto handle authentication with Front? Truto manages the full OAuth flow for Front on your behalf. Your end users connect their Front workspace through Truto's managed auth, and you never need to handle token storage, refresh, or revocation directly. ### How do Front concepts map to Truto's Unified APIs? Front Conversations map to Tickets in the Unified Ticketing API, Front Teammates map to Users in both the Unified User Directory and Ticketing APIs, and Front Tags, Contacts, Accounts, Comments, and Teams map to their corresponding Unified Ticketing resources. ### Does Truto support reading and writing custom fields in Front? Yes. Truto exposes tools for listing custom fields on conversations, contacts, accounts, inboxes, links, and teammates — such as list_all_front_conversation_custom_fields and list_all_front_contact_custom_fields — through the Unified Ticketing API's Fields resource. ### Can I manage Front knowledge bases and message templates through Truto? Yes. You can create, read, update, and delete knowledge bases and their articles, as well as message templates and template folders, using dedicated tools like create_a_front_knowledge_base, update_a_front_knowledge_base_article_content_by_id, and create_a_front_message_template. ### Does Truto handle pagination when listing Front conversations or events? Yes. Truto abstracts away Front's cursor-based pagination. When you call list endpoints like list_all_front_conversations or list_all_front_events, Truto handles page traversal automatically so you receive complete result sets. ### What conversation-level actions can I perform beyond reading data? You can update conversation status, assign or reassign teammates, add or remove tags, post internal comments with @mentions, attach external links, manage followers, create and update drafts, and send messages — all through Truto's proxy and unified API layer.