PAGERDUTY n8n INTEGRATION: AUTOMATE PAGERDUTY WITH N8N

The "Get User" action retrieves detailed information about a specific user from your PagerDuty account. This is particularly useful when you need to enrich incident data with assignee details, validate user existence before assigning incidents, or sync user information to other systems.

Key parameters: Credential to connect with: Required dropdown to select your PagerDuty account credentials for authentication. Resource: Set to "User" to interact with user-related operations. Operation: Set to "Get" to retrieve a single user's details. User ID: Required text field where you specify the unique identifier of the PagerDuty user you want to retrieve.

Practical use cases: Fetch on-call responder details to include in Slack notifications, validate user IDs before bulk incident assignments, or sync PagerDuty user profiles to your internal directory or CRM.

The "Get Many Log Entries" action allows you to retrieve multiple log entries from PagerDuty in a single request. Log entries capture the complete audit trail of incident activity, making this action essential for reporting, compliance, and post-incident analysis workflows.

Key parameters: Credential to connect with: Required dropdown for PagerDuty account authentication. Resource: Set to "Log Entry" to target log entry operations. Operation: Set to "Get Many" to retrieve multiple entries. Return All: Optional toggle—when enabled, fetches all available log entries regardless of limit. Limit: When "Return All" is disabled, this number field (default: 100) specifies the maximum entries to retrieve. Options: Expandable section with "Add Field" button for additional filtering parameters like incident IDs or date ranges.

Practical use cases: Generate weekly incident activity reports in Google Sheets, feed log entry data into your data warehouse for trend analysis, or create compliance audit trails by archiving all incident activities.

The "Get Log Entry" action retrieves details about a specific log entry using its unique identifier. This is useful when you need to fetch detailed information about a particular incident event, such as when it was acknowledged, who responded, or what actions were taken.

Key parameters: Credential to connect with: Required dropdown for selecting PagerDuty credentials. Resource: Set to "Log Entry" to work with log entry data. Operation: Set to "Get" to retrieve a single log entry. Log Entry ID: Required text field for the unique identifier of the log entry you want to retrieve.

Practical use cases: Fetch specific event details when building incident timeline visualizations, retrieve acknowledgment timestamps for SLA compliance tracking, or pull detailed log entry data for inclusion in post-incident review documents.

The "Get Many Incident Notes" action retrieves multiple notes attached to PagerDuty incidents. Incident notes contain valuable context added by responders during incident handling, making this action crucial for documentation and knowledge management workflows.

Key parameters: Credential to connect with: Required dropdown for PagerDuty authentication. Resource: Set to "Incident Note" to interact with notes. Operation: Set to "Get Many" for retrieving multiple notes. Incident ID: Optional text field to filter notes for a specific incident. Return All: Toggle to retrieve all notes instead of a limited number. Limit: Number field (default: 100) for maximum notes when "Return All" is disabled.

Practical use cases: Compile all notes from resolved incidents into Confluence pages for knowledge base, extract responder observations for machine learning analysis, or aggregate notes across multiple incidents for pattern detection.

The "Create Incident Note" action allows you to programmatically add notes to existing PagerDuty incidents. This is invaluable for automatically documenting actions taken by external systems, adding context from monitoring tools, or maintaining a comprehensive incident timeline.

Key parameters: Credential to connect with: Required dropdown for PagerDuty credentials. Resource: Set to "Incident Note" for note operations. Operation: Set to "Create" to add a new note. Incident ID: Required text field specifying which incident receives the note. Content: Required text field for the actual note content. Email: Required text field for the email address of the user creating the note (used for attribution in PagerDuty).

Practical use cases: Automatically add notes when automated remediation scripts run, document external system statuses (e.g., "Database backup completed during incident"), or add Slack or Discord conversation summaries to incidents for context preservation.

The "Update Incident" action enables you to modify existing PagerDuty incidents—changing status, priority, assignments, or adding conference bridge details. This is essential for building workflows that automatically escalate, resolve, or enrich incidents based on external signals.

Key parameters: Credential to connect with: Required dropdown for authentication. Resource: Set to "Incident" for incident operations. Operation: Set to "Update" to modify an existing incident. Incident ID: Required text field for the unique identifier of the incident to update. Email: Required text field for the email of the user making the update. Update Fields: Expandable section with "Add Field" button to specify which properties to modify (status, priority, assignments, etc.). Conference Bridge: Optional section to attach or update conference call details for the incident.

Practical use cases: Automatically resolve incidents when monitoring shows recovery, escalate incident priority based on customer tier from your CRM like HubSpot, or add Zoom meeting links as conference bridges when incidents are created.

The "Get Many Incidents" action retrieves multiple incidents from PagerDuty, enabling bulk operations, reporting, and dashboard integrations. This is your go-to action for building incident overview dashboards, generating reports, or syncing incident data to external systems.

Key parameters: Credential to connect with: Required dropdown for PagerDuty authentication. Resource: Set to "Incident" to work with incident data. Operation: Set to "Get Many" for bulk retrieval. Return All: Optional toggle to fetch all incidents instead of a limited number. Limit: Number field (default: 100) for maximum incidents when "Return All" is disabled. Options: Expandable section with "Add Field" for filtering by status, urgency, service, date range, and more.

Practical use cases: Build daily incident summary reports sent via email or Slack, sync all open incidents to a Google Sheet for executive dashboards, or feed incident data into your BI tool for trend analysis and MTTR calculations.

The "Get Incident" action retrieves detailed information about a specific PagerDuty incident using its unique identifier. This is essential when you need to fetch complete incident details for processing, validation, or enrichment within your workflows.

Key parameters: Credential to connect with: Required dropdown for selecting PagerDuty credentials. Resource: Set to "Incident" for incident-related operations. Operation: Set to "Get" to retrieve a single incident. Incident ID: Required text field for the unique identifier of the incident you want to retrieve.

Practical use cases: Fetch incident details to include in Slack notifications with full context, validate incident status before triggering downstream actions, or retrieve incident metadata for routing to appropriate support queues.

The "Create Incident" action allows you to programmatically create new incidents in PagerDuty. This is the foundation for building proactive alerting workflows that respond to signals from any system in your stack—monitoring tools, customer feedback platforms, or custom applications.

Key parameters: Credential to connect with: Required dropdown for PagerDuty authentication. Resource: Set to "Incident" for incident operations. Operation: Set to "Create" to generate a new incident. Title: Required text field for the incident's headline or summary. Service Name or ID: Text field specifying which PagerDuty service the incident belongs to. Email: Required text field for the email of the user creating the incident. Additional Fields: Expandable section for adding custom properties like urgency, priority, or body details. Conference Bridge: Optional section to immediately attach conference call information to the new incident.

Practical use cases: Create incidents from custom monitoring scripts or internal tools, generate PagerDuty alerts from customer-reported issues in Zendesk, or trigger incidents based on anomaly detection in your data pipeline using tools like Grafana or PagerDuty's Events API.