App Store
The App Store is where TextSetu connects to the tools your team already uses. Apps add capabilities to a project — syncing strings with a code repository, machine translation, custom editor panels, and more — without leaving TextSetu.
Where to find it. Open your organization's App Store from the org menu, or a project's Apps menu to see what's enabled for that project.
How apps install
Apps install at two levels, and most integrations use both:
- Organization — install the app once for the whole org (this is where shared credentials and connections live, e.g. the GitHub App). Requires the Manage organization permission.
- Project — enable an org-installed app on a specific project and configure it there, or install some apps directly into a single project. Requires the Manage project permission.
Each app declares the scopes it needs (for example, read translations and write translations). Those scopes are granted at install time and enforced on every action the app performs.
Available integrations
| App | What it does |
|---|---|
| GitHub Sync | Continuous localization with a GitHub repository — pull source strings in, push translations back as a pull request. |
Each app appears as a card in the App Store — click Install to add it to your organization:
More integrations are added over time. If an app exposes a page, it appears in the project's Apps menu once enabled.
Automating with the API
Anything an integration does can also be scripted directly against the TextSetu API — importing sources, exporting translations, and managing projects. Integrations are the no-code path; the API is the build-your-own path. See the API Reference and the MCP server for details.