Run pipelines to supercharge your PagerDuty workflows using Flowpipe.

pagerduty

pagerduty.pipeline.create_incident

incident

Name for credentials to use. If not provided, the default credentials will be used.

cred

service_id

service_type

A succinct description of the nature, symptoms, cause, or effect of the incident.

title

The email address of a valid user associated with the account making the request.

from

body

body_type

The phone number of the conference call for the conference bridge.

conference_number

An URL for the conference bridge. This could be a link to a web conference or Slack channel.

conference_url

The ID of the escalation policy for the incident.

escalation_policy_id

The type of the escalation policy for the incident.

escalation_policy_type

A string which identifies the incident. Sending subsequent requests referencing the same service and with the same incident_key will result in those requests being rejected if an open incident matches that incident_key.

incident_key

priority_id

The type of the priority of the incident.

priority_type

The urgency of the incident. Allowed values are 'high' and 'low'.

urgency

create_incident

Create Incident

Create a new note for the specified incident.

pagerduty.pipeline.create_note_on_incident

note

content

incident_id

create_note_on_incident

Create Note on Incident

Create a new status update for the specified incident.

pagerduty.pipeline.create_status_update_on_incident

The new status update for the specified incident.

status_update

The message to be posted as a status update.

message

create_status_update_on_incident

Create Status Update on Incident

pagerduty.pipeline.create_user

user

email

name

color

description

job_title

license

The user role. Account must have the read_only_users ability to set a user as a read_only_user or a read_only_limited_user, and must have advanced permissions abilities to set a user as observer or restricted_access.

role

The preferred time zone name. If null, the account's time zone will be used.

time_zone

create_user

Create User

pagerduty.pipeline.delete_user

user_id

delete_user

Delete User

Get details about the current user. Requires use a user-level token.

pagerduty.pipeline.get_current_user

get_current_user

Get Current User

Show detailed information about an incident.

pagerduty.pipeline.get_incident

get_incident

Get Incident

pagerduty.pipeline.get_user

get_user

Get User

pagerduty.pipeline.list_incident_alerts

alerts

list_incident_alerts

List Incident Alerts

List log entries for the specified incident.

pagerduty.pipeline.list_incident_log_entries

log_entries

list_incident_log_entries

List Incident Log Entries

List existing notes for the specified incident.

pagerduty.pipeline.list_incident_notes

notes

list_incident_notes

List Incident Notes

pagerduty.pipeline.list_incidents

incidents

list_incidents

List Incidents

pagerduty.pipeline.list_on_calls

on_calls

list_on_calls

List On-Calls

pagerduty.pipeline.list_users

users

list_users

List Users

pagerduty.pipeline.snooze_incident

The incident that was successfully snoozed.

The number of seconds to snooze the incident for. After this number of seconds has elapsed, the incident will return to the triggered state.

duration

snooze_incident

Snooze Incident

Acknowledge, resolve, escalate or reassign an incident.

pagerduty.pipeline.update_incident

The incident type. Allowed values are 'incident' and 'incident_reference'

type

Escalate the incident to this level in the escalation policy.

escalation_level

The resolution for this incident if status is set to resolved.

resolution

The new status of the incident. Allowed values are 'acknowledged' and 'resolved'.

Triggers