Skip to main content
Connect Discord from a Biqli workspace’s integration settings. The connection is permanently scoped to the Biqli workspace from which installation starts. No API key or bot token is pasted into Discord. During authorization, select one Discord server and one channel. Discord adds the /biqli application command to that server and creates a channel webhook for the optional activity notifications you select in Biqli.

​
Connect Discord

  1. Open the intended Biqli workspace and go to Settings → Integrations.
  2. Choose Discord, select Enable, and continue to Discord.
  3. Select the intended Discord server and notification channel.
  4. Approve application commands and webhook access.
  5. Back in Biqli, choose the default short domain and notification types.
  6. Save the settings and test /biqli in the Discord server.
Only the Biqli workspace owner can connect, change, or disconnect the integration. One Discord server can belong to only one Biqli workspace.

​
Commands

  • /biqli url:https://example.com creates a short link.
  • /biqli url:(launch) https://example.com creates a link with the launch alias.
  • /biqli url:clicks:launch shows the five most recent clicks for that link.
  • /biqli url:config shows the fixed Biqli workspace, default domain, and notification channel.
The command creates links in the connected Biqli workspace. Workspace and domain selection cannot be changed from Discord; the workspace owner controls them in Biqli.

​
Channel notifications

The workspace owner can independently enable notifications for link changes, clicks, leads, and sales. Biqli posts only the selected events to the channel chosen during Discord authorization. To move notifications to another channel, disconnect Discord in Biqli and connect it again, selecting the new channel during authorization.

​
Permissions and security

Biqli requests only applications.commands and webhook.incoming. The integration does not require a bot user, message history, channel management, thread management, or administrator permission. OAuth access tokens and the selected channel webhook are encrypted at rest.

​
Troubleshooting

If /biqli is missing, confirm that the app remains installed in the selected server and that application commands are allowed in the current channel. If a link uses the wrong domain, update the integration’s default domain in Biqli. Reconnect after a Discord administrator removes the app or webhook, when the notification channel needs to change, or when the Biqli workspace changes ownership.

​
Frequently asked questions

​
Does /biqli expose an API key?

No. Use only the official authorization flow. Never paste a workspace API key into a Discord command or channel.

​
Can anyone in the server use /biqli?

Anyone allowed to use the application command can create links in the connected Biqli workspace. Restrict command access with Discord’s server or channel permissions when needed. In the Biqli workspace that owns the Discord installation.