> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superun.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> Connect Feishu, Notion, and other platforms to find, read, and organize authorized work content in your conversations.

## What connectors do

Connectors let superun use external content you have authorized in a conversation. Read requirements, summarize meeting notes, or compare documents to support planning, consultation, and development.

The current scope is **searching, reading, and organizing content**. Writing, updating, or deleting content on external platforms is not currently offered through connectors.

<Info>
  Connectors provide content for your conversations with superun. Integrations in the Skill Library add capabilities such as login and messaging to the apps you build. Their purpose and authorization setup are different.
</Info>

## Platforms

| Platform | Account or content scope |
| - | - |
| Feishu | Authorized work content in Feishu |
| DingTalk | Authorized work content in the selected organization |
| WeCom | Work content the connected bot is permitted to access |
| Notion | Pages allowed within the authorized workspace |
| GitHub | GitHub resources covered by your authorization |
| WPS / KDocs | Content allowed on the WPS authorization page |
| Tencent Docs | Authorized online documents and spreadsheets |

Available platforms and readable content depend on the **My connectors** page and your platform permissions.

## Connect for the first time

<Steps>
  <Step title="Open connectors">
    Select **My connectors** from your avatar menu. You can also select **Use connectors** from the attachment menu in a home or project conversation to open the management panel.
  </Step>

  <Step title="Choose a platform and authorize">
    Click **Connect** and follow the QR-code or web authorization instructions. On first use, you may initially see “Preparing the connection…”.

    A first-time Feishu connection may involve two steps: creating a Feishu app, then authorizing your account. Complete them in order and wait for the next step to open automatically.
  </Step>

  <Step title="Check the connection">
    Return to superun and confirm that the connection is **Authorized** and enabled. Connections belong to your account and can be reused across projects without connecting again for each project.
  </Step>
</Steps>

## Use a connector in a conversation

In exploration, consultation, or development, specify **which platform to use, what content to read, and what to do with it**. A document link, clear title, or time range helps identify the content.

For example:

* “Read this Notion requirements document and summarize the target users, core workflows, and open questions: document link.”
* “Find this week's project meeting notes in Feishu, summarize decisions and action items, and list the sources.”
* “Compare these two authorized documents and identify requirement differences. Do not change the project code yet.”

After authorizing, you can continue in the same conversation. A new conversation is not required. When you need current content, explicitly ask to **read it again** rather than rely only on material from earlier messages.

## Manage connections

| Action | Effect |
| - | - |
| Turn on | Allow the connector to be used in conversations, provided authorization is valid |
| Turn off | Stop using it while retaining authorization; this setting applies across your projects |
| Reauthorize | Authorize again when access expires or the authorization scope needs to change |
| Disconnect | Remove the connection credentials stored by superun; using it again requires reconnecting |

Access uses the authorization of the user making the request. Joining a shared project does not automatically grant access to another member's external account.

## Troubleshooting

| Situation | What to do |
| - | - |
| The authorization window did not open | Use **Continue authorization** or **Open authorization page** as prompted, and allow the authorization popup |
| The connection stays in Authorizing | Complete the platform's steps and reopen the panel to check progress. Closing the panel does not cancel authorization; reconnect if the attempt expires |
| Authorized, but specific content cannot be read | Check the account, authorization scope, and access to that content. A successful connection does not grant access to everything |
| A Notion page cannot be read | Check that the target page was selected or permitted during authorization. Grant the required page access and retry |
| Authorization has expired | Reauthorize the affected platform, then request the read again in the same conversation |
| Results are incomplete | Follow the reported limitations, narrow the request or grant missing permissions, then request another read. Do not treat partial results as complete |

### DingTalk requires administrator access

Ask an administrator of the selected organization to open **DingTalk Developer Platform → More → Basic Information → CLI Settings**. Enable “Allow members to access personal data through CLI” and add your account under **Usage Scope Management**. Then reconnect in superun and select the same organization.

### WeCom is connected but cannot read existing documents

Ask the connected bot's creator to open **WeCom → Workbench → Smart Bots → the connected bot → Edit → Available Permissions → Documents**, then authorize **Search and retrieve document content**. Contact an enterprise administrator if approval is required.

Once permission is granted, request the read again in the same superun conversation. Disconnecting and reconnecting is not required first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.