Integration
Connect Freshdesk to Simpleen Translation
When something happens in Freshdesk, your agent does the next thing in Simpleen Translation. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Freshdesk and Simpleen Translation to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Freshdesk and Simpleen Translation
Triggers and actions 3 triggers ยท 34 actions
Trigger
New CompanyTriggers when a new company is created.
- New Contact
Triggers when a new contact is created.
- New Ticket
Triggers when a new ticket is created.
- Add Note to Ticket
Adds a private or public note to a ticket.
- Create Company
Creates a new company.
- Create Contact
Creates a new contact.
- Create Ticket
Creates a new ticket in Freshdesk.
- Delete Contact
Deletes a contact by ID.
- Delete Ticket
Deletes a ticket by ID.
- Get Agent
Retrieves an agent by ID.
- Get Company
Retrieves a company by ID.
- Get Contact
Retrieves a contact by ID.
- Get Ticket
Retrieves a single ticket by ID.
- List Agents
Lists all agents.
- List Companies
Lists companies.
- List Contacts
Lists contacts.
- List Ticket Conversations
Lists all conversations (replies and notes) on a ticket.
- List Tickets
Lists tickets, most recently updated first.
- Reply to Ticket
Adds a public reply to a ticket conversation.
- Search Contacts
Searches contacts using a Freshdesk query string.
- Search Tickets
Searches tickets using a Freshdesk query string.
- Update Company
Updates a company by ID.
- Update Contact
Updates a contact by ID.
- Update Ticket
Updates an existing ticket by ID.
Action
Add glossaryCreate a new glossary of word entries/ignored terms for translation. POST /glossaries.
- Add segment
Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.
- Create Translation
Translates content to selected target language
- Get file
Get a specific localization file by id, including its segments and languages. GET /files/{id}.
- Get glossary
Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
- Get segment
Get a specific translation segment by id. GET /segments/{id}.
- List files
List the localization files known to the account. GET /files.
- List glossaries
List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
- List languages
List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
- List segments
List translatable segments (source/translated entry pairs) across the user's files. GET /segments.
- Run translator
Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
- Update glossary
Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
- Update segment
Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews