Notifications: Monitoring Events and Task Results

Notifications is the shared screen for ASO.dev results.

It contains events from Subscriptions, results from completed Tasks, and system messages. This screen does not start or configure monitoring. It shows what already happened.

100%

Notifications: Monitoring Events and Task Results

100%

Notifications: Monitoring Events and Task Results

Notifications can include:

• new continuous monitoring events
• completed tasks and reports
• downloadable files when a task creates an export
• app and country changes
• future event types

For example, if you run a one-time auction report, the result appears here when the task is complete. If an active subscription detects a new review, that event appears in the same feed.

The exact content depends on the event type, but a notification usually shows:

• app
• country
• event or task completion time
• event type
• result: report, review text, app positions, CSV file, or other available data

For tasks, a notification is often the entry point to the result. Open it to view the report or download the file.

Notifications can come from three sources:

• Subscriptions - continuous monitoring that checks for changes automatically.
• Tasks - one-time operations started manually and processed in the background.
• System updates - service messages from ASO.dev.

Use Subscriptions when you need recurring monitoring. Use Tasks when you need one report or export.

All results are available on this screen. This is the main place to view event history and open completed reports.

For memberships with access to the ASO analysis: Indie, Pro and Marketing

A push notification is sent when an event is detected or a task is complete. This is useful for background tasks: start a report and return to it after the notification arrives.

Available only for the Pro and Marketing memberships.

Webhooks are used for continuous monitoring events and are configured in Subscriptions. The format is suitable for automation and sending data to external systems.

Where to get a webhook URL for ASO.dev

In ASO.dev, paste a webhook URL into the webhook field. We will send subscription reports to that URL. Create this URL first in the service where you want to receive reports.

Start with direct integrations: Slack, Discord, Telegram, and Microsoft Teams.
For Telegram, create a bot with BotFather and use a Telegram Bot API URL. For the other services, create the webhook URL in the service settings.
If you need another tool, use Make, Zapier, n8n, or Pipedream as the middle step.

A webhook URL is usually a long HTTPS URL. It works like a secret delivery address for reports, so do not publish it publicly.

After pasting the URL into ASO.dev, click the test button to check that the report reaches the selected service.

Slack

Slack can generate a direct incoming webhook URL for a channel.

Where to get the URL:

1. Open the Slack App settings or create a new Slack app.
2. Enable Incoming Webhooks.
3. Click Add New Webhook to Workspace.
4. Choose the channel where reports should arrive.
5. Copy the URL that starts with https://hooks.slack.com/services/....
6. Paste this URL into ASO.dev and send a test.

If the test does not appear in the channel, use Make, Zapier, n8n, or Pipedream: copy the webhook URL from the automation tool, paste it into ASO.dev, then add a Slack message step.

Discord

Discord can generate a webhook URL for a specific channel.

Where to get the URL:

1. Open the server or channel settings. You need permission to manage webhooks.
2. Go to Integrations -> Webhooks.
3. Create a new webhook.
4. Choose the channel where reports should arrive.
5. Copy the webhook URL.
6. Paste this URL into ASO.dev and send a test.

If the test does not appear in the channel, use Make, Zapier, n8n, or Pipedream and send the report to Discord through a separate step.

Telegram

Telegram does not provide a simple webhook URL that you can copy from a chat or channel. For direct delivery, create a Telegram bot with @BotFather and use the Telegram Bot API URL.

Where to get the URL for ASO.dev:

1. Open @BotFather in Telegram and send /newbot.
2. Set the bot name and username, then copy the bot token.
3. Add the bot to the chat, group, or channel where reports should arrive. For a channel, make the bot an administrator.
4. Send any message in that chat, or press Start in a direct chat with the bot.
5. Open https://api.telegram.org/bot<BOT_TOKEN>/getUpdates and find the chat.id value. For a public channel, you can use @channel_username.
6. Build the Telegram Bot API URL: https://api.telegram.org/bot<BOT_TOKEN>/sendMessage?chat_id=<CHAT_ID>
7. Paste this URL into ASO.dev and send a test.

In ASO.dev, paste the Telegram Bot API URL.
Do not paste a t.me link, a separate bot token, or a URL from an automation service.
The URL contains the bot token, so keep it secret.

Microsoft Teams

For new setups, use Teams Workflows. Avoid choosing old Teams Connectors for new integrations.

Where to get the URL:

1. Open the target channel or chat in Teams.
2. Select More options -> Workflows.
3. Choose a webhook alerts template for a channel or chat.
4. Save the workflow.
5. Copy the webhook URL from the workflow page.
6. Paste this URL into ASO.dev and send a test.

If the report should look like a card or a message in a specific format, add formatting inside the Teams Workflow.

Integrations through Make, Zapier, n8n, or Pipedream

Use this option when the target service does not provide a ready webhook URL or when the report needs to be forwarded to another tool.

Where to get the URL for ASO.dev:

1. Create a new scenario, zap, or workflow in Make, Zapier, n8n, or Pipedream.
2. Choose an incoming webhook as the first step:
   • Make: Webhooks -> Custom webhook
   • Zapier: Webhooks by Zapier -> Catch Hook
   • n8n: Webhook
   • Pipedream: HTTP / Webhook
3. Copy the URL shown by the service.
4. Paste that URL into the subscription webhook channel in ASO.dev.
5. Send a test from ASO.dev.
6. After the test works, add the next step: send a message or save the report in the target service.

For n8n, use the test URL only while setting up the workflow. After enabling the workflow, paste the production URL into ASO.dev.

• open a completed task result
• download a CSV export
• check new reviews detected by a subscription
• see a monitoring state change
• jump from an event to an app, country, or report

API

We have started working on a public API.

If you have requirements for specific endpoints, send them to support@aso.dev.