Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsPagerDuty ToolsPagerduty Fetch Incident List
PagerDuty Tools

Pagerduty Fetch Incident List

Retrieves a list of incidents from PagerDuty based on specified criteria. This endpoint allows users to fetch multiple incidents, making it useful for incident management, reporting, and analysis. It supports filtering by status and date range, as well as pagination for handling…

Write actionRisk level 2 of 5API key connection
Use Pagerduty Fetch Incident List

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • limitinteger
    Number of incidents to return per page. Must be between 1 and 100. Default is 25 if not specified. Use with offset for pagination.
  • sincestring
    Start of date range filter (ISO 8601 format). Only incidents created after this time are returned. Example: '2024-01-01T00:00:00Z'. Maximum range is 6 months. Defaults to 1 month ago if not specified. Ignored when date_range='all'.
  • totalboolean
    By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated. See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more informatio…
  • untilstring
    End of date range filter (ISO 8601 format). Only incidents created before this time are returned. Example: '2024-12-31T23:59:59Z'. Must be within 6 months of 'since' parameter. Defaults to now if not specified. Ignored when date_range='all'.
  • offsetinteger
    Pagination offset to start results from. Use with limit for pagination. For example, offset=25 with limit=25 returns results 26-50. Default is 0.
  • includearray
    Array of additional details to include in the response. Available options: 'acknowledgers', 'agents', 'assignees', 'conference_bridge', 'escalation_policies', 'first_trigger_log_entries', 'priorities', 'services', 'teams', 'users'. Including these expands the response with addit…
  • sort_byarray
    Sort incidents by specified fields and direction. Format: 'field:direction'. Available fields: 'incident_number', 'created_at', 'resolved_at', 'urgency'. Direction: 'asc' (default) or 'desc'. Examples: ['created_at:desc'], ['urgency:desc', 'created_at:asc']. Maximum two fields.…
  • statusesarray
    Filter incidents by status. Accepts multiple values: 'triggered', 'acknowledged', 'resolved'. Returns only incidents matching the specified statuses. If not specified, returns incidents of all statuses.
  • team__idsarray
    An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter.
  • time_zonestring
    Time zone for rendering dates/times in response. Uses IANA time zone format (e.g., 'America/New_York', 'UTC', 'Europe/London'). Defaults to account's configured time zone if not specified.
  • urgenciesarray
    Array of urgencies to filter incidents. Accepts multiple values: 'high', 'low'. Defaults to all urgencies if not specified. Account must have the `urgencies` ability to use this filter.
  • user__idsarray
    Returns only the incidents currently assigned to the passed user(s). This expects one or more user IDs. Note: When using the assigned_to_user filter, you will only receive incidents with statuses of triggered or acknowledged. This is because resolved incidents are not assigned t…

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.