The open alternative to Salesforce, designed for AI.
TypeScript crmcrm-systemcustomergood-first-issuegraphqlhacktoberfestjavascriptmarketingmonoreponestjsopen-sourcepostgresqlreactreactjssalestypescriptweb
i18n - docs translations (#20243)
github-actions[bot]a76047f28bb8
diff --git a/packages/twenty-docs/l/de/developers/extend/apps/connections.mdx b/packages/twenty-docs/l/de/developers/extend/apps/connections.mdxindex 02f1ce90fdb..7614d2f9c1d 100644--- a/packages/twenty-docs/l/de/developers/extend/apps/connections.mdx+++ b/packages/twenty-docs/l/de/developers/extend/apps/connections.mdx@@ -1,20 +1,20 @@----title: Connections-description: Let your app act on a user's behalf in third-party services via OAuth.+title: Verbindungen+description: Ermöglichen Sie Ihrer App, im Namen eines Benutzers über OAuth in Diensten von Drittanbietern zu handeln.icon: plug----Connections are credentials a user holds for an external service (Linear, GitHub, Slack, ...). Your app declares **how** those credentials are obtained — a **connection provider** — and consumes them at runtime to make authenticated calls to the third-party API.+Verbindungen sind Anmeldedaten, die ein Benutzer für einen externen Dienst besitzt (Linear, GitHub, Slack, ...). Ihre App legt fest, **wie** diese Anmeldedaten bezogen werden — ein **Verbindungsanbieter** — und verwendet sie zur Laufzeit, um authentifizierte Aufrufe an die Drittanbieter-API zu tätigen.-Today only OAuth 2.0 is supported. Future credential types (personal access tokens, API keys, basic auth) will plug into the same surface — apps already using `defineConnectionProvider({ type: 'oauth', ... })` won't need to migrate.+Derzeit wird nur OAuth 2.0 unterstützt. Zukünftige Anmeldedatentypen (Personal Access Tokens, API-Schlüssel, Basic Auth) werden in dieselbe Oberfläche integriert — Apps, die bereits `defineConnectionProvider({ type: 'oauth', ... })` müssen nicht migriert werden.<AccordionGroup>-<Accordion title="defineConnectionProvider" description="Declare how your app's connections are obtained">+<Accordion title="defineConnectionProvider" description="Legen Sie fest, wie die Verbindungen Ihrer App bezogen werden">-A connection provider describes the OAuth handshake your app needs. The user clicks "Add connection" in your app's settings, completes the provider's consent screen, and a `ConnectedAccount` row is created in their workspace.+Ein Verbindungsanbieter beschreibt den OAuth-Handshake, den Ihre App benötigt. Der Benutzer klickt in den Einstellungen Ihrer App auf "Verbindung hinzufügen", schließt den Zustimmungsbildschirm des Anbieters ab, und in seinem Arbeitsbereich wird eine `ConnectedAccount`-Zeile erstellt.-A working setup needs **two files** — the connection provider, and a matching `serverVariables` declaration on `defineApplication` that holds the OAuth client credentials.+Eine funktionierende Einrichtung benötigt **zwei Dateien** — den Verbindungsanbieter und eine passende `serverVariables`-Deklaration in `defineApplication`, die die OAuth-Client-Anmeldedaten enthält.```ts src/connection-providers/linear-connection.tsimport { defineConnectionProvider } from 'twenty-sdk/define';@@ -73,14 +73,14 @@ export default defineApplication({Hauptpunkte:-* `name` is the unique identifier string used in `listConnections({ providerName })` (kebab-case, must match `^[a-z][a-z0-9-]*$`).-* `displayName` shows in the per-app settings tab and in the AI tool list.-* `clientIdVariable` / `clientSecretVariable` are **names**, not values — they must match keys declared in `defineApplication.serverVariables`. The actual `client_id` and `client_secret` are entered by the server admin through the app registration UI, never committed to your repo.-* Use `serverVariables` (not `applicationVariables`) — OAuth credentials are server-wide and one OAuth app per Twenty server.-* Until both `serverVariables` are filled in, the per-app settings tab shows a "needs server admin" hint and the "Add connection" button is disabled.-* `type: 'oauth'` is the only supported value today. The discriminator is forward-compatible: future types (`'pat'`, `'api-key'`, ...) will add new sub-config blocks alongside `oauth`.+* `name` ist die eindeutige Bezeichner-Zeichenfolge, die in `listConnections({ providerName })` verwendet wird (kebab-case, muss `^[a-z][a-z0-9-]*$` entsprechen).+* `displayName` wird im Einstellungs-Tab der jeweiligen App und in der KI-Toolliste angezeigt.+* `clientIdVariable` / `clientSecretVariable` sind **Namen**, keine Werte — sie müssen den in `defineApplication.serverVariables` deklarierten Schlüsseln entsprechen. Die tatsächlichen `client_id` und `client_secret` werden vom Serveradministrator über die App-Registrierungsoberfläche eingegeben und niemals in Ihr Repository eingecheckt.+* Verwenden Sie `serverVariables` (nicht `applicationVariables`) — OAuth-Anmeldedaten gelten serverweit und es gibt eine OAuth-App pro Twenty-Server.+* Solange beide `serverVariables` nicht ausgefüllt sind, zeigt der Einstellungs-Tab pro App den Hinweis "Benötigt Server-Admin" an und der Button "Verbindung hinzufügen" ist deaktiviert.+* `type: 'oauth'` ist derzeit der einzige unterstützte Wert. Der Diskriminator ist vorwärtskompatibel: zukünftige Typen (`'pat'`, `'api-key'`, ...) werden neue Unterkonfigurationsblöcke neben `oauth` hinzufügen.-The OAuth callback URL your provider needs to whitelist is:+Die OAuth-Callback-URL, die Ihr Anbieter auf die Whitelist setzen muss, lautet:```https://<your-twenty-server>/apps/oauth/callback@@ -88,9 +88,9 @@ https://<your-twenty-server>/apps/oauth/callback</Accordion>-<Accordion title="listConnections / getConnection" description="Use connections from a logic function">+<Accordion title="listConnections / getConnection" description="Verbindungen aus einer Logikfunktion verwenden">-Inside a logic function handler, `listConnections({ providerName })` returns this app's `ConnectedAccount` rows for the given provider, with refreshed access tokens.+Innerhalb eines Logikfunktions-Handlers gibt `listConnections({ providerName })` die `ConnectedAccount`-Zeilen dieser App für den angegebenen Anbieter zurück, mit aktualisierten Zugriffstoken.```ts src/logic-functions/handlers/create-linear-issue-handler.tsimport { listConnections } from 'twenty-sdk/logic-function';@@ -135,34 +135,34 @@ export const createLinearIssueHandler = async (input: {};```-Each connection has:+Jede Verbindung hat:-| Feld | Beschreibung |-| ------------------ | -------------------------------------------------------------------------------------------------------- |-| `id` | Unique row id; pass to `getConnection(id)` to refetch a single one |-| `sichtbarkeit` | `'user'` (private to one workspace member) or `'workspace'` (shared with all members) |-| `geltungsbereiche` | OAuth permissions granted by the upstream provider (distinct from `visibility` — those are unrelated) |-| `userWorkspaceId` | The owner's userWorkspace id — useful for picking "the request user's connection" in HTTP-route triggers |-| `accessToken` | Fresh OAuth access token (refreshed automatically if expired) |-| `name` / `handle` | The connection's display name (auto-derived at OAuth callback, user-renameable) |-| `authFailedAt` | Set when the most recent refresh failed; the user must reconnect |+| Feld | Beschreibung |+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |+| `id` | Eindeutige Zeilen-ID; an `getConnection(id)` übergeben, um eine einzelne Verbindung erneut abzurufen |+| `sichtbarkeit` | `'user'` (privat für ein Mitglied des Arbeitsbereichs) oder `'workspace'` (mit allen Mitgliedern geteilt) |+| `geltungsbereiche` | Vom Upstream-Anbieter gewährte OAuth-Berechtigungen (unabhängig von `visibility` — diese sind nicht miteinander verknüpft) |+| `userWorkspaceId` | Die userWorkspace-ID des Eigentümers — nützlich, um "die Verbindung des anfragenden Benutzers" in HTTP-Routen-Triggern auszuwählen |+| `accessToken` | Frisches OAuth-Zugriffstoken (wird bei Ablauf automatisch erneuert) |+| `name` / `handle` | Anzeigename der Verbindung (automatisch beim OAuth-Callback abgeleitet, vom Benutzer umbenennbar) |+| `authFailedAt` | Gesetzt, wenn die jüngste Aktualisierung fehlgeschlagen ist; der Benutzer muss die Verbindung erneut herstellen |Hauptpunkte:-* Pass `{ providerName }` to filter by provider; omit it to get all connections this app owns across all providers.-* The server transparently refreshes the access token before returning. Your handler always sees a usable token (or `authFailedAt` set).-* `getConnection(id)` is the single-row equivalent.+* Übergeben Sie `{ providerName }`, um nach Anbieter zu filtern; lassen Sie es weg, um alle Verbindungen dieser App über alle Anbieter hinweg zu erhalten.+* Der Server aktualisiert das Zugriffstoken vor der Rückgabe transparent. Ihr Handler sieht stets ein verwendbares Token (oder `authFailedAt` ist gesetzt).+* `getConnection(id)` ist das Pendant für eine einzelne Zeile.</Accordion>-<Accordion title="Per-user vs workspace-shared visibility" description="How users choose between private and shared credentials">+<Accordion title="Sichtbarkeit: pro Benutzer vs. im Arbeitsbereich geteilt" description="Wie Benutzer zwischen privaten und geteilten Anmeldedaten wählen">-When a user clicks "Add connection," they're prompted to pick a visibility:+Wenn ein Benutzer auf "Verbindung hinzufügen" klickt, wird er aufgefordert, eine Sichtbarkeit auszuwählen:-* **Just for me** — the credential is private to the connecting user. Any logic function called on their behalf (HTTP-route trigger with `isAuthRequired: true`) sees it; cron triggers and database events do not.-* **Workspace shared** — any workspace member can use the credential. Cron / database triggers also see it, since they have no request user.+* **Nur für mich** — die Anmeldedaten sind für den sich verbindenden Benutzer privat. Jede Logikfunktion, die in seinem/ihrem Auftrag aufgerufen wird (HTTP-Routen-Trigger mit `isAuthRequired: true`), sieht sie; Cron-Trigger und Datenbankereignisse nicht.+* **Im Arbeitsbereich geteilt** — jedes Arbeitsbereichsmitglied kann die Anmeldedaten verwenden. Cron-/Datenbank-Trigger sehen sie ebenfalls, da sie keinen anfragenden Benutzer haben.-Use the right one for each handler:+Verwenden Sie für jeden Handler die richtige Option:```ts// HTTP-route trigger — prefer the request user's own connection.@@ -174,19 +174,19 @@ const conn =const conn = connections.find((c) => c.visibility === 'workspace');```-Multiple connections per (user, provider) are allowed, so the same user can hold "Personal Linear" and "Work Linear" side by side.+Mehrere Verbindungen pro (Benutzer, Anbieter) sind erlaubt, sodass derselbe Benutzer "Persönliches Linear" und "Arbeits-Linear" nebeneinander haben kann.</Accordion>-<Accordion title="One-time provider setup" description="Register your OAuth app with the third-party service">+<Accordion title="Einmalige Anbietereinrichtung" description="Registrieren Sie Ihre OAuth-App beim Drittanbieterdienst">-For each connection provider, the server admin needs to register an OAuth app at the third party first.+Für jeden Verbindungsanbieter muss der Serveradministrator zunächst eine OAuth-App beim Drittanbieter registrieren.-1. Go to the provider's developer settings (e.g. https://linear.app/settings/api/applications/new).-2. Set the **Redirect URI** to `\<SERVER_URL>/apps/oauth/callback`.-3. Copy the generated **Client ID** and **Client Secret**.-4. Open the installed app in Twenty as a server admin → set the values on the corresponding `serverVariables`.-5. Workspace members can then add connections from the per-app **Connections** section.+1. Gehen Sie zu den Entwickler-Einstellungen des Anbieters (z. B. https://linear.app/settings/api/applications/new).+2. Setzen Sie die **Redirect-URI** auf `\<SERVER_URL>/apps/oauth/callback`.+3. Kopieren Sie die generierte **Client ID** und das **Client Secret**.+4. Öffnen Sie die installierte App in Twenty als Serveradministrator → setzen Sie die Werte in den entsprechenden `serverVariables`.+5. Mitglieder des Arbeitsbereichs können dann Verbindungen im **Verbindungen**-Abschnitt der jeweiligen App hinzufügen.</Accordion>diff --git a/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdxindex 49cf549b48c..0b94b01f2f2 100644--- a/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-Der Dev-Modus ist nur auf Twenty-Instanzen verfügbar, die im Entwicklungsmodus laufen (`NODE_ENV=development`). Produktionsinstanzen lehnen Dev-Synchronisierungsanfragen ab. Verwenden Sie `yarn twenty deploy`, um auf Produktionsservern bereitzustellen — Details finden Sie unter [Apps veröffentlichen](/l/de/developers/extend/apps/publishing).+Der Dev-Modus ist nur auf Twenty-Instanzen verfügbar, die im Entwicklungsmodus laufen (`NODE_ENV=development`). Produktionsinstanzen lehnen Dev-Synchronisierungsanfragen ab. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/de/developers/extend/apps/publishing) for details.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdxindex 9c739c4d85c..e3af17be6aa 100644--- a/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdx+++ b/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdx@@ -77,9 +77,9 @@ Pre-Release-Tags funktionieren wie erwartet: Das Erhöhen von `1.0.0-rc.1` → `{/* TODO: add screenshot of the Upgrade button */}-### Server version compatibility+### Kompatibilität der Serverversionen-If your app uses a feature introduced in a specific Twenty server version (for example, OAuth providers added in v2.3.0), you should declare the minimum server version your app requires using the `engines.twenty` field in `package.json`:+Wenn Ihre App eine Funktion verwendet, die in einer bestimmten Twenty-Serverversion eingeführt wurde (z. B. OAuth-Anbieter, die in v2.3.0 hinzugefügt wurden), sollten Sie die minimale Serverversion, die Ihre App benötigt, mithilfe des Felds `engines.twenty` in `package.json` angeben:```json filename="package.json"{@@ -92,22 +92,22 @@ If your app uses a feature introduced in a specific Twenty server version (for e}```-The value is a standard [semver range](https://github.com/npm/node-semver#ranges). Common patterns:+Der Wert ist ein standardmäßiger [semver-Bereich](https://github.com/npm/node-semver#ranges). Häufige Muster:-| Range | Meaning |-| ---------------------------------- | ------------------------------------------ |-| `>=2.3.0` | Any server from 2.3.0 onward |-| `>=2.3.0 \<3.0.0` | 2.3.0 or later, but below the next major |-| `^2.3.0` | Same as `>=2.3.0 \<3.0.0` |+| Bereich | Bedeutung |+| ---------------------------------- | ------------------------------------------------------ |+| `>=2.3.0` | Jeder Server ab 2.3.0 |+| `>=2.3.0 \<3.0.0` | 2.3.0 oder höher, aber unter der nächsten Hauptversion |+| `^2.3.0` | Entspricht `>=2.3.0 \<3.0.0` |-**What happens at deploy and install time:**+**Was bei Bereitstellung und Installation passiert:**-* If `engines.twenty` is set and the target server's version does not satisfy the range, the deploy (tarball upload) or install is rejected with a `SERVER_VERSION_INCOMPATIBLE` error and a message indicating both the required range and the actual server version.-* If `engines.twenty` is **not set**, the app is accepted on any server version (backward-compatible with existing apps).-* If the server has no `APP_VERSION` configured, the check is skipped.+* Wenn `engines.twenty` gesetzt ist und die Version des Zielservers den Bereich nicht erfüllt, wird die Bereitstellung (Tarball-Upload) oder Installation mit dem Fehler `SERVER_VERSION_INCOMPATIBLE` abgelehnt, zusammen mit einer Meldung, die sowohl den erforderlichen Bereich als auch die tatsächliche Serverversion angibt.+* Wenn `engines.twenty` nicht gesetzt ist, wird die App auf jeder Serverversion akzeptiert (abwärtskompatibel mit bestehenden Apps).+* Wenn auf dem Server keine `APP_VERSION` konfiguriert ist, wird die Prüfung übersprungen.<Note>-The server is the authoritative check — it validates `engines.twenty` on both tarball upload and workspace install. If you deploy a tarball out-of-band or install from the marketplace, the server still enforces compatibility.+Der Server ist die maßgebliche Prüfinstanz — er validiert `engines.twenty` sowohl beim Tarball-Upload als auch bei der Workspace-Installation. Auch wenn Sie ein Tarball außerhalb des regulären Prozesses bereitstellen oder aus dem Marketplace installieren, erzwingt der Server weiterhin die Kompatibilität.</Note>## Automatisiertes CI/CD (vorgefertigte Workflows)diff --git a/packages/twenty-docs/l/pt/developers/extend/apps/connections.mdx b/packages/twenty-docs/l/pt/developers/extend/apps/connections.mdxindex e46666c0c22..02112ac98fb 100644--- a/packages/twenty-docs/l/pt/developers/extend/apps/connections.mdx+++ b/packages/twenty-docs/l/pt/developers/extend/apps/connections.mdx@@ -1,20 +1,20 @@----title: Connections-description: Let your app act on a user's behalf in third-party services via OAuth.+title: Conexões+description: Permita que seu aplicativo aja em nome de um usuário em serviços de terceiros via OAuth.icon: plug----Connections are credentials a user holds for an external service (Linear, GitHub, Slack, ...). Your app declares **how** those credentials are obtained — a **connection provider** — and consumes them at runtime to make authenticated calls to the third-party API.+Conexões são credenciais que um usuário mantém para um serviço externo (Linear, GitHub, Slack, ...). Seu app declara **como** essas credenciais são obtidas — um **provedor de conexão** — e as consome em tempo de execução para fazer chamadas autenticadas à API de terceiros.-Today only OAuth 2.0 is supported. Future credential types (personal access tokens, API keys, basic auth) will plug into the same surface — apps already using `defineConnectionProvider({ type: 'oauth', ... })` won't need to migrate.+Atualmente, apenas o OAuth 2.0 tem suporte. Tipos de credenciais futuros (tokens de acesso pessoal, chaves de API, autenticação básica) serão conectados à mesma interface — apps que já usam `defineConnectionProvider({ type: 'oauth', ... })` não precisarão migrar.<AccordionGroup>-<Accordion title="defineConnectionProvider" description="Declare how your app's connections are obtained">+<Accordion title="defineConnectionProvider" description="Declare como as conexões do seu app são obtidas">-A connection provider describes the OAuth handshake your app needs. The user clicks "Add connection" in your app's settings, completes the provider's consent screen, and a `ConnectedAccount` row is created in their workspace.+Um provedor de conexão descreve o handshake OAuth de que seu app precisa. O usuário clica em "Adicionar conexão" nas configurações do seu app, conclui a tela de consentimento do provedor e uma linha `ConnectedAccount` é criada no seu workspace.-A working setup needs **two files** — the connection provider, and a matching `serverVariables` declaration on `defineApplication` that holds the OAuth client credentials.+Uma configuração funcional precisa de **dois arquivos** — o provedor de conexão e uma declaração correspondente de `serverVariables` em `defineApplication` que contém as credenciais do cliente OAuth.```ts src/connection-providers/linear-connection.tsimport { defineConnectionProvider } from 'twenty-sdk/define';@@ -73,14 +73,14 @@ export default defineApplication({Pontos-chave:-* `name` is the unique identifier string used in `listConnections({ providerName })` (kebab-case, must match `^[a-z][a-z0-9-]*$`).-* `displayName` shows in the per-app settings tab and in the AI tool list.-* `clientIdVariable` / `clientSecretVariable` are **names**, not values — they must match keys declared in `defineApplication.serverVariables`. The actual `client_id` and `client_secret` are entered by the server admin through the app registration UI, never committed to your repo.-* Use `serverVariables` (not `applicationVariables`) — OAuth credentials are server-wide and one OAuth app per Twenty server.-* Until both `serverVariables` are filled in, the per-app settings tab shows a "needs server admin" hint and the "Add connection" button is disabled.-* `type: 'oauth'` is the only supported value today. The discriminator is forward-compatible: future types (`'pat'`, `'api-key'`, ...) will add new sub-config blocks alongside `oauth`.+* `name` é a string de identificador exclusivo usada em `listConnections({ providerName })` (kebab-case, deve corresponder a `^[a-z][a-z0-9-]*$`).+* `displayName` aparece na aba de configurações do app e na lista de ferramentas de IA.+* `clientIdVariable` / `clientSecretVariable` são **nomes**, não valores — devem corresponder às chaves declaradas em `defineApplication.serverVariables`. Os `client_id` e `client_secret` reais são inseridos pelo administrador do servidor por meio da interface de registro do app e nunca são versionados no seu repositório.+* Use `serverVariables` (não `applicationVariables`) — as credenciais OAuth são do servidor como um todo e há um app OAuth por servidor do Twenty.+* Até que ambos os `serverVariables` sejam preenchidos, a aba de configurações do app mostra uma dica "precisa de administrador do servidor" e o botão "Adicionar conexão" fica desativado.+* `type: 'oauth'` é o único valor compatível atualmente. O discriminador é compatível com versões futuras: tipos futuros (`'pat'`, `'api-key'`, ...) adicionarão novos blocos de subconfiguração ao lado de `oauth`.-The OAuth callback URL your provider needs to whitelist is:+O URL de callback do OAuth que seu provedor precisa adicionar à lista de permissões é:```https://<your-twenty-server>/apps/oauth/callback@@ -88,9 +88,9 @@ https://<your-twenty-server>/apps/oauth/callback</Accordion>-<Accordion title="listConnections / getConnection" description="Use connections from a logic function">+<Accordion title="listConnections / getConnection" description="Use conexões a partir de uma função de lógica">-Inside a logic function handler, `listConnections({ providerName })` returns this app's `ConnectedAccount` rows for the given provider, with refreshed access tokens.+Dentro de um handler de função de lógica, `listConnections({ providerName })` retorna as linhas `ConnectedAccount` deste app para o provedor fornecido, com tokens de acesso atualizados.```ts src/logic-functions/handlers/create-linear-issue-handler.tsimport { listConnections } from 'twenty-sdk/logic-function';@@ -135,34 +135,34 @@ export const createLinearIssueHandler = async (input: {};```-Each connection has:+Cada conexão tem:-| Campo | Descrição |-| ----------------- | -------------------------------------------------------------------------------------------------------- |-| `id` | Unique row id; pass to `getConnection(id)` to refetch a single one |-| `visibilidade` | `'user'` (private to one workspace member) or `'workspace'` (shared with all members) |-| `escopos` | OAuth permissions granted by the upstream provider (distinct from `visibility` — those are unrelated) |-| `userWorkspaceId` | The owner's userWorkspace id — useful for picking "the request user's connection" in HTTP-route triggers |-| `accessToken` | Fresh OAuth access token (refreshed automatically if expired) |-| `name` / `handle` | The connection's display name (auto-derived at OAuth callback, user-renameable) |-| `authFailedAt` | Set when the most recent refresh failed; the user must reconnect |+| Campo | Descrição |+| ----------------- | -------------------------------------------------------------------------------------------------------------------------- |+| `id` | ID de linha exclusivo; passe para `getConnection(id)` para buscar novamente um único registro |+| `visibilidade` | `'user'` (privada para um membro do workspace) ou `'workspace'` (compartilhada com todos os membros) |+| `escopos` | Permissões OAuth concedidas pelo provedor de origem (distintas de `visibility` — não têm relação) |+| `userWorkspaceId` | O id de userWorkspace do proprietário — útil para selecionar "a conexão do usuário da requisição" em gatilhos de rota HTTP |+| `accessToken` | Token de acesso OAuth recente (atualizado automaticamente se estiver expirado) |+| `name` / `handle` | O nome de exibição da conexão (derivado automaticamente no callback do OAuth, renomeável pelo usuário) |+| `authFailedAt` | Definido quando a atualização mais recente falhou; o usuário deve reconectar |Pontos-chave:-* Pass `{ providerName }` to filter by provider; omit it to get all connections this app owns across all providers.-* The server transparently refreshes the access token before returning. Your handler always sees a usable token (or `authFailedAt` set).-* `getConnection(id)` is the single-row equivalent.+* Passe `{ providerName }` para filtrar por provedor; omita para obter todas as conexões que este app possui em todos os provedores.+* O servidor atualiza transparentemente o token de acesso antes de retornar. Seu handler sempre vê um token utilizável (ou `authFailedAt` definido).+* `getConnection(id)` é o equivalente de uma única linha.</Accordion>-<Accordion title="Per-user vs workspace-shared visibility" description="How users choose between private and shared credentials">+<Accordion title="Visibilidade por usuário vs. compartilhada no workspace" description="Como os usuários escolhem entre credenciais privadas e compartilhadas">-When a user clicks "Add connection," they're prompted to pick a visibility:+Quando um usuário clica em "Adicionar conexão", é solicitado que escolha uma visibilidade:-* **Just for me** — the credential is private to the connecting user. Any logic function called on their behalf (HTTP-route trigger with `isAuthRequired: true`) sees it; cron triggers and database events do not.-* **Workspace shared** — any workspace member can use the credential. Cron / database triggers also see it, since they have no request user.+* **Apenas para mim** — a credencial é privada para o usuário que a conectou. Qualquer função de lógica chamada em seu nome (gatilho de rota HTTP com `isAuthRequired: true`) a vê; gatilhos cron e eventos de banco de dados não.+* **Compartilhada no workspace** — qualquer membro do workspace pode usar a credencial. Gatilhos de cron / banco de dados também a veem, pois não há um usuário da requisição.-Use the right one for each handler:+Use a adequada para cada handler:```ts// HTTP-route trigger — prefer the request user's own connection.@@ -174,19 +174,19 @@ const conn =const conn = connections.find((c) => c.visibility === 'workspace');```-Multiple connections per (user, provider) are allowed, so the same user can hold "Personal Linear" and "Work Linear" side by side.+Várias conexões por (usuário, provedor) são permitidas, então o mesmo usuário pode manter "Linear pessoal" e "Linear de trabalho" lado a lado.</Accordion>-<Accordion title="One-time provider setup" description="Register your OAuth app with the third-party service">+<Accordion title="Configuração única do provedor" description="Registre seu app OAuth no serviço de terceiros">-For each connection provider, the server admin needs to register an OAuth app at the third party first.+Para cada provedor de conexão, o administrador do servidor precisa primeiro registrar um app OAuth no serviço de terceiros.-1. Go to the provider's developer settings (e.g. https://linear.app/settings/api/applications/new).-2. Set the **Redirect URI** to `\<SERVER_URL>/apps/oauth/callback`.-3. Copy the generated **Client ID** and **Client Secret**.-4. Open the installed app in Twenty as a server admin → set the values on the corresponding `serverVariables`.-5. Workspace members can then add connections from the per-app **Connections** section.+1. Acesse as configurações de desenvolvedor do provedor (por exemplo, https://linear.app/settings/api/applications/new).+2. Defina a **URI de redirecionamento** como `\<SERVER_URL>/apps/oauth/callback`.+3. Copie o **ID do cliente** e o **Segredo do cliente** gerados.+4. Abra o app instalado no Twenty como administrador do servidor → defina os valores nos `serverVariables` correspondentes.+5. Os membros do workspace podem então adicionar conexões na seção **Conexões** de cada app.</Accordion>diff --git a/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdxindex ca815e81e60..63533932815 100644--- a/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-O modo de desenvolvimento só está disponível em instâncias do Twenty em modo de desenvolvimento (`NODE_ENV=development`). Instâncias de produção rejeitam solicitações de sincronização de desenvolvimento. Use `yarn twenty deploy` para fazer o deploy em servidores de produção — veja [Publicando aplicativos](/l/pt/developers/extend/apps/publishing) para detalhes.+O modo de desenvolvimento só está disponível em instâncias do Twenty em modo de desenvolvimento (`NODE_ENV=development`). Instâncias de produção rejeitam solicitações de sincronização de desenvolvimento. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/pt/developers/extend/apps/publishing) for details.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdxindex 3ad6233f947..7789056df32 100644--- a/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdx+++ b/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdx@@ -77,9 +77,9 @@ Tags de pré-lançamento funcionam como esperado: incrementar `1.0.0-rc.1` → `{/* TODO: add screenshot of the Upgrade button */}-### Server version compatibility+### Compatibilidade da versão do servidor-If your app uses a feature introduced in a specific Twenty server version (for example, OAuth providers added in v2.3.0), you should declare the minimum server version your app requires using the `engines.twenty` field in `package.json`:+Se o seu aplicativo usar um recurso introduzido em uma versão específica do servidor Twenty (por exemplo, provedores OAuth adicionados na v2.3.0), você deve declarar a versão mínima do servidor que seu aplicativo requer usando o campo `engines.twenty` em `package.json`:```json filename="package.json"{@@ -92,22 +92,22 @@ If your app uses a feature introduced in a specific Twenty server version (for e}```-The value is a standard [semver range](https://github.com/npm/node-semver#ranges). Common patterns:+O valor é um [intervalo semver](https://github.com/npm/node-semver#ranges) padrão. Padrões comuns:-| Range | Meaning |-| ---------------------------------- | ------------------------------------------ |-| `>=2.3.0` | Any server from 2.3.0 onward |-| `>=2.3.0 \<3.0.0` | 2.3.0 or later, but below the next major |-| `^2.3.0` | Same as `>=2.3.0 \<3.0.0` |+| Intervalo | Significado |+| ---------------------------------- | ---------------------------------------------------------- |+| `>=2.3.0` | Qualquer servidor a partir de 2.3.0 |+| `>=2.3.0 \<3.0.0` | 2.3.0 ou posterior, mas abaixo da próxima versão principal |+| `^2.3.0` | O mesmo que `>=2.3.0 \<3.0.0` |-**What happens at deploy and install time:**+**O que acontece no momento da implantação e da instalação:**-* If `engines.twenty` is set and the target server's version does not satisfy the range, the deploy (tarball upload) or install is rejected with a `SERVER_VERSION_INCOMPATIBLE` error and a message indicating both the required range and the actual server version.-* If `engines.twenty` is **not set**, the app is accepted on any server version (backward-compatible with existing apps).-* If the server has no `APP_VERSION` configured, the check is skipped.+* Se `engines.twenty` estiver definido e a versão do servidor de destino não satisfizer o intervalo, a implantação (upload do tarball) ou a instalação será rejeitada com o erro `SERVER_VERSION_INCOMPATIBLE` e uma mensagem indicando tanto o intervalo exigido quanto a versão real do servidor.+* Se `engines.twenty` **não estiver definido**, o aplicativo é aceito em qualquer versão do servidor (retrocompatível com os aplicativos existentes).+* Se o servidor não tiver `APP_VERSION` configurado, a verificação será ignorada.<Note>-The server is the authoritative check — it validates `engines.twenty` on both tarball upload and workspace install. If you deploy a tarball out-of-band or install from the marketplace, the server still enforces compatibility.+O servidor realiza a verificação definitiva — ele valida `engines.twenty` tanto no upload do tarball quanto na instalação no workspace. Se você implantar um tarball fora de banda ou instalar a partir do marketplace, o servidor ainda impõe a compatibilidade.</Note>## CI/CD automatizado (fluxos de trabalho pré-configurados)diff --git a/packages/twenty-docs/l/ru/developers/extend/apps/connections.mdx b/packages/twenty-docs/l/ru/developers/extend/apps/connections.mdxindex 2f026bf4eb3..728adb1cf6c 100644--- a/packages/twenty-docs/l/ru/developers/extend/apps/connections.mdx+++ b/packages/twenty-docs/l/ru/developers/extend/apps/connections.mdx@@ -1,20 +1,20 @@----title: Connections-description: Let your app act on a user's behalf in third-party services via OAuth.+title: Подключения+description: Разрешите вашему приложению действовать от имени пользователя в сторонних сервисах с помощью OAuth.icon: plug----Connections are credentials a user holds for an external service (Linear, GitHub, Slack, ...). Your app declares **how** those credentials are obtained — a **connection provider** — and consumes them at runtime to make authenticated calls to the third-party API.+Подключения — это учетные данные, которыми пользователь располагает для внешнего сервиса (Linear, GitHub, Slack, ...). Ваше приложение определяет, **как** получают эти учетные данные — через **провайдера подключения** — и использует их во время выполнения для выполнения аутентифицированных вызовов к стороннему API.-Today only OAuth 2.0 is supported. Future credential types (personal access tokens, API keys, basic auth) will plug into the same surface — apps already using `defineConnectionProvider({ type: 'oauth', ... })` won't need to migrate.+На данный момент поддерживается только OAuth 2.0. Будущие типы учетных данных (персональные токены доступа, ключи API, базовая аутентификация) будут подключаться к тому же интерфейсу — приложения, уже использующие `defineConnectionProvider({ type: 'oauth', ... })` не потребуют миграции.<AccordionGroup>-<Accordion title="defineConnectionProvider" description="Declare how your app's connections are obtained">+<Accordion title="defineConnectionProvider" description="Определите, как в вашем приложении получаются подключения">-A connection provider describes the OAuth handshake your app needs. The user clicks "Add connection" in your app's settings, completes the provider's consent screen, and a `ConnectedAccount` row is created in their workspace.+Провайдер подключения описывает процедуру OAuth-обмена, которая требуется вашему приложению. Пользователь нажимает "Добавить подключение" в настройках вашего приложения, подтверждает разрешения на экране согласия провайдера, и в его рабочем пространстве создается запись `ConnectedAccount`.-A working setup needs **two files** — the connection provider, and a matching `serverVariables` declaration on `defineApplication` that holds the OAuth client credentials.+Рабочей конфигурации нужны **два файла** — провайдер подключения и соответствующее объявление `serverVariables` в `defineApplication`, которое содержит учетные данные клиента OAuth.```ts src/connection-providers/linear-connection.tsimport { defineConnectionProvider } from 'twenty-sdk/define';@@ -73,14 +73,14 @@ export default defineApplication({Основные моменты:-* `name` is the unique identifier string used in `listConnections({ providerName })` (kebab-case, must match `^[a-z][a-z0-9-]*$`).-* `displayName` shows in the per-app settings tab and in the AI tool list.-* `clientIdVariable` / `clientSecretVariable` are **names**, not values — they must match keys declared in `defineApplication.serverVariables`. The actual `client_id` and `client_secret` are entered by the server admin through the app registration UI, never committed to your repo.-* Use `serverVariables` (not `applicationVariables`) — OAuth credentials are server-wide and one OAuth app per Twenty server.-* Until both `serverVariables` are filled in, the per-app settings tab shows a "needs server admin" hint and the "Add connection" button is disabled.-* `type: 'oauth'` is the only supported value today. The discriminator is forward-compatible: future types (`'pat'`, `'api-key'`, ...) will add new sub-config blocks alongside `oauth`.+* `name` — это уникальная строка-идентификатор, используемая в `listConnections({ providerName })` (kebab-case, должна соответствовать `^[a-z][a-z0-9-]*$`).+* `displayName` отображается на вкладке настроек приложения и в списке инструментов ИИ.+* `clientIdVariable` / `clientSecretVariable` — это **имена**, а не значения — они должны совпадать с ключами, объявленными в `defineApplication.serverVariables`. Фактические `client_id` и `client_secret` вводятся администратором сервера через интерфейс регистрации приложения и никогда не коммитятся в ваш репозиторий.+* Используйте `serverVariables` (не `applicationVariables`) — учетные данные OAuth являются общими для сервера, и на каждом сервере Twenty используется одно приложение OAuth.+* Пока оба `serverVariables` не заполнены, на вкладке настроек приложения показывается подсказка "нужен администратор сервера", а кнопка "Добавить подключение" отключена.+* `type: 'oauth'` — единственное поддерживаемое сегодня значение. Дискриминатор совместим с будущими версиями: будущие типы (`'pat'`, `'api-key'`, ...) добавят новые блоки подконфигурации рядом с `oauth`.-The OAuth callback URL your provider needs to whitelist is:+URL обратного вызова OAuth, который вашему провайдеру нужно добавить в список разрешенных:```https://<your-twenty-server>/apps/oauth/callback@@ -88,9 +88,9 @@ https://<your-twenty-server>/apps/oauth/callback</Accordion>-<Accordion title="listConnections / getConnection" description="Use connections from a logic function">+<Accordion title="listConnections / getConnection" description="Используйте подключения из логической функции">-Inside a logic function handler, `listConnections({ providerName })` returns this app's `ConnectedAccount` rows for the given provider, with refreshed access tokens.+Внутри обработчика логической функции `listConnections({ providerName })` возвращает записи `ConnectedAccount` этого приложения для указанного провайдера с обновленными токенами доступа.```ts src/logic-functions/handlers/create-linear-issue-handler.tsimport { listConnections } from 'twenty-sdk/logic-function';@@ -135,34 +135,34 @@ export const createLinearIssueHandler = async (input: {};```-Each connection has:+Каждое подключение имеет:-| Поле | Описание |-| ----------------- | -------------------------------------------------------------------------------------------------------- |-| `id` | Unique row id; pass to `getConnection(id)` to refetch a single one |-| `visibility` | `'user'` (private to one workspace member) or `'workspace'` (shared with all members) |-| `scopes` | OAuth permissions granted by the upstream provider (distinct from `visibility` — those are unrelated) |-| `userWorkspaceId` | The owner's userWorkspace id — useful for picking "the request user's connection" in HTTP-route triggers |-| `accessToken` | Fresh OAuth access token (refreshed automatically if expired) |-| `name` / `handle` | The connection's display name (auto-derived at OAuth callback, user-renameable) |-| `authFailedAt` | Set when the most recent refresh failed; the user must reconnect |+| Поле | Описание |+| ----------------- | --------------------------------------------------------------------------------------------------------------------------- |+| `id` | Уникальный идентификатор записи; передайте его в `getConnection(id)`, чтобы повторно получить одну запись |+| `visibility` | `'user'` (приватно для одного участника рабочего пространства) или `'workspace'` (доступно всем участникам) |+| `scopes` | Разрешения OAuth, предоставленные внешним провайдером (отличаются от `visibility` — это несвязанные вещи) |+| `userWorkspaceId` | Идентификатор userWorkspace владельца — полезно для выбора "подключения пользователя запроса" в триггерах HTTP-маршрутов |+| `accessToken` | Актуальный токен доступа OAuth (обновляется автоматически при истечении срока действия) |+| `name` / `handle` | Отображаемое имя подключения (автоматически определяется при обратном вызове OAuth, может быть переименовано пользователем) |+| `authFailedAt` | Устанавливается, если последняя попытка обновления не удалась; пользователю нужно переподключиться |Основные моменты:-* Pass `{ providerName }` to filter by provider; omit it to get all connections this app owns across all providers.-* The server transparently refreshes the access token before returning. Your handler always sees a usable token (or `authFailedAt` set).-* `getConnection(id)` is the single-row equivalent.+* Передайте `{ providerName }`, чтобы отфильтровать по провайдеру; опустите, чтобы получить все подключения этого приложения у всех провайдеров.+* Сервер прозрачно обновляет токен доступа перед возвратом. Ваш обработчик всегда получает рабочий токен (или установлено `authFailedAt`).+* `getConnection(id)` — эквивалент для одной записи.</Accordion>-<Accordion title="Per-user vs workspace-shared visibility" description="How users choose between private and shared credentials">+<Accordion title="Индивидуальная и общая для рабочего пространства видимость" description="Как пользователи выбирают между приватными и общими учетными данными">-When a user clicks "Add connection," they're prompted to pick a visibility:+Когда пользователь нажимает "Добавить подключение", ему предлагается выбрать видимость:-* **Just for me** — the credential is private to the connecting user. Any logic function called on their behalf (HTTP-route trigger with `isAuthRequired: true`) sees it; cron triggers and database events do not.-* **Workspace shared** — any workspace member can use the credential. Cron / database triggers also see it, since they have no request user.+* **Только для меня** — учетные данные приватны для подключившегося пользователя. Любая логическая функция, вызываемая от его имени (триггер HTTP-маршрута с `isAuthRequired: true`), видит их; триггеры cron и события базы данных — нет.+* **Общее для рабочего пространства** — любой участник рабочего пространства может использовать эти учетные данные. Триггеры cron/базы данных также видят их, поскольку у них нет пользователя запроса.-Use the right one for each handler:+Используйте подходящий вариант для каждого обработчика:```ts// HTTP-route trigger — prefer the request user's own connection.@@ -174,19 +174,19 @@ const conn =const conn = connections.find((c) => c.visibility === 'workspace');```-Multiple connections per (user, provider) are allowed, so the same user can hold "Personal Linear" and "Work Linear" side by side.+Допускается несколько подключений на пару (пользователь, провайдер), поэтому один и тот же пользователь может иметь "Personal Linear" и "Work Linear" одновременно.</Accordion>-<Accordion title="One-time provider setup" description="Register your OAuth app with the third-party service">+<Accordion title="Единоразовая настройка провайдера" description="Зарегистрируйте свое приложение OAuth у стороннего сервиса">-For each connection provider, the server admin needs to register an OAuth app at the third party first.+Для каждого провайдера подключения администратору сервера сначала нужно зарегистрировать у стороннего сервиса приложение OAuth.-1. Go to the provider's developer settings (e.g. https://linear.app/settings/api/applications/new).-2. Set the **Redirect URI** to `\<SERVER_URL>/apps/oauth/callback`.-3. Copy the generated **Client ID** and **Client Secret**.-4. Open the installed app in Twenty as a server admin → set the values on the corresponding `serverVariables`.-5. Workspace members can then add connections from the per-app **Connections** section.+1. Перейдите в настройки разработчика провайдера (например, https://linear.app/settings/api/applications/new).+2. Установите **Redirect URI** в значение `\<SERVER_URL>/apps/oauth/callback`.+3. Скопируйте сгенерированные **Client ID** и **Client Secret**.+4. Откройте установленное приложение в Twenty под учетной записью администратора сервера → задайте значения в соответствующих `serverVariables`.+5. Затем участники рабочего пространства смогут добавлять подключения в разделе **Подключения** конкретного приложения.</Accordion>diff --git a/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdxindex c7edeb3ba34..833e42a42c5 100644--- a/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-Режим разработки доступен только на экземплярах Twenty, запущенных в режиме разработки (`NODE_ENV=development`). Экземпляры в продакшене отклоняют запросы синхронизации из режима разработки. Используйте `yarn twenty deploy` для развёртывания на продакшен-серверах — подробности см. в разделе [Публикация приложений](/l/ru/developers/extend/apps/publishing).+Режим разработки доступен только на экземплярах Twenty, запущенных в режиме разработки (`NODE_ENV=development`). Экземпляры в продакшене отклоняют запросы синхронизации из режима разработки. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/ru/developers/extend/apps/publishing) for details.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/tr/developers/extend/apps/connections.mdx b/packages/twenty-docs/l/tr/developers/extend/apps/connections.mdxindex d06594ae9cf..4ec47816355 100644--- a/packages/twenty-docs/l/tr/developers/extend/apps/connections.mdx+++ b/packages/twenty-docs/l/tr/developers/extend/apps/connections.mdx@@ -1,20 +1,20 @@----title: Connections-description: Let your app act on a user's behalf in third-party services via OAuth.+title: Bağlantılar+description: Uygulamanızın, OAuth aracılığıyla üçüncü taraf hizmetlerde kullanıcı adına işlem yapmasına izin verin.icon: plug----Connections are credentials a user holds for an external service (Linear, GitHub, Slack, ...). Your app declares **how** those credentials are obtained — a **connection provider** — and consumes them at runtime to make authenticated calls to the third-party API.+Bağlantılar, bir kullanıcının harici bir hizmet için (Linear, GitHub, Slack, ...) sahip olduğu kimlik bilgileridir. Uygulamanız bu kimlik bilgilerinin **nasıl** elde edildiğini — bir **bağlantı sağlayıcısı** — bildirir ve çalışma zamanında üçüncü taraf API'sine kimlik doğrulamalı çağrılar yapmak için bunları kullanır.-Today only OAuth 2.0 is supported. Future credential types (personal access tokens, API keys, basic auth) will plug into the same surface — apps already using `defineConnectionProvider({ type: 'oauth', ... })` won't need to migrate.+Bugün yalnızca OAuth 2.0 destekleniyor. Gelecekteki kimlik bilgisi türleri (kişisel erişim belirteçleri, API anahtarları, basic auth) aynı yüzeye bağlanacak — halihazırda `defineConnectionProvider({ type: 'oauth', ... })` kullanan uygulamaların geçiş yapması gerekmeyecek.<AccordionGroup>-<Accordion title="defineConnectionProvider" description="Declare how your app's connections are obtained">+<Accordion title="defineConnectionProvider" description="Uygulamanızın bağlantılarının nasıl elde edildiğini belirtin">-A connection provider describes the OAuth handshake your app needs. The user clicks "Add connection" in your app's settings, completes the provider's consent screen, and a `ConnectedAccount` row is created in their workspace.+Bir bağlantı sağlayıcısı, uygulamanızın ihtiyaç duyduğu OAuth el sıkışmasını açıklar. Kullanıcı, uygulamanızın ayarlarında "Bağlantı ekle"ye tıklar, sağlayıcının izin ekranını tamamlar ve çalışma alanında bir `ConnectedAccount` satırı oluşturulur.-A working setup needs **two files** — the connection provider, and a matching `serverVariables` declaration on `defineApplication` that holds the OAuth client credentials.+Çalışan bir kurulum **iki dosya** gerektirir — bağlantı sağlayıcısı ve OAuth istemci kimlik bilgilerini tutan `defineApplication` üzerindeki eşleşen bir `serverVariables` bildirimi.```ts src/connection-providers/linear-connection.tsimport { defineConnectionProvider } from 'twenty-sdk/define';@@ -73,14 +73,14 @@ export default defineApplication({Önemli noktalar:-* `name` is the unique identifier string used in `listConnections({ providerName })` (kebab-case, must match `^[a-z][a-z0-9-]*$`).-* `displayName` shows in the per-app settings tab and in the AI tool list.-* `clientIdVariable` / `clientSecretVariable` are **names**, not values — they must match keys declared in `defineApplication.serverVariables`. The actual `client_id` and `client_secret` are entered by the server admin through the app registration UI, never committed to your repo.-* Use `serverVariables` (not `applicationVariables`) — OAuth credentials are server-wide and one OAuth app per Twenty server.-* Until both `serverVariables` are filled in, the per-app settings tab shows a "needs server admin" hint and the "Add connection" button is disabled.-* `type: 'oauth'` is the only supported value today. The discriminator is forward-compatible: future types (`'pat'`, `'api-key'`, ...) will add new sub-config blocks alongside `oauth`.+* `name`, `listConnections({ providerName })` içinde kullanılan benzersiz tanımlayıcı dizedir (kebab-case, `^[a-z][a-z0-9-]*$` ile eşleşmelidir).+* `displayName` uygulama başına ayarlar sekmesinde ve Yapay Zeka araç listesinde gösterilir.+* `clientIdVariable` / `clientSecretVariable` değer değil, **isimdir** — `defineApplication.serverVariables` içinde bildirilen anahtarlarla eşleşmelidir. Gerçek `client_id` ve `client_secret`, sunucu yöneticisi tarafından uygulama kayıt arayüzü üzerinden girilir; deponuza asla commit edilmez.+* `serverVariables` kullanın (`applicationVariables` değil) — OAuth kimlik bilgileri sunucu genelidir ve her Twenty sunucusu için bir OAuth uygulaması vardır.+* Her iki `serverVariables` da doldurulana kadar, uygulama başına ayarlar sekmesi "sunucu yöneticisine ihtiyaç var" ipucunu gösterir ve "Bağlantı ekle" düğmesi devre dışı bırakılır.+* `type: 'oauth'` bugün desteklenen tek değerdir. Seçici ileriye dönük uyumludur: gelecekteki türler (`'pat'`, `'api-key'`, ...) `oauth` yanında yeni alt yapılandırma blokları eklenecektir.-The OAuth callback URL your provider needs to whitelist is:+Sağlayıcınızın beyaz listeye alması gereken OAuth geri çağrı URL'si şudur:```https://<your-twenty-server>/apps/oauth/callback@@ -88,9 +88,9 @@ https://<your-twenty-server>/apps/oauth/callback</Accordion>-<Accordion title="listConnections / getConnection" description="Use connections from a logic function">+<Accordion title="listConnections / getConnection" description="Bir mantık işlevinden bağlantıları kullanın">-Inside a logic function handler, `listConnections({ providerName })` returns this app's `ConnectedAccount` rows for the given provider, with refreshed access tokens.+Bir mantık işlevi işleyicisi içinde, `listConnections({ providerName })`, verilen sağlayıcı için bu uygulamanın `ConnectedAccount` satırlarını, yenilenmiş erişim belirteçleriyle döndürür.```ts src/logic-functions/handlers/create-linear-issue-handler.tsimport { listConnections } from 'twenty-sdk/logic-function';@@ -135,34 +135,34 @@ export const createLinearIssueHandler = async (input: {};```-Each connection has:+Her bağlantı şunlara sahiptir:-| Alan | Açıklama |-| ----------------- | -------------------------------------------------------------------------------------------------------- |-| `id` | Unique row id; pass to `getConnection(id)` to refetch a single one |-| `visibility` | `'user'` (private to one workspace member) or `'workspace'` (shared with all members) |-| `scopes` | OAuth permissions granted by the upstream provider (distinct from `visibility` — those are unrelated) |-| `userWorkspaceId` | The owner's userWorkspace id — useful for picking "the request user's connection" in HTTP-route triggers |-| `accessToken` | Fresh OAuth access token (refreshed automatically if expired) |-| `name` / `handle` | The connection's display name (auto-derived at OAuth callback, user-renameable) |-| `authFailedAt` | Set when the most recent refresh failed; the user must reconnect |+| Alan | Açıklama |+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------- |+| `id` | Tekil satır kimliği; tek bir tanesini yeniden getirmek için `getConnection(id)` işlevine iletin |+| `visibility` | `'user'` (bir çalışma alanı üyesine özel) veya `'workspace'` (tüm üyelerle paylaşılan) |+| `scopes` | Üst sağlayıcı tarafından verilen OAuth izinleri (`visibility` ile karıştırılmamalıdır — bunlar ilişkili değildir) |+| `userWorkspaceId` | Sahibinin userWorkspace kimliği — HTTP rota tetikleyicilerinde "istek kullanıcısının bağlantısını" seçmek için kullanışlıdır |+| `accessToken` | Yeni OAuth erişim belirteci (süresi dolmuşsa otomatik olarak yenilenir) |+| `name` / `handle` | Bağlantının görünen adı (OAuth geri çağrısında otomatik türetilir, kullanıcı tarafından yeniden adlandırılabilir) |+| `authFailedAt` | En son yenileme başarısız olduğunda ayarlanır; kullanıcı yeniden bağlanmalıdır |Önemli noktalar:-* Pass `{ providerName }` to filter by provider; omit it to get all connections this app owns across all providers.-* The server transparently refreshes the access token before returning. Your handler always sees a usable token (or `authFailedAt` set).-* `getConnection(id)` is the single-row equivalent.+* Sağlayıcıya göre filtrelemek için `{ providerName }` iletin; bu uygulamanın tüm sağlayıcılardaki tüm bağlantılarını almak için bunu atlayın.+* Sunucu, döndürmeden önce erişim belirtecini şeffaf bir şekilde yeniler. İşleyiciniz her zaman kullanılabilir bir belirteç görür (veya `authFailedAt` ayarlanmıştır).+* `getConnection(id)`, tek satırlık karşılığıdır.</Accordion>-<Accordion title="Per-user vs workspace-shared visibility" description="How users choose between private and shared credentials">+<Accordion title="Kullanıcıya özel ve çalışma alanı paylaşımlı görünürlük" description="Kullanıcıların özel ve paylaşılan kimlik bilgileri arasında nasıl seçim yaptığı">-When a user clicks "Add connection," they're prompted to pick a visibility:+Bir kullanıcı "Bağlantı ekle"ye tıkladığında, bir görünürlük seçmesi istenir:-* **Just for me** — the credential is private to the connecting user. Any logic function called on their behalf (HTTP-route trigger with `isAuthRequired: true`) sees it; cron triggers and database events do not.-* **Workspace shared** — any workspace member can use the credential. Cron / database triggers also see it, since they have no request user.+* **Yalnızca benim için** — kimlik bilgisi, bağlanan kullanıcıya özeldir. Adlarına çağrılan herhangi bir mantık işlevi (`isAuthRequired: true` ile HTTP rota tetikleyicisi) bunu görür; cron tetikleyicileri ve veritabanı olayları görmez.+* **Çalışma alanı paylaşımlı** — herhangi bir çalışma alanı üyesi bu kimlik bilgisini kullanabilir. Cron / veritabanı tetikleyicileri de görür, çünkü istek kullanıcısı yoktur.-Use the right one for each handler:+Her işleyici için doğru olanı kullanın:```ts// HTTP-route trigger — prefer the request user's own connection.@@ -174,19 +174,19 @@ const conn =const conn = connections.find((c) => c.visibility === 'workspace');```-Multiple connections per (user, provider) are allowed, so the same user can hold "Personal Linear" and "Work Linear" side by side.+Kullanıcı ve sağlayıcı başına birden çok bağlantıya izin verilir; böylece aynı kullanıcı "Personal Linear" ve "Work Linear" bağlantılarını yan yana tutabilir.</Accordion>-<Accordion title="One-time provider setup" description="Register your OAuth app with the third-party service">+<Accordion title="Tek seferlik sağlayıcı kurulumu" description="OAuth uygulamanızı üçüncü taraf hizmete kaydedin">-For each connection provider, the server admin needs to register an OAuth app at the third party first.+Her bağlantı sağlayıcısı için, sunucu yöneticisinin önce üçüncü tarafta bir OAuth uygulaması kaydetmesi gerekir.-1. Go to the provider's developer settings (e.g. https://linear.app/settings/api/applications/new).-2. Set the **Redirect URI** to `\<SERVER_URL>/apps/oauth/callback`.-3. Copy the generated **Client ID** and **Client Secret**.-4. Open the installed app in Twenty as a server admin → set the values on the corresponding `serverVariables`.-5. Workspace members can then add connections from the per-app **Connections** section.+1. Sağlayıcının geliştirici ayarlarına gidin (örn. https://linear.app/settings/api/applications/new).+2. **Redirect URI**'yi `\<SERVER_URL>/apps/oauth/callback` olarak ayarlayın.+3. Oluşturulan **Client ID** ve **Client Secret**'ı kopyalayın.+4. Yüklü uygulamayı Twenty'de bir sunucu yöneticisi olarak açın → karşılık gelen `serverVariables` üzerinde değerleri ayarlayın.+5. Ardından çalışma alanı üyeleri, uygulama başına **Bağlantılar** bölümünden bağlantılar ekleyebilir.</Accordion>diff --git a/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdxindex eb0962d1e17..db572669bbf 100644--- a/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-Geliştirme modu yalnızca geliştirme ortamında (`NODE_ENV=development`) çalışan Twenty örneklerinde kullanılabilir. Üretim örnekleri geliştirme eşitleme isteklerini reddeder. Üretim sunucularına dağıtmak için `yarn twenty deploy` komutunu kullanın — ayrıntılar için [Uygulamaları Yayınlama](/l/tr/developers/extend/apps/publishing) bölümüne bakın.+Geliştirme modu yalnızca geliştirme ortamında (`NODE_ENV=development`) çalışan Twenty örneklerinde kullanılabilir. Üretim örnekleri geliştirme eşitleme isteklerini reddeder. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/tr/developers/extend/apps/publishing) for details.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/zh/developers/extend/apps/connections.mdx b/packages/twenty-docs/l/zh/developers/extend/apps/connections.mdxindex 2a44bbabfd0..114d1627b91 100644--- a/packages/twenty-docs/l/zh/developers/extend/apps/connections.mdx+++ b/packages/twenty-docs/l/zh/developers/extend/apps/connections.mdx@@ -1,20 +1,20 @@----title: Connections+title: 连接description: Let your app act on a user's behalf in third-party services via OAuth.icon: plug----Connections are credentials a user holds for an external service (Linear, GitHub, Slack, ...). Your app declares **how** those credentials are obtained — a **connection provider** — and consumes them at runtime to make authenticated calls to the third-party API.+连接是用户为外部服务(Linear、GitHub、Slack 等)持有的凭据。 你的应用声明**如何**获取这些凭据——即**连接提供程序**——并在运行时使用它们向第三方 API 发起认证调用。-Today only OAuth 2.0 is supported. Future credential types (personal access tokens, API keys, basic auth) will plug into the same surface — apps already using `defineConnectionProvider({ type: 'oauth', ... })` won't need to migrate.+目前仅支持 OAuth 2.0。 将来的凭据类型(个人访问令牌、API 密钥、基本身份验证)将接入相同的接口——已经使用 `defineConnectionProvider({ type: 'oauth', ... })` 的应用将无需迁移。<AccordionGroup>-<Accordion title="defineConnectionProvider" description="Declare how your app's connections are obtained">+<Accordion title="defineConnectionProvider" description="声明你的应用如何获取连接">-A connection provider describes the OAuth handshake your app needs. The user clicks "Add connection" in your app's settings, completes the provider's consent screen, and a `ConnectedAccount` row is created in their workspace.+连接提供程序描述了你的应用所需的 OAuth 握手流程。 用户在你的应用设置中点击"添加连接",完成提供方的授权同意页面后,会在其工作区中创建一条 `ConnectedAccount` 行。-A working setup needs **two files** — the connection provider, and a matching `serverVariables` declaration on `defineApplication` that holds the OAuth client credentials.+一个可用的配置需要**两个文件**——连接提供程序,以及在 `defineApplication` 上与之匹配、用于保存 OAuth 客户端凭据的 `serverVariables` 声明。```ts src/connection-providers/linear-connection.tsimport { defineConnectionProvider } from 'twenty-sdk/define';@@ -73,14 +73,14 @@ export default defineApplication({关键点:-* `name` is the unique identifier string used in `listConnections({ providerName })` (kebab-case, must match `^[a-z][a-z0-9-]*$`).-* `displayName` shows in the per-app settings tab and in the AI tool list.-* `clientIdVariable` / `clientSecretVariable` are **names**, not values — they must match keys declared in `defineApplication.serverVariables`. The actual `client_id` and `client_secret` are entered by the server admin through the app registration UI, never committed to your repo.-* Use `serverVariables` (not `applicationVariables`) — OAuth credentials are server-wide and one OAuth app per Twenty server.-* Until both `serverVariables` are filled in, the per-app settings tab shows a "needs server admin" hint and the "Add connection" button is disabled.-* `type: 'oauth'` is the only supported value today. The discriminator is forward-compatible: future types (`'pat'`, `'api-key'`, ...) will add new sub-config blocks alongside `oauth`.+* `name` 是在 `listConnections({ providerName })` 中使用的唯一标识符字符串(短横线命名(kebab-case),必须匹配 `^[a-z][a-z0-9-]*$`)。+* `displayName` 会显示在每个应用的设置选项卡以及 AI 工具列表中。+* `clientIdVariable` / `clientSecretVariable` 是**名称**,而不是值——它们必须与 `defineApplication.serverVariables` 中声明的键匹配。 实际的 `client_id` 和 `client_secret` 由服务器管理员通过应用注册 UI 输入,绝不会提交到你的仓库。+* 请使用 `serverVariables`(而非 `applicationVariables`)——OAuth 凭据是服务器范围的,并且每个 Twenty 服务器只配置一个 OAuth 应用。+* 在两个 `serverVariables` 都填写之前,每个应用的设置选项卡会显示"需要服务器管理员"的提示,并且"添加连接"按钮将被禁用。+* `type: 'oauth'` 是目前唯一受支持的取值。 该判别器具备前向兼容性:未来的类型(`'pat'`、`'api-key'` 等) 将会与 `oauth` 并列新增子配置块。-The OAuth callback URL your provider needs to whitelist is:+你的提供方需要加入白名单的 OAuth 回调 URL 为:```https://<your-twenty-server>/apps/oauth/callback@@ -88,9 +88,9 @@ https://<your-twenty-server>/apps/oauth/callback</Accordion>-<Accordion title="listConnections / getConnection" description="Use connections from a logic function">+<Accordion title="listConnections / getConnection" description="在逻辑函数中使用连接">-Inside a logic function handler, `listConnections({ providerName })` returns this app's `ConnectedAccount` rows for the given provider, with refreshed access tokens.+在逻辑函数处理器内,`listConnections({ providerName })` 会返回此应用针对给定提供方的 `ConnectedAccount` 行,并附带已刷新的访问令牌。```ts src/logic-functions/handlers/create-linear-issue-handler.tsimport { listConnections } from 'twenty-sdk/logic-function';@@ -135,34 +135,34 @@ export const createLinearIssueHandler = async (input: {};```-Each connection has:+每个连接包含:-| 字段 | 描述 |-| ----------------- | -------------------------------------------------------------------------------------------------------- |-| `id` | Unique row id; pass to `getConnection(id)` to refetch a single one |-| `可见性` | `'user'` (private to one workspace member) or `'workspace'` (shared with all members) |-| `范围` | OAuth permissions granted by the upstream provider (distinct from `visibility` — those are unrelated) |-| `userWorkspaceId` | The owner's userWorkspace id — useful for picking "the request user's connection" in HTTP-route triggers |-| `accessToken` | Fresh OAuth access token (refreshed automatically if expired) |-| `name` / `handle` | The connection's display name (auto-derived at OAuth callback, user-renameable) |-| `authFailedAt` | Set when the most recent refresh failed; the user must reconnect |+| 字段 | 描述 |+| ----------------- | ---------------------------------------------------- |+| `id` | 唯一的行 id;传给 `getConnection(id)` 以重新获取单个连接 |+| `可见性` | `'user'`(仅对单个工作区成员私有)或 `'workspace'`(与所有成员共享) |+| `范围` | 上游提供方授予的 OAuth 权限(不同于 `visibility`——两者不相关) |+| `userWorkspaceId` | 所有者的 userWorkspace id——在 HTTP 路由触发器中用于选择"请求用户的连接"很有用 |+| `accessToken` | 最新的 OAuth 访问令牌(若已过期会自动刷新) |+| `name` / `handle` | 连接的显示名称(在 OAuth 回调时自动生成,用户可重命名) |+| `authFailedAt` | 当最近一次刷新失败时会设置;用户必须重新连接 |关键点:-* Pass `{ providerName }` to filter by provider; omit it to get all connections this app owns across all providers.-* The server transparently refreshes the access token before returning. Your handler always sees a usable token (or `authFailedAt` set).-* `getConnection(id)` is the single-row equivalent.+* 传入 `{ providerName }` 以按提供方筛选;省略它则可获取此应用在所有提供方上的全部连接。+* 服务器会在返回前透明地刷新访问令牌。 你的处理器始终会拿到可用的令牌(或已设置 `authFailedAt`)。+* `getConnection(id)` 是获取单行记录的对应方法。</Accordion>-<Accordion title="Per-user vs workspace-shared visibility" description="How users choose between private and shared credentials">+<Accordion title="按用户与工作区共享的可见性" description="用户如何在私有与共享凭据之间进行选择">-When a user clicks "Add connection," they're prompted to pick a visibility:+当用户点击"添加连接"时,系统会提示其选择可见性:-* **Just for me** — the credential is private to the connecting user. Any logic function called on their behalf (HTTP-route trigger with `isAuthRequired: true`) sees it; cron triggers and database events do not.-* **Workspace shared** — any workspace member can use the credential. Cron / database triggers also see it, since they have no request user.+* **仅限我**——该凭据仅对连接的用户私有。 代表其调用的任何逻辑函数(带有 `isAuthRequired: true` 的 HTTP 路由触发器)都可以看到它;Cron 触发器和数据库事件则不可。+* **工作区共享**——任何工作区成员都可以使用该凭据。 Cron / 数据库触发器也可以使用它,因为它们没有请求用户。-Use the right one for each handler:+为每个处理器使用合适的类型:```ts// HTTP-route trigger — prefer the request user's own connection.@@ -174,19 +174,19 @@ const conn =const conn = connections.find((c) => c.visibility === 'workspace');```-Multiple connections per (user, provider) are allowed, so the same user can hold "Personal Linear" and "Work Linear" side by side.+每个(用户、提供方)允许有多个连接,因此同一用户可以同时拥有"个人 Linear"和"工作 Linear"。</Accordion>-<Accordion title="One-time provider setup" description="Register your OAuth app with the third-party service">+<Accordion title="一次性提供方设置" description="在第三方服务中注册你的 OAuth 应用">-For each connection provider, the server admin needs to register an OAuth app at the third party first.+对于每个连接提供方,服务器管理员需要先在第三方注册一个 OAuth 应用。-1. Go to the provider's developer settings (e.g. https://linear.app/settings/api/applications/new).-2. Set the **Redirect URI** to `\<SERVER_URL>/apps/oauth/callback`.-3. Copy the generated **Client ID** and **Client Secret**.-4. Open the installed app in Twenty as a server admin → set the values on the corresponding `serverVariables`.-5. Workspace members can then add connections from the per-app **Connections** section.+1. 前往提供方的开发者设置(例如 https://linear.app/settings/api/applications/new)。+2. 将**Redirect URI** 设置为 `\<SERVER_URL>/apps/oauth/callback`。+3. 复制生成的**Client ID**和**Client Secret**。+4. 以服务器管理员身份在 Twenty 中打开已安装的应用 → 在相应的 `serverVariables` 上设置这些值。+5. 之后,工作区成员可以在每个应用的**连接**部分添加连接。</Accordion>diff --git a/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdxindex b4ab89dddbe..c2f08510f08 100644--- a/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-开发模式仅适用于以开发模式运行的 Twenty 实例(`NODE_ENV=development`)。 生产实例会拒绝开发同步请求。 使用 `yarn twenty deploy` 部署到生产服务器——详见[发布应用](/l/zh/developers/extend/apps/publishing)。+开发模式仅适用于以开发模式运行的 Twenty 实例(`NODE_ENV=development`)。 生产实例会拒绝开发同步请求。 Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/zh/developers/extend/apps/publishing) for details.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/zh/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/zh/developers/extend/apps/publishing.mdxindex 317042578d7..e426ae6ded6 100644--- a/packages/twenty-docs/l/zh/developers/extend/apps/publishing.mdx+++ b/packages/twenty-docs/l/zh/developers/extend/apps/publishing.mdx@@ -77,9 +77,9 @@ yarn twenty deploy{/* TODO: add screenshot of the Upgrade button */}-### Server version compatibility+### 服务器版本兼容性-If your app uses a feature introduced in a specific Twenty server version (for example, OAuth providers added in v2.3.0), you should declare the minimum server version your app requires using the `engines.twenty` field in `package.json`:+如果你的应用使用了特定 Twenty 服务器版本中引入的功能(例如在 v2.3.0 中新增的 OAuth 提供方),应当在 `package.json` 的 `engines.twenty` 字段中声明应用所需的最低服务器版本:```json filename="package.json"{@@ -92,22 +92,22 @@ If your app uses a feature introduced in a specific Twenty server version (for e}```-The value is a standard [semver range](https://github.com/npm/node-semver#ranges). Common patterns:+该值是标准的 [semver 范围](https://github.com/npm/node-semver#ranges)。 常见模式:-| Range | Meaning |-| ---------------------------------- | ------------------------------------------ |-| `>=2.3.0` | Any server from 2.3.0 onward |-| `>=2.3.0 \<3.0.0` | 2.3.0 or later, but below the next major |-| `^2.3.0` | Same as `>=2.3.0 \<3.0.0` |+| 范围 | 含义 |+| ---------------------------------- | --------------------------------------- |+| `>=2.3.0` | 任何 2.3.0 及以上的服务器 |+| `>=2.3.0 \<3.0.0` | 2.3.0 或更高,但低于下一个主版本 |+| `^2.3.0` | 与 `>=2.3.0 \<3.0.0` 相同 |-**What happens at deploy and install time:**+**在部署和安装时会发生什么:**-* If `engines.twenty` is set and the target server's version does not satisfy the range, the deploy (tarball upload) or install is rejected with a `SERVER_VERSION_INCOMPATIBLE` error and a message indicating both the required range and the actual server version.-* If `engines.twenty` is **not set**, the app is accepted on any server version (backward-compatible with existing apps).-* If the server has no `APP_VERSION` configured, the check is skipped.+* 如果已设置 `engines.twenty`,且目标服务器的版本不满足该范围,则部署(tarball 上传)或安装将被拒绝,并返回 `SERVER_VERSION_INCOMPATIBLE` 错误以及一条同时指明所需范围和实际服务器版本的消息。+* 如果 `engines.twenty` **未设置**,则该应用可在任何服务器版本上被接受(与现有应用向后兼容)。+* 如果服务器未配置 `APP_VERSION`,则跳过该检查。<Note>-The server is the authoritative check — it validates `engines.twenty` on both tarball upload and workspace install. If you deploy a tarball out-of-band or install from the marketplace, the server still enforces compatibility.+服务器是权威校验方——它会在 tarball 上传和工作区安装时验证 `engines.twenty`。 即使你通过带外方式部署 tarball 或从应用市场安装,服务器仍会强制执行兼容性要求。</Note>## 自动化 CI/CD(脚手架生成的工作流)