Tavina

Connected apps overview

📖 This content is synced from the Tavina Handbook.
The canonical version always lives at https://tavina.ai/docs/friendly/connected-apps/overview

Connected apps overview

Connected apps let Tavina work with supported external services after you connect them. Depending on the app and the trust level you grant, Tavina may be able to read information, draft changes, or perform actions.

Only connect apps you want Tavina to use.

Google app links

Gmail, Google Drive, Google Docs, and Google Sheets are connected-app capabilities, not embedded Tavina work panels. Tavina can still help search, draft, create, edit, and organize those services when your connection and trust setting allow it. When there is something for you to view, Tavina should give you a link that opens the item in the real Google app.

Google Calendar is different: connected Google Calendar items can appear as an optional read-only source inside Tavina’s native Calendar when that source is enabled.

Important-email alerts

With Gmail connected, Tavina can watch for email that needs your attention and alert you. This is metadata-only: Tavina reads sender, subject, and labels — never email content — keeps triage history for at most seven days, and can only prepare drafts you review and send yourself; it never sends email on its own. You can teach it “never this” for mail like a given alert, and the learned rules are visible and removable. See Proactivity and proactive moments for the full posture and controls.

Trust levels

Trust settings define how much Tavina may do with a connected app. The exact actions available depend on the app, current product support, and your account permissions.

Use the lowest trust level that works for the task. Higher trust levels can be powerful and should be granted deliberately.

Trust level Customer expectation
Low trust Tavina should be limited and may need more confirmation or manual follow-up.
Medium trust Tavina may have enough access for common assisted workflows.
High trust Tavina may perform broader or more sensitive actions when supported. Use with care.
Maximum trust Tavina may perform the most sensitive supported actions for that app. Use only when you understand the warning and deliberately choose it.

If an action needs a higher trust level than you granted, Tavina should explain the required trust level instead of failing vaguely.

One boundary to understand: Tavina’s version-history recovery covers Tavina-owned tools. When Tavina deletes something inside a connected app at your request — an external calendar event, for example — that deletion happens in the external service and follows the app’s own recovery options, not Tavina’s (tavina/tavina#1957). That is part of what trust levels communicate: grant them with the connected app’s behavior in mind.

Review app actions

Before relying on a connected-app result, check:

  • which app Tavina used;
  • what action Tavina attempted;
  • whether Tavina reported success, failure, or a permission problem;
  • whether the app itself shows the expected result.

Privacy and sensitive data

Connected apps can expose sensitive information. Do not connect an app or grant a trust level unless you are comfortable with Tavina using the app for your requests.

Avoid asking Tavina to handle secrets, passwords, private keys, one-time codes, or payment details.

If a connected app fails

Common causes include an expired connection, insufficient trust level, unsupported action, app-side permission problem, temporary service issue, or a provider/model setting that no longer matches what the provider accepts.

Start with Connected app troubleshooting or Provider response troubleshooting if an app stops working.

BYOK provider fallback

Some Tavina accounts can connect their own AI provider key and choose a primary model. If your settings include a backup model, choose one from the same provider and key as the primary model. Tavina does not use this backup to switch to a different provider account.

Tavina tries the primary model first. If the provider still cannot complete the request after Tavina’s primary retry, Tavina may use the backup model and should tell you that fallback happened. Tavina should not use a backup model for authentication-style failures such as an expired, revoked, or unauthorized provider key.

If you often see provider fallback notices, check whether the primary model name is current and compatible with your provider key. Support may ask for the visible notice and the time it happened, but should not ask for the provider key itself.

Related pages

Scroll to Top