API integration
Expand your
Helpdesk
integrations with the
Help Scout
API integration.
superAI
Comprehensive Slack AI Agent toolset with fine-grained access control and MCP Server capabilities. Slack MCP Servers works seamlessly with Cursor and Claude AI editors for immediate consumption. Integrates with all popular LLM frameworks including LangChain and PyDantic for advanced AI orchestration.
get_single_helpscout_user_by_id
Get information about a specific user in Help Scout by id. Returns id, firstName, lastName, email, r…
delete_a_helpscout_user_by_id
Delete a user by id in Help Scout. Only Administrators and Account Owners can delete users. The user…
list_all_helpscout_users
List users in Help Scout. Returns an array of user objects including id, firstName, lastName, email,…
get_single_helpscout_tag_by_id
Get a tag by id in Help Scout. Returns id, name, slug, and color of the tag.
list_all_helpscout_tags
List tags used across all inboxes in Help Scout. Returns id, name, slug, ticketCount, color, created…
list_all_helpscout_teams
List teams in Help Scout. Returns an array of teams with fields id, name, initials, mention, created…
get_single_helpscout_user_by_id
Get information about a specific user in Help Scout by id. Returns id, firstName, lastName, email, r…
delete_a_helpscout_user_by_id
Delete a user by id in Help Scout. Only Administrators and Account Owners can delete users. The user…
list_all_helpscout_users
List users in Help Scout. Returns an array of user objects including id, firstName, lastName, email,…
Enhanced
Help Scout
with AI Capabilities
Unified APIs for
Help Scout
Skip writing code for every integration. Save time by using Truto's category-specific Unified APIs. You can use the schema we provide out of the box or customize and override the mappings to suit your needs with AI.
Roles
The Role object represents a role of a User.
Unified User Directory API
Users
The User object represents a User.
Unified User Directory API
Groups
Groups are a collection of users in the source application. In some applications, they might also be called Teams.
Unified User Directory API
Attachments
Attachments are the files associated with a ticket or a comment.
Unified Ticketing API
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. Yo…
Unified Ticketing API
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.
Unified Ticketing API
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.
Unified Ticketing API
Tags
Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them.
Unified Ticketing API
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.
Unified Ticketing API
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.
Unified Ticketing API
Ticket types
Ticket Types represent the classification system used by the underlying products for Tickets. Some examples are bugs, feature, incident, etc.
Unified Ticketing API
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,…
Unified Ticketing API
Ticket status
Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status.
Unified Ticketing API
Users
Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc.
Unified Ticketing API
Workspaces
Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the…
Unified Ticketing API
Proxy API for
Help Scout
✨ Powered by AI
Customize the mappings as you need using AI.
Build your own unified API from scratch, aided by AI.
We have been able to dramatically accelerate our GTM timeline by several months as a result of Truto. The devs at Truto worked with us to build a unified API structure with our team so that we have a solid base for future integrations as well. The support has been very quick to respond to our inquiries and provide timely resolutions for our requests.
Josh Benson,
CEO of Omnitrain