Task Notifications

Receive result reminders after background scheduled tasks finish, through browser notifications or third-party channels.

Supported Channels

After enabling task notifications in Settings → General → Notifications, you can configure reminders for auto check-in, WebDAV auto sync, model sync, usage history sync, balance history capture, and site announcements.

Currently supported channels:

Channel	Best for	Required configuration
Browser system notifications	Receiving reminders on the current device	Browser `notifications` permission
Telegram Bot	Receiving reminders in a Telegram chat or group	Bot token and Chat ID
Feishu Bot	Receiving team reminders in a Feishu group	Feishu custom bot webhook URL or key
DingTalk Bot	Receiving team reminders in a DingTalk group	DingTalk custom bot webhook URL or access_token, optional signing secret
WeCom Bot	Receiving team reminders in a WeCom group	WeCom group message push webhook URL or key
ntfy	Receiving reminders through the ntfy app, a self-hosted ntfy server, or a subscribed topic	Topic URL or topic name, optional access token
Generic webhook	Connecting self-hosted services, automation platforms, or compatible services	An HTTP(S) endpoint that accepts JSON requests

After configuring a channel, click Send test notification to confirm delivery.

Feishu Bot

The Feishu channel sends plain-text messages through a Feishu group custom bot. The easiest setup is to paste the full webhook URL provided by Feishu.

Get The Webhook URL

Open the target Feishu group.
Add a custom bot from the group settings or bot entry.
Copy the webhook URL generated by Feishu. It usually looks like:

https://open.feishu.cn/open-apis/bot/v2/hook/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

In All API Hub, go to Settings → General → Notifications → Feishu Bot.
Paste the full webhook URL into Webhook URL or key, enable the channel, and click Send test notification.

If you copied only the key after /hook/, you can enter that too. All API Hub will complete the Feishu webhook URL automatically.

Security Settings

Feishu custom bots support keywords, IP whitelist, signature verification, and other security settings. For bot creation and security setup, refer to the Feishu custom bot guide.

When using All API Hub:

If keyword verification is enabled, make sure the notification title or body contains your configured keyword, such as All API Hub.
IP whitelist rules depend on your current network egress. Mobile networks, proxies, or home broadband changes may cause delivery failures.
The current Feishu channel only accepts a webhook URL or key and does not provide a separate signing secret field. If Feishu signature verification is enabled, test notifications may fail because no signature is sent.

Common Errors

Error	Possible cause	What to do
`param invalid: incoming webhook access token invalid`	The webhook URL or key is wrong, or the bot was deleted / recreated	Copy the full webhook URL again from the Feishu bot settings page
`Bad Request`	Feishu rejected the request body, commonly because bot security settings do not match	Check keywords, security settings, and whether the bot is still in the target group
Test notification does not arrive	The channel is disabled, the URL is empty, the network failed, or Feishu security policies blocked it	Enable the channel, send another test notification, and check the Feishu group bot configuration

DingTalk Bot

The DingTalk channel sends plain-text messages through a DingTalk group custom bot. The easiest setup is to paste the full webhook URL provided by DingTalk. If you copied only the value after access_token=, you can enter that too.

Create The Bot And Get The Webhook URL

Open the target DingTalk group.
Open group settings, choose Bots, and add a custom bot.
Configure the bot name and security settings. DingTalk supports custom keywords, signed requests, and IP address ranges.
After creating the bot, open its configuration page and copy the webhook URL. It usually looks like:

https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

In All API Hub, go to Settings → General → Notifications → DingTalk Bot.
Paste the full webhook URL into Webhook URL or access_token. If the DingTalk bot uses signed security, paste the generated SEC... value into Signing secret.
Enable the channel and click Send test notification.

Security Settings

When using All API Hub with DingTalk security settings:

If keyword verification is enabled, make sure the notification title or body contains your configured keyword, such as All API Hub.
If signed security is enabled, enter the SEC... secret from DingTalk. All API Hub generates a fresh timestamp and HMAC-SHA256 sign value for each request.
IP address range rules depend on your current network egress. Mobile networks, proxies, or home broadband changes may cause delivery failures.
Keep the webhook URL and signing secret private. Do not publish them in public repositories, public docs, or screenshots.

For DingTalk's official setup flow, see Create a custom bot, Custom bot security settings, and Get the custom bot webhook URL.

API Behavior

The DingTalk custom bot API sends messages through POST /robot/send?access_token=.... All API Hub sends a text message:

{
  "msgtype": "text",
  "text": {
    "content": "Notification title\nNotification content"
  },
  "at": {
    "isAtAll": false
  }
}

If a signing secret is configured, the request URL also includes timestamp and sign parameters. All API Hub treats errcode: 0 as success. If DingTalk returns another errcode, the test notification surfaces the returned errmsg to help you check the configuration.

Common Errors

Error	Possible cause	What to do
`keywords not in content` or a similar keyword error	Keyword verification is enabled, but the notification content does not contain the keyword	Adjust the DingTalk keyword, or make sure the notification title/body contains it
`sign not match` or a similar signing error	Signed security is enabled, but the secret is missing or wrong	Copy the `SEC...` secret again from the DingTalk bot settings page
`msgtype is null`	DingTalk did not parse the request body as a valid bot message	Update All API Hub to a version that sends the DingTalk text payload with `msgtype`, and send another test notification
`access_token` related errors	The webhook URL or access_token is wrong, or the bot was deleted / recreated	Copy the full webhook URL again from the DingTalk bot settings page
Test notification does not arrive	The channel is disabled, the URL is empty, the network failed, or DingTalk security policies blocked it	Enable the channel, send another test notification, and check the DingTalk group bot configuration

WeCom Bot

The WeCom channel sends plain-text messages through the message push configuration of a WeCom group. The easiest setup is to paste the full webhook URL provided by WeCom.

Get The Webhook URL

Open the target WeCom group.
Open group settings and find Message Push.
Create a new message push configuration, or open an existing one.
Copy the webhook URL generated by WeCom. It usually looks like:

https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

In All API Hub, go to Settings → General → Notifications → WeCom Bot.
Paste the full webhook URL into Webhook URL or key, enable the channel, and click Send test notification.

If you copied only the key after key=, you can enter that too. All API Hub will complete the WeCom webhook URL automatically.

API Behavior

The WeCom message push API sends messages through POST /cgi-bin/webhook/send?key=.... All API Hub sends a text message:

{
  "msgtype": "text",
  "text": {
    "content": "Notification title\nNotification content"
  }
}

All API Hub treats errcode: 0 as success. If WeCom returns another errcode, the test notification surfaces the returned errmsg to help you check the configuration.

Limits

Message formats and sending frequency limits follow the WeCom message push configuration docs.

When using All API Hub:

WeCom message push has sending frequency limits. If many tasks finish at the same time, platform rate limiting may apply.
If the test notification returns invalid webhook url, key not found, or a similar error, copy the full webhook URL again from the WeCom message push configuration.

ntfy

The ntfy channel sends plain-text notifications through ntfy's topic publish API. You can use the public ntfy.sh service or enter a topic URL from a self-hosted ntfy server.

Configure The Topic

Prepare a topic name in the ntfy app, web app, or your self-hosted server, such as all-api-hub-alerts.
In All API Hub, go to Settings → General → Notifications → ntfy.
Enter the full topic URL in Topic URL or topic name:

https://ntfy.sh/all-api-hub-alerts

You can also enter only the topic name:

all-api-hub-alerts

When only a topic name is entered, All API Hub sends to https://ntfy.sh/<topic>. For a self-hosted ntfy server, enter the full URL, for example:

https://ntfy.example.com/all-api-hub-alerts

If the topic requires authentication, enter the ntfy access token in Access token (optional). Leave it empty for public topics.
Enable the channel and click Send test notification.

API Behavior

All API Hub uses ntfy's publish API and sends a POST request to the topic URL. The notification body is sent as the plain-text request body, and the notification title is sent in the Title request header. Non-ASCII titles are RFC 2047 encoded before sending so they remain compatible with browser extension background request-header limits. If an access token is configured, the request includes Authorization: Bearer <token>.

For ntfy's publish API, request headers, and authentication options, see the official Publishing messages documentation.

Limits

Public ntfy.sh topics are not private namespaces. Use a hard-to-guess topic name, or use a self-hosted server with an access token.
If your self-hosted server uses private topics, confirm that the access token has publish permission.
If the test notification returns 401, 403, or a similar authentication error, check the topic URL, access token, and server-side permissions.