Notification settings, Jira & chat

Weekly spend summary, Slack and Teams webhooks, and connecting Jira Cloud.

Notification settings, Jira & chat

Choose how you receive your spend summary, connect Jira so alerts open issues, and send report digests to Slack or Microsoft Teams.

Where in CostGlassSettings → Notifications
PlanAll plans
Who can do thisEveryone for their own summary; Owner and Admin for Jira
Time needed10 minutes
In short
  • Spend summaries are personal: each person chooses their own schedule and channels.
  • The weekly summary goes out on Mondays at 01:00 UTC, by email by default. Slack and Microsoft Teams are optional.
  • Webhook URLs are secrets: after saving they are shown only as the last four characters.
  • Jira Cloud can be connected once per organisation by an Owner or Admin, then chosen as a channel on alert rules.
  • Scheduled reports and saved views can also post a digest to Slack or Teams.
Before you begin
  • For Slack or Teams: permission to create an incoming webhook in your workspace.
  • For Jira: a Jira Cloud site (https://yourcompany.atlassian.net), an Atlassian account that can create issues in the project, and an Owner or Admin role in CostGlass.

Your spend summary

1
Open the page
Choose Settings, then Notifications.
Settings → Notifications: delivery schedule, channels and a live preview.
2
Pick a schedule
Under Delivery Schedule tick Weekly Spend Summary (default, recommended) and optionally Monthly Executive Rollup.
3
Pick channels
Under delivery channels keep Email Digest on, or enable Slack Incoming Webhook or Microsoft Teams Webhook and paste the webhook URL.
4
Save and test
Click Save Preferences, then Send Test Notification to send a sample now. The preview underneath shows how the email, Slack and Teams versions look.
SummaryWhen it is sentWhat it compares
WeeklyMondays, 01:00 UTC. Only people who existed on that Monday receive it, so a new account gets its first one the following Monday.The past 7 days against the 7 days before.
MonthlyThe 1st of the month, 01:00 UTC (the page text says 02:00 UTC; the job runs at 01:00).The full month against the previous calendar month.

Each summary shows estimated monthly spend, month to date, the change against last month and the top seven services. If your organisation has no recorded spend yet the page says so and nothing is sent. If sending fails, the test reports the failure instead of pretending it worked.

Slack and Microsoft Teams webhooks

Slack

  1. In Slack, create an app (or use an existing one) and turn on Incoming Webhooks.
  2. Add a webhook to the channel that should receive the summary and copy its URL.
  3. Paste it into Slack Incoming Webhook in CostGlass. It must look like https://hooks.slack.com/services/....

Microsoft Teams

  1. In Teams, add an incoming webhook or a Workflows webhook to the channel and copy the URL.
  2. Paste it into Microsoft Teams Webhook. Accepted addresses end in .webhook.office.com, or are Workflows addresses (.logic.azure.com, .api.powerplatform.com) or outlook.office.com.
Treat webhooks as passwords
Anyone with the URL can post to your channel. CostGlass only accepts addresses on these approved hosts, never shows the full URL again, and keeps the saved one if you leave the box empty. To replace it, paste a new URL.
Tip
Click Send Test Notification after saving: a placeholder or mistyped URL is rejected with a clear message.

Connect Jira Cloud

Once connected, you can pick Jira as a channel on anomaly notification rules and cost alerts. Each event creates one issue, and the same event never creates two.

1
Create an API token in Atlassian
Go to id.atlassian.com, open Security, then API tokens, and create one. Copy it.
2
Open the Jira card
On Settings → Notifications find the Jira card (visible to Owners and Admins).
3
Enter your site
Fill in Jira site URL (for example https://yourcompany.atlassian.net), Atlassian account email and API token.
4
Choose where issues go
Type the Project key (for example OPS) and the Issue type (default Task), or click Find projects to pick from suggestions.
5
Connect
Click Connect. CostGlass checks the token, project and issue type with Jira first; nothing is saved if the check fails.
6
Send a test
Click Send test issue and confirm. One real issue titled "[CostGlass TEST] Jira connection test" is created; close it afterwards.
  • Only Jira Cloud sites on atlassian.net over https are accepted.
  • The token is stored in a secrets vault and only its last four characters are ever shown. Leave API token blank when editing to keep it.
  • The account must be able to create issues in the project.
  • Edit changes the project or token. Disconnect stops new issues; existing issues stay in Jira.
  • The card shows Connected or Needs attention and the last error.
Note
The Jira connection has been built against Atlassian's documentation and tested with simulated responses. Run the test issue before relying on it.

Report and view digests in Slack or Teams

When you schedule a saved report (in the report library) or a saved Cost Explorer view, the schedule dialog has Also post a summary to chat (optional). Click Slack or Microsoft Teams to add a channel (up to five), give it a label and paste its webhook. The post is a short summary: total, change against the previous period, biggest movers, top items and a link back. A schedule needs at least one email recipient or one chat channel.

Frequently asked questions

Do my colleagues get my settings?
No. Summary preferences and webhooks belong to the person who saved them.
I did not get Monday's email.
You may have joined after that Monday, have no recorded spend yet, or have the weekly summary off. Check spam and use Send Test Notification.
Where do anomaly and budget alerts go?
Those are set on their own rules, not here. See Alerts overview.

Related guides