Connected Apps

Bring your apps into the conversation.

Tell Rosi what you want to do. If a service needs access, Rosi gives you a secure connection link at that moment, so setup follows the task instead of the other way around.

Connected Apps in Rosi are powered by Composio.

You said:

Find the planning notes in Google Docs and summarize the open decisions.

Rosi

Google Docs needs to be connected before I can continue. Here is a secure Rosi link to review the access first.

The connection flow

Ask first. Connect only when needed.

The first link you see belongs to Rosi. It explains what comes next before sending you into the secure provider flow and, when applicable, the service’s consent screen.

  1. 01

    Start with the task

    Ask in natural language. Rosi searches the available capabilities and only asks for a connection when the task needs one.

  2. 02

    Open a Rosi link

    The Rosi page names the service, identifies Composio as the connection provider, and waits for you to choose Continue with Composio.

  3. 03

    Review and return

    Follow the service’s sign-in or credential steps. When a consent screen appears, review the requested access before approving it, then return to the conversation.

Breadth without setup sprawl

One conversation. A catalog of 1,000+ services.

Composio gives Rosi access to a broad service catalog without a separate Rosi-built connection for each app. Available actions and permissions vary by service, and authentication methods vary too.

  • Google Docs
  • Google Drive
  • Notion
  • Slack
  • ClickUp
  • LinkedIn
  • GitHub
  • Instagram
  • Supabase
  • Convex
  • and more

Clear roles

Rosi stays your assistant. Composio provides the connection.

Rosi

The conversation and task

Rosi understands what you asked, selects relevant capabilities, coordinates the work, and brings the result back to you.

Composio

Authentication and connectivity

Composio presents the connection flow, requests configured scopes when applicable, provides the implemented toolkit actions, and carries task-related requests and results. Where the method uses tokens, Composio holds and refreshes them.

The connected service

Permission and API rules

Google, Notion, Slack, or another service defines and enforces its sign-in, permission, and API model. For OAuth, the service shows the scopes requested by the connection configuration before you approve them.

Before you connect

A connection should never be a surprise.

You decide
You choose whether to continue. When the connection uses a consent screen, review the requested access before approving it.
What Rosi never sees
Rosi does not receive the password you enter at the service or the raw access token held by Composio.
What passes through
Task-related requests and results pass through Composio when Rosi uses a Connected App.
Disconnecting
Disconnecting removes the connection from Rosi and Composio; you can also revoke access directly in the service’s security settings.

Meet Rosi. Ask for what you need.

Request a free trial or subscribe, then install Rosi Agent. Connections appear in the conversation when they become useful.