Connect PagerDuty to Reepay

Both apps 48PagerDuty 28Reepay 20

• Trigger
  List Maintenance Windows

  Gets a list of maintenance windows (GET /maintenance_windows).

• Trigger
  New Incidents

  Polls for new incidents in PagerDuty (GET /incidents, newest first).

• Action
  Add Responders

  Request additional responders (a user or escalation policy) to help with an incident.

• Action
  Add Team Member

  Add a user to a team with a given role.

• Action
  Create Incident

  Creates an incident in PagerDuty (POST /incidents).

• Action
  Create Note on Incident

  Creates a note on a given incident.

• Action
  Delete or End a Maintenance Window

  Deletes a maintenance window that hasn't started yet, or ends one that is ongoing.

• Action
  Get Escalation Policy

  Retrieve a single escalation policy by its ID.

• Action
  Get Incident

  Retrieve a single PagerDuty incident by id.

• Action
  Get Schedule

  Retrieve a single on-call schedule by its ID.

• Action
  Get Service

  Retrieve a single PagerDuty service by id.

• Action
  Get Team

  Retrieve a single team by its ID.

• Action
  Get User Information

  Gets a user's information based on provided ID.

• Action
  List Escalation Policies

  List PagerDuty escalation policies (GET /escalation_policies).

• Action
  List Incident Notes

  List all notes attached to an incident.

• Action
  List Incidents

  List PagerDuty incidents with filters (statuses, service_ids, urgencies, date range) (GET /incidents).

• Action
  List On-Calls

  List current on-call entries — who is on call now, by escalation policy/schedule/user/time window (GET /oncalls).

• Action
  List Schedule Overrides

  List overrides on a schedule within a required since/until time window.

• Action
  List Schedules

  List PagerDuty on-call schedules (GET /schedules).

• Action
  List Services

  List PagerDuty services (GET /services).

• Action
  List Teams

  List all teams in the account.

• Action
  List Users

  List PagerDuty users (GET /users).

• Action
  Manage Incidents

  Bulk acknowledge or resolve multiple incidents in a single call.

• Action
  Snooze Incident

  Snooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires.

• Action
  Two-way sync add a maintenance window

  Creates a maintenance window for use with two-way sync triggers (POST /maintenance_windows). Does not update. Use only with two-way sync triggers.

• Action
  Two-way sync add or update an incident

  Creates or updates an incident for use with two-way sync triggers (POST /incidents; incident_key dedups). Use only with two-way sync triggers.

• Action
  Update Incident

  Updates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.

• Action
  Update Maintenance Window

  Updates a maintenance window.

• Action
  Add coupon

  Create a new coupon. POST /v1/coupon

• Action
  Add credit

  Create a credit note/credit for a customer. POST /v1/credit

• Action
  Add customer

  Create a new customer. POST /v1/customer

• Action
  Add invoice

  Create an invoice for a customer. POST /v1/customer/{handle}/invoice

• Action
  Add plan

  Create a new subscription plan. POST /v1/plan

• Action
  Add subscription

  Create a new subscription for a customer. POST /v1/subscription

• Action
  Cancel subscription

  Cancel a subscription by handle. POST /v1/subscription/{handle}/cancel

• Action
  Delete customer

  Delete a customer by handle. DELETE /v1/customer/{handle}

• Action
  Get charge

  Retrieve a charge by handle. GET /v1/charge/{handle}

• Action
  Get coupon

  Retrieve a coupon by handle. GET /v1/coupon/{handle}

• Action
  Get customer

  Retrieve a customer by handle. GET /v1/customer/{handle}

• Action
  Get invoice

  Retrieve an invoice by id. GET /v1/invoice/{id}

• Action
  Get plan

  Retrieve the current version of a plan by handle. GET /v1/plan/{handle}/current

• Action
  Get subscription

  Retrieve a subscription by handle. GET /v1/subscription/{handle}

• Action
  List customers

  List all customers. GET /v1/list/customer

• Action
  List invoices

  List all invoices. GET /v1/list/invoice

• Action
  List plans

  List all plans. GET /v1/list/plan

• Action
  List subscriptions

  List all subscriptions. GET /v1/list/subscription

• Action
  Update customer

  Update an existing customer by handle. PUT /v1/customer/{handle}

• Action
  Update subscription

  Change/update an existing subscription by handle. PUT /v1/subscription/{handle}

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.