Look up status page details on demand
When someone asks about a status page, send its id to Notis and get the Better Stack details in the report without opening another tool.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Status Page
Tool to get a single status page by id. use when you need detailed information about a specific status page.
Why this helps
Finding status page details during customer or team follow-up can add an unnecessary app switch to a busy moment.
- Retrieve a specific status page's details on demand.
- Use a simple request with a known page id.
- Keep the returned context in a run report for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Better Stack once in the Notis portal.
- 2Create a new automation in Automations, or tell Notis from any channel to create it.
- 3In one instruction, ask Notis to fetch the status page identified in the incoming request and summarize its details in the report.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real status page id and review the returned details.
Questions about this workflow
What does the request need?
Provide the Better Stack status page id so Notis can retrieve the specific page.
Will this publish or change the page?
No. This action retrieves status page details for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Better stack. A trigger fires from one place; an action lands in another.
Jira triggers
Better stack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Escalation Policy
Tool to create a new escalation policy. use when defining how incidents should escalate across team members.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Heartbeat Group
Tool to create a new heartbeat group. use when you need to organize related heartbeat checks under a single, logical group. example prompt: "create a new heartbeat group named 'backend services'."
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Outgoing Webhook Integration
Tool to create a new outgoing webhook integration. use when you need to register an endpoint to receive event notifications from better stack.
New Project
Triggered when a new project is added in Jira
Create Source Group
Tool to create a new source group. use when you have finalized the group name (and optional sort index) and need to organize related log sources under that group.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Delete Escalation Policy
Tool to delete an escalation policy by id. use when you need to permanently remove an existing escalation policy after confirming its id.
Delete Source Group
Tool to delete a source group by id. use when you need to permanently remove an existing source group after confirming it is no longer needed.
Get Heartbeat
Tool to get a single heartbeat by id. use when you need to fetch details of a specific heartbeat.
Get Heartbeat Availability
Tool to retrieve availability summary for a specific heartbeat. use when you need availability metrics for a heartbeat within an optional date range.
Connect any two apps with Notis in the middle.
Jira and Better stack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Better stack.