PagerDuty and Atlassian Statuspage

PagerDuty

Triggers

• New incidentRuns when an incident is opened in PagerDuty, with a link to it (html_url) and who is on call for it (on_call).
• Incident acknowledgedRuns when someone acknowledges an incident in PagerDuty.
• Incident resolvedRuns when an incident is resolved in PagerDuty.

Actions

• Find incidentsFind incidents, newest first, by status, urgency, service and when they were opened.
• Get incidentGet one incident: its status, urgency, service and who it is assigned to.
• Create incidentOpen an incident on a service. PagerDuty notifies whoever is on call for it, or the people you assign.
• Acknowledge incidentAcknowledge an incident, so PagerDuty stops paging people about it.
• Resolve incidentResolve an incident, optionally saying how it was fixed.
• Update incidentChange an incident's title, urgency or priority, or escalate it to another level of its escalation policy.

Atlassian Statuspage

Actions

• List status pagesList every status page the connected user manages, with its name, address, time zone and subscriber settings.
• Update status pageChange a status page's name, website, time zone, search visibility or which kinds of subscriber it allows. Only what you fill in changes.
• List componentsList the components on a status page with their status and group. Gets one page; to see more, run it again with the next page number.
• Get componentGet one component with its status, description and group.
• Add componentAdd a component, a part of your service people can see the status of, to a status page.
• Update componentRename a component or change its status, description, group or whether it shows on the page. Only what you fill in changes. Changing the status here does not post an incident or notify subscribers.