DIJJI.ai notifies you in two channels: email, sent to your account address, and Slack, posted to a channel you connect per project. This page lists every message in each channel, what triggers it, and what it carries.
Email goes to the address on your DIJJI.ai account. There is no per-user on/off switch — account and security email always sends. The only configurable email is the low-balance warning, whose trigger amount an admin sets for the organization.
| Sent when | What it contains | Status | |
|---|---|---|---|
| Verification code | You sign up, or change your account email. | A 6-digit code and how long it stays valid. | Live |
| Team invitation | An admin invites you to an organization. | The organization and team you’re invited to, your assigned role, the expiry date, and a link to accept. | Live |
| Task completed | A run finishes successfully. | The project and task, how long the run took, and what it cost, with a link to the task. | Coming soon |
| Task failed | A run ends in failure. | The project and task, the failure reason, when the last attempt ran, and a link to the task. | Coming soon |
| Action needed | A run reaches a stage gate that needs you. | The project, task, and stage name, what the stage is waiting on, and a link to act on it. | Coming soon |
| Low balance | The organization balance falls past a warning threshold. | The organization, the current balance, the threshold that was crossed, and a reminder that tasks can’t start below $10. | Coming soon |
The four emails marked coming soon are not yet sent. Until they ship, watch the run detail page or connect Slack (below) to track run progress, and watch the Billing page for the balance.
Verification code and invitation
These two are the email channel today. The verification code email carries a one-time code you enter to confirm your address — see Sign up and verify your email. The team invitation email carries an accept link; it expires, and an admin can resend it — see Invite a team member.
Low-balance warning
When the Low balance email ships, it fires as the organization balance drops through a set of thresholds — $50, $25, and $10 — so a falling balance produces a warning more than once. An admin can change the first threshold for the organization; $50 is the default. The $10 figure is also the floor below which a new task can’t start. See Balances, spending limits, and time.
Slack
Slack notifications are per project. Each project connects its own Slack channel through a webhook URL; one project’s messages never post to another’s channel. A project with no Slack connection sends no Slack messages. To set one up, see Set up Slack notifications for a project.
Every Slack message follows the same shape: a bold title line, an optional detail line, and a link back to the run or task in DIJJI.ai.
| Slack message | Posted when | Detail line |
|---|---|---|
| Task started | You start a run. | The run number and a link to the task. |
| Task completed | A run finishes successfully. | The run number and a link to the run. |
| Task failed | A run ends in failure. | The failure reason and a link to the run. |
| PR ready — merge to continue | A stage’s pull request is open and waiting for you to merge it. | The stage name and a link to the run. |
| Pipeline gate waiting | A run is held at a stage gate that needs you for another reason. | The stage name and a link to the run. |
| Answer needed — run paused | A run asks a question and waits for your reply. | The question being asked and a link to the run. |
| Plan approval needed — run paused | A run produces a plan and waits for your decision. | The plan version and a link to the run. |
Each message names the run number so you can tell concurrent runs apart. The link opens the run or task directly, so a message about a waiting run takes you straight to where you act on it.
Mapping Slack messages to run states
Four of the seven Slack messages mark a run that has paused and needs you. They line up with the run states:
| Slack message | Run state it signals |
|---|---|
| PR ready — merge to continue | Waiting for Gate |
| Pipeline gate waiting | Waiting for Gate |
| Answer needed — run paused | Waiting for Answer |
| Plan approval needed — run paused | Awaiting Plan Approval |
The other three — Task started, Task completed, Task failed — are progress reports, not calls to act.
Configuring delivery
| Slack | ||
|---|---|---|
| Scope | One address per account. | One channel per project. |
| Who sets it up | Set when you create your account. | An admin connects the project’s webhook. |
| Can it be turned off? | No — account email always sends. | Yes — remove the project’s Slack connection. |
| Adjustable | The low-balance threshold (admin, org-wide). | The webhook URL and channel for each project. |
If Slack messages stop arriving, the project’s Slack connection may have a delivery problem. Check its health on the integration — see Integration health states.