Skip to main content

Integrations

Integrations are the services your blocks can talk to. You manage them under Integrations in your app. Discord and Roblox are always enabled. Others, like Bloxlink, Roblox Open Cloud, Cookie API and ER:LC, need a key from your account with that service, which you enter when you enable them. Disabling one keeps its key, removing it deletes the key.

Before you enable one, Kite shows what its blocks send to the service, with links to its privacy policy and terms if it has them. Cookie API's transcript block also sends your bot's token, as Cookie API reads the channel's messages itself.

ER:LC only runs commands from apps the owner of the private server authorized. After you enter the server key, ER:LC has an Authorize Kite button, which opens ER:LC's page to do that. The ER:LC guide walks through setting it up and building commands for your server.

The key is stored encrypted and can't be read back. Kite sends it only to the service it belongs to, with the requests of that service's blocks, so the key is never part of a flow and can't be sent anywhere else by a flow you imported.

Blocks of an integration you haven't enabled still show in the block explorer, marked with Enable. If a flow has one, the block is marked red in the editor and fails when it runs, until you enable the integration.

Roblox Open Cloud​

The Roblox group blocks use an API key from Roblox's Creator Hub. Create it on the account that manages the group, as the key can only do what that account can:

  1. Open Credentials of your own account, not the group's, and create an API key.
  2. Under Access Permissions, add groups with the group:read and group:write permissions.
  3. Allow any IP address under Accepted IP Addresses by adding 0.0.0.0/0.
  4. Copy the key and enter it when you enable Roblox Open Cloud in Kite.