Notifications
The Notifications page and the bell list every alert in the workspace. Each one has its own page with the rows that matched and where it was sent. Plus browser notifications and "notify me when done".
Every alert that fires in a workspace is kept once, whatever its rule sends to. Jsonify calls this list Local Notifications, and you can read it in two places: the Notifications page and the bell at the top of every page. Each alert also has its own page, with the rows that matched and where it went. On top of rules, you can ask to be told when a specific run or a specific Jason task finishes.
The Notifications page
Open it from the bell’s View all link, or from View alerts on the Rules tab. Its address is /notifications/history.
Each row is one alert, in five columns:
| Column | What it shows |
|---|---|
| Notification | An icon for how it reads (red for a failed run or an urgent rule, amber for a cancelled run or a failed delivery, green for a completed run, blue otherwise), the title (“Pipeline run failed”, “Pipeline run cancelled”, or the rule’s name), a Test badge for tests, and the reason: “18,420 meaningful price drops” |
| Rule | The rule that sent it, linking to the rule’s page |
| Sent to | The integration it went to, or Local Notifications when the rule sends nowhere else. An amber badge such as “Slack not delivered” when delivery failed, with the error on hover |
| From | What caused it: the pipeline run, or the dataset |
| When | How long ago, with the exact time on hover |
Click a row to open that alert’s page: a rule’s alert opens inside its rule, and a Jason update opens its conversation. Pages are 50 rows long, with page controls and a per-page selector at the bottom. There are no filters; a rule’s own History tab lists that rule’s alerts, including the checks that did not fire.
Header actions:
A workspace with nothing yet shows “No notifications yet. They appear here when an alert rule fires or watched work finishes.” with a Set up alert rules link.
One notification
Each alert has its own page, inside its rule’s History: /notifications/<rule id>/history/<alert id>. The bell, Slack’s View notification link and the email’s View notification button all open it.
The page shows, top to bottom:
History at the top returns to the rule’s list. Up to 10,000 matching rows are kept per alert. When the workspace’s data retention removes them, the page keeps the count and says “These rows are no longer kept; the workspace’s retention policy removed them.”
Clear all
Clear all, on the Notifications page or in the bell, hides everything currently listed. The page asks first: “Clear all notifications? Alert rules keep their own history.” What it does:
There is no per-item dismiss or delete, and no retry for a failed delivery.
The bell
The bell sits in the top bar of every page.
“No alerts yet” shows when there is nothing to list. The bell refreshes every few seconds and when you return to the tab, so an alert shows within moments.
Browser notifications
Browser notifications reach your desktop or phone even when Jsonify is closed. They are a destination like Slack or email, with one difference: a browser notifications integration is bound to the person who enabled it and pings only that person’s devices.
- Connect it. Integrations → Outputs → Connect Output → Browser notifications, then tell Jason what should notify you.
- Enable on this device. On the integration’s Settings tab, press Enable on this device and allow notifications when your browser asks. The toast reads “This device will now receive browser notifications.”
- Repeat on each device. The panel reads “This device is subscribed. Re-enable on any other browser you want pinged.” once done.
Once enabled, choose it as a rule’s Send to, and the rule’s alerts arrive as system notifications: the rule name as the title, the reason as the body, and a click that opens the alert. See Browser notifications.
Because a browser notifications integration belongs to one person, a workspace rule sending to it notifies only that person. For a team, send the rule to Slack or email, and let each person use “notify me when done” for their own runs.
If you blocked notifications by mistake, the bell on a run shows a crossed-out icon: “Notifications are blocked for this site. Enable them in your browser settings to be pinged when this finishes.” Allow the site again in your browser settings and try again.
“Notify me when done” on a run
On a run that is still going, the header shows a small bell with the tooltip Notify me when this finishes. Press it, allow notifications if asked, and the toast reads “I’ll notify you when this finishes — you can close the tab.” Press it again to stop. When the run completes, fails or is cancelled you get one browser notification, for example “Pipeline run finished” and “Price & promotion tracking finished — 1,204 rows.” Clicking it opens the run. The bell is hidden in a browser that cannot show notifications.
“Notify me” on a Jason task
While Jason is working, the activity status shows Notify me. Press it to be told when the turn ends; the toast reads “You’ll be notified when Jason finishes.” If browser notifications are available they are used. Otherwise, or by choosing (edit), a Notify me by menu lets you pick Browser push or any live Slack, email or webhook integration in the workspace, or None to stop. The message reads “Jason finished”, “Jason replied”, “Jason needs your attention” or “Jason stopped”, with the conversation’s title, and opens the conversation.
Email delivery
Email is a destination like the others. Every workspace starts with an Email notifications integration addressed to the workspace owner, so a new rule can send email with no set-up. Add more for other recipients from Integrations → Outputs.
An alert email has the subject “[Jsonify] {rule name}”, a header of Notification, Run succeeded, Run failed, Run cancelled or Jason update, the reason as the message, the matching rows or the run’s datasets attached as Excel files, and a View notification or Open task button. The footer says the message was sent automatically. See Slack and email.
Completion pings
“Notify me when done” requests are delivered through a system rule named Completion pings (“Notifications you asked to receive when work finishes.”). It does not appear on the Rules tab and cannot be edited, but its alerts appear in the bell and on the Notifications page like any other, so you have a record of the runs and tasks you asked about. Each request is used once, by the first delivery.
Delivery status
Every alert records how delivery went:
| Status | Meaning |
|---|---|
| sent | The destination accepted it. |
| failed | The destination rejected it or could not be reached; the error is on the badge in Notifications, on the alert’s page and on the rule’s History tab. Nothing is retried. |
| skipped | Nothing to send: a check that did not fire, a test that only checked, or browser notifications with no enabled devices. |
| logged | The rule sends to Local Notifications only. |
A not delivered badge with “Integration … is not live” means the destination still needs setup or was paused. Open it from Integrations, finish its settings, press Test, then use Send test message on the rule’s Test tab to confirm.
Which alerts fired overnight, and did any of them fail to reach Slack?
Jason lists the alerts since yesterday evening by rule, flags the ones whose delivery failed with the error text, and offers to test the Slack integration.