Kick destination
Runs official Kick API actions through the account’s connection: the webhook gateway by default, or a self-hosted Kick companion. Register a Kick account and sign in first. Works in standalone and Overwolf. With a companion in Overwolf, pair the companion before signing in or running actions.
Actions through the Stream Pulse-operated gateway require StreamPulse Pro, including connection tests. Self-hosted gateways and companions remain free. Expired Pro pauses managed actions without deleting saved destinations or rules.
- Under Connections > Destinations, add Kick and choose its sending account.
- Test connection, then save. The test verifies the gateway or companion sign-in; it does not send chat or prove moderation rights on another channel.
- Add a Kick action to a rule or Control board button. Select a target channel where offered; parameters accept templates.
| Action | Target | Parameters |
|---|---|---|
| Send chat message | Registered channel | Message, optional reply message ID |
| Delete chat message | Identified by message ID | Message ID |
| Ban or time out user | Registered channel | User ID, optional timeout in minutes |
| Unban user | Registered channel | User ID |
| Update stream title | Sending account’s own channel | Title |
Chat is sent as the signed-in user, not implicitly as Kick’s app bot.
Messages must fit Kick’s 500-character and 2048-byte limits. Leave the timeout
empty for a permanent ban. For event-driven moderation, use
and from the
Kick source.
Read-only accounts can identify target channels but cannot send actions. Account roles are labels, not permissions: Kick enforces the token’s scopes and actual broadcaster/moderator rights. API errors are shown in Activity. The gateway and companion only allow the listed actions, not arbitrary API requests. Actions are not retried automatically, and simulator dry run sends nothing. Gateway actions carry an idempotency key so a repeated request is not sent to Kick twice.