Integration
Connect My Music Staff to Simpleen Translation
When something happens in My Music Staff, 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 My Music Staff 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 My Music Staff and Simpleen Translation
Triggers and actions 8 triggers ยท 18 actions
Trigger
Attendance TakenTriggers when attendance is taken or edited for a calendar event.
Trigger
New EmailTriggers when a new email message is created.
Trigger
New InvoiceTriggers when a new invoice is created (manually or by auto-invoicing).
Trigger
New SMSTriggers when a new SMS message is created.
Trigger
New StudentTriggers when a new student is added to your My Music Staff account.
Trigger
Payment AddedTriggers when a payment is recorded in a Family Account.
Trigger
Student Added to EventTriggers when a student is added to an event on the calendar.
Trigger
Student UpdatedTriggers when a student's profile information is updated.
Action
Add PaymentRecords a payment in the Family Account
Action
Add StudentAdds a new student to your My Music Staff account.
Action
Find All ParentsFinds all parents based on Family ID or on search text.
Action
Find Attendance RecordsSearches attendance records by date range, student, teacher, event, or status. Returns matching records with a total count.
Action
Find StudentFinds students based on Student ID or on search text.
Action
Add glossaryCreate a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segmentCreate a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create TranslationTranslates content to selected target language
Action
Get fileGet a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossaryGet a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segmentGet a specific translation segment by id. GET /segments/{id}.
Action
List filesList the localization files known to the account. GET /files.
Action
List glossariesList the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languagesList all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segmentsList translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translatorTranslate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossaryUpdate an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segmentPost-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.