Connect Ninety to Simpleen Translation

Both apps 38Ninety 25Simpleen Translation 13

• Trigger
  New Issue Created

  Triggered when a new issue is created in Ninety, optionally only on one team or only short-term vs long-term issues.

• Trigger
  New Measurable

  Triggered when a new measurable (KPI) is added to your Ninety scorecard, optionally only those tracked over a given period like weekly or monthly.

• Trigger
  New Team

  Triggered when a new team is created in your Ninety company.

• Trigger
  To-Do Created, Updated, or Deleted

  Triggered when a to-do is created or changed in Ninety — including being completed or archived — optionally only on one team or only personal to-dos. Ninety's API does not report hard deletions, so a removed to-do simply stops appearing rather than firing this trigger.

• Action
  Create Issue

  Creates an issue on a Ninety team's issues list.

• Action
  Create Milestone

  Creates a milestone on a Ninety rock, with a title and due date.

• Action
  Create Rock

  Creates a rock (a quarterly goal) for a Ninety team, with a due date, status and level.

• Action
  Create To-Do

  Creates a to-do on a Ninety team, with a due date and optional description.

• Action
  Delete Issue

  Deletes an existing Issue in Ninety by its ID.

• Action
  Delete Measurable Note

  Deletes the note on a Measurable for one scorecard period.

• Action
  Delete Measurable Score

  Deletes the score on a Measurable for one scorecard period.

• Action
  Delete Rock

  Deletes a Rock in Ninety by its ID. Returns the deleted Rock's ID along with the status Ninety returned.

• Action
  Delete To-Do

  Deletes a to-do in Ninety by its ID. Use it to remove a to-do that was created by mistake or is no longer needed.

• Action
  Find Issue

  Searches Ninety for issues matching the words you provide, optionally narrowed to one team or to short-term vs long-term issues. Returns the matching issues.

• Action
  Find Measurable

  Searches Ninety's scorecard for measurables (KPIs) matching the words you provide, optionally limited to a tracking period like weekly or monthly. Returns the matching measurables.

• Action
  Find Milestone

  Searches Ninety for milestones by title. Ninety carries milestones on their rocks, so this reads the rocks (optionally just one team's) and returns the milestones whose title matches, optionally limited to a single rock.

• Action
  Find Rock

  Searches Ninety for rocks (quarterly goals) matching the words you provide, optionally narrowed to one team or one status. Returns the matching rocks.

• Action
  Find Team

  Returns the teams in your Ninety company, optionally only those whose name contains the words you provide. Use it to get the team ID other Ninety actions need.

• Action
  Find To-Do

  Searches Ninety for to-dos matching the words you provide, optionally narrowed to one team, to personal to-dos, or to finished vs open ones. Returns the matching to-dos.

• Action
  Update Issue

  Changes an existing issue in Ninety — its title, detail, team, priority, short-term/long-term setting, or whether it is solved. Fields you leave blank are left as they are.

• Action
  Update Measurable Note

  Saves the note on a Ninety scorecard measurable for one period, replacing any note already there.

• Action
  Update Measurable Score

  Records the score on a Ninety scorecard measurable for one period, replacing any score already there.

• Action
  Update Milestone

  Changes an existing milestone in Ninety — its title, detail, due date, owner, or whether it is finished. Fields you leave blank are left as they are.

• Action
  Update Rock

  Changes an existing rock (quarterly goal) in Ninety — its title, detail, status, owner, team, quarter, due date, or whether it is archived. Fields you leave blank are left as they are.

• Action
  Update To-Do

  Changes an existing to-do in Ninety — its title, detail, due date, owner, team, repeat setting, or whether it is done or archived. Fields you leave blank are left as they are.

• Action
  Add glossary

  Create a new glossary of word entries/ignored terms for translation. POST /glossaries.

• Action
  Add segment

  Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.

• Action
  Create Translation

  Translates content to selected target language

• Action
  Get file

  Get a specific localization file by id, including its segments and languages. GET /files/{id}.

• Action
  Get glossary

  Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.

• Action
  Get segment

  Get a specific translation segment by id. GET /segments/{id}.

• Action
  List files

  List the localization files known to the account. GET /files.

• Action
  List glossaries

  List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.

• Action
  List languages

  List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.

• Action
  List segments

  List translatable segments (source/translated entry pairs) across the user's files. GET /segments.

• Action
  Run translator

  Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.

• Action
  Update glossary

  Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.

• Action
  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.