1. Install the ntfy app or open the web app, then choose Add subscription.
2. Keep the default server https://ntfy.sh unless you use a self-hosted server.
3. In Allimbot Settings, generate or enter an unguessable topic and copy it before saving.
4. Subscribe in ntfy using exactly the same server and topic. A private server may also require an access token.
5. Select ntfy, choose Save this channel, then use Channels → Send test and confirm the notification.

The topic acts like a password. Do not use a short or guessable name.

Not received? Compare both the server and topic character-for-character, allow phone notifications, and check whether a private server needs a token.

1. Use an account with Manage Webhooks permission and open Server Settings → Integrations → Webhooks.
2. Create a webhook, choose the destination text channel, and select Copy Webhook URL.
3. In Allimbot Settings, select Discord, paste the URL, and choose Save this channel.
4. Use Channels → Send test and confirm the message in the selected Discord channel.

Anyone with the webhook URL can post to the channel. Never share it.

Delivery failed? Confirm the webhook still exists and belongs to the intended channel. Create a new URL if it was deleted or exposed.

1. Create an app in Kakao Developers and copy its REST API key. If Client Secret is enabled, copy that value too.
2. Enable Kakao Login and register https://localhost as the Redirect URI exactly.
3. In Kakao Login → Consent Items, configure the KakaoTalk message permission (talk_message).
4. In Allimbot Settings, select KakaoTalk, enter the REST API key and optional Client Secret, then choose Save this channel.
5. Choose 1. Open authorization and consent. On the localhost error page, press Ctrl+L and copy only the value after code= from the address.
6. Paste that one-time code into Authorization code, choose 2. Complete authorization, then send a channel test.

No code? If the address contains error instead, review login consent and Redirect URI settings. If token issuance fails, open authorization again and use a fresh code.

1. Open @BotFather, run /newbot, and copy the bot token it issues.
2. Open a chat with the new bot, choose Start, and send it one message. For a group, add the bot and send a message in that group.
3. Enter the bot token in Allimbot Settings.
4. Choose Find Chat ID in the Telegram settings card.
5. Choose the matching conversation, enable Telegram, and save this channel.
6. Send a channel test, then send a reply and confirm both directions in Messenger.

The bot token controls the bot. Do not share the token or the getUpdates URL containing it.

getUpdates is empty? Send the bot another message and reload. For a group, make sure the bot is a member and the Chat ID includes a leading minus sign when shown.

1. Enable 2-Step Verification on the Google Account that will send the email.
2. Open Google Account → App passwords and create a dedicated app password for Allimbot.
3. In Allimbot Settings, enter the Gmail address and app password. Leave Recipient blank to send to the same Gmail address.
4. Select Gmail, choose Save this channel, send a test, and check Inbox and Spam.

Use an app password, not the Google Account password. Google may hide app passwords for managed or Advanced Protection accounts.

Password stopped working? Google revokes app passwords after an account password change; create and save a new one.

1. Get the SMTP host, STARTTLS port, username, and app-specific password from your mail provider.
2. In Allimbot Settings, enter the host and port (commonly 587) and keep STARTTLS set to true when required.
3. Enter an allowed From address and one or more recipient addresses separated by commas.
4. Select SMTP email, save this channel, send a test, and check Inbox and Spam.

This adapter supports SMTP with optional STARTTLS, not implicit TLS/SMTPS commonly used on port 465.

Authentication or relay error? Confirm the provider allows SMTP, use an app password when required, and make sure the From address is permitted for that account.

1. Create a fine-grained personal access token for the resource owner and target repository.
2. Grant the selected repository Issues permission with write access. Organization-owned repositories may require administrator approval.
3. In Allimbot Settings, enter the token and repository as owner/name. Keep https://api.github.com unless using GitHub Enterprise Server.
4. Select GitHub Issues, save this channel, and send a test. A new issue should appear in the repository.

Every Allimbot delivery creates a new issue. Use a dedicated repository or choose this channel only when issue creation is intended.

403 or 404? Check repository selection, Issues write permission, organization approval, and the exact owner/name spelling.

1. Create or open a Slack app for the destination workspace and enable Incoming Webhooks.
2. Choose Add New Webhook to Workspace, select the receiving channel, and approve access.
3. Copy the generated hooks.slack.com URL. In Allimbot Settings, select Slack, paste it, and save this channel.
4. Use Channels → Send test and confirm the message in the selected Slack channel.

The incoming webhook URL is a credential. Do not share it or commit it to Git.

403 or 404? The app may have lost channel access or the webhook may be revoked. Reinstall the app or create a new webhook.

1. Choose a Matrix account that is already joined to the destination room and is allowed to send messages.
2. From your homeserver or client's developer settings, obtain the homeserver base URL and an access token.
3. Open the room's advanced settings and copy its internal Room ID, which looks like !room:example.org.
4. In Allimbot Settings, enter all three values, select Matrix, save this channel, and send a test.

The access token grants account access. Use a dedicated account and an unencrypted room; this adapter does not implement Matrix end-to-end encryption.

401, 403, or 404? Check token validity, room membership and send permission, the internal Room ID, and the matching homeserver.