Skip to content
OctodusDocs

Connectors

Yandex Disk

Your spaces' files and documents on your own Yandex Disk: what the agent can do, what access it gets, connecting and attaching to spaces, limits and errors.

Last updated:

On this page
  1. What the agent can do
  2. Access and on whose behalf
  3. How to connect
  4. Attaching to spaces
  5. Limits
  6. Troubleshooting

What the agent can do

  • List folders and files, create folders, upload and download files, move them and delete them (to the Disk trash).
  • Publish a file with a public link and unpublish it.
  • Create and edit .docx documents and .xlsx spreadsheets right on the Disk.
  • Work with Telemost recordings, which Yandex saves in the Telemost recordings folder.

Access and on whose behalf

The agent acts as the Yandex account you connected, with read, write and Disk info permissions. Access covers the whole Disk, not an app folder: Telemost recordings live outside app folders.

How to connect

  1. Open Integrations, Yandex Disk and click Connect Yandex Disk.
  2. Sign in to the right Yandex account and allow access without unticking any permission.
  3. Back in the dashboard, attach the Disk to spaces (see below). You can connect several Disks.

Attaching to spaces

  • By space: Attach a space on the Disk card. The dashboard asks you to confirm, naming the space.
  • Automatically: the Attach new spaces switch connects the Disk to new spaces from Bitrix24, Yandex Messenger and the API.
  • By integration: choose a shared Disk in the Yandex 360 organization console. Each of the organization's spaces works in its own folder under the root (/Octo by default) and cannot see the rest of the Disk.

Attaching by tag, and the general rules: Connecting services to spaces. An attached Disk turns on the Yandex Disk and documents capabilities for the space; the owner can turn them off.

Limits

  • One directly attached Disk per space.
  • Up to 32 MB per file transfer.
  • Detaching takes effect immediately and the files stay on the Disk. Disconnecting revokes the token at Yandex and removes all attachments.
  • The agent cannot delete the Disk root.

Troubleshooting

After signing in to Yandex: permissions are missing
A permission was unticked on the consent screen. Connect again and keep every permission.
"The space is already attached to another Disk"
Detach the space on that Disk's card first.
The Disk was connected with the old app-folder-only access
Reconnect it once; the attachments are kept.
The agent says the Disk needs a new sign-in
Yandex revoked access. Reconnect the same account on the Disk page.
"No Yandex Disk attached to this space"
The space owner attaches a Disk in the dashboard.