ceven

PagerDuty

Triggers incident responses based on external signals, syncs on call schedules with team calendars, and automates the creation of postmortem reports.

Try PagerDuty in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native PagerDuty integration

    • Describe the outcome and Ceven picks the right PagerDuty calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your PagerDuty data, across all 363 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke PagerDuty access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in PagerDuty, when, and on whose behalf.
    • The agent pauses and asks when PagerDuty is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach PagerDuty.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every PagerDuty action to support review and sign off.

Supported tools

Every action Ceven's agents can run on PagerDuty, and when to use it.

Create incident
Use this when an external event requires immediate attention from on call teams to start a formal incident record.
Create service
Set up a new monitored service with specific escalation policies and configurations.
Create escalation policy
Define the structured response plan and order of responders for a specific service.
Create schedule layer
Establish rotation patterns for team members to manage who is on call and when.
Create status page post
Publish an update to the public status page regarding an incident or planned maintenance.
Create postmortem
Add a detailed analysis and resolution summary to a status page post after an incident ends.
Create response play
Define a set of automated actions to execute when a specific type of incident occurs.
Create schedule override
Temporarily change the on call person for a specific time window for vacations or swaps.
Create maintenance window
Schedule a period where incidents are suppressed for a specific service during planned work.
Create incident workflow
Build a series of automated steps to be executed during the incident response process.
Create team
Establish a group of users with shared responsibilities for organization and routing.
Create webhook subscription
Set up a listener to receive notifications for specific PagerDuty events in real time.
Add service to incident workflow trigger
This endpoint adds a service to an existing incident workflow trigger in pagerduty. it allows you to associate a specific service with a trigger, enabling automated incident management processes for that service. use this endpoint when you
Aggregate escalation policy incident metrics
This endpoint analyzes and aggregates incident metrics across all escalation policies in pagerduty. it allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response times,
Associate service dependencies
Associates multiple service dependencies in pagerduty, allowing you to define relationships between supporting and dependent services. this endpoint is used to establish a hierarchical structure of services, which is crucial for effective i
Associate team with automation action
This endpoint associates a specific team with an automation action in pagerduty. it allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response processe
Audit escalation policy records
Retrieves the audit records for a specific escalation policy in pagerduty. this endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services, a
Convert service rule by id
Converts the rules associated with a specific pagerduty service to a new or optimized format. this endpoint is used to update and standardize the incident management rules for a given service, improving the efficiency and consistency of ale
Count paused incident reports
Retrieves the count of paused incident reports in the pagerduty system. this endpoint is part of pagerduty's incident management and analytics features, providing a quick way to quantify the number of incidents that are currently in a pause
Create a custom field for an incident type
Create a custom field for an incident type. custom fields (cf) are a feature which will allow customers to extend incidents with their own custom data, to provide additional context and support features such as customized filtering, search
Create a field option for a custom field
Create a field option for a custom field. custom fields (cf) are a feature which will allow customers to extend incidents with their own custom data, to provide additional context and support features such as customized filtering, search an
Create and manage custom incident fields
Creates a new custom field for incidents in pagerduty. this endpoint allows you to define additional data points to be associated with incidents, enhancing incident management and reporting capabilities. custom fields can be used to store v
Create an incident type
Create a new incident type. incident types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident. <!-- theme: warning --> > ### early access > this endpoint is i
Create a ruleset
Creates a new ruleset in pagerduty for managing incident routing and notification rules. this endpoint allows you to define a named set of rules that determine how incidents are processed and directed to specific teams or users. it's partic
Create a trigger
Create new incident workflow trigger scoped oauth requires: `incident workflows.write`
Create automation runner endpoint
Creates a new automation runner in the pagerduty incident management system. this endpoint allows you to set up either a sidecar runner, which polls for invocations externally, or a runbook runner, which communicates directly with a runbook
Create business service
This endpoint creates a new business service in pagerduty, which represents a specific service or application that can be monitored and managed within the incident management platform. it allows you to define essential properties of the ser
Create event orchestration
Creates a new event orchestration in pagerduty, which defines how incoming events are processed and routed to appropriate services. this endpoint allows you to set up a configuration that manages the flow of events from various integrations
Create event rule in ruleset
Creates a new event rule within a specified ruleset in pagerduty's incident management system. this endpoint allows you to define complex conditions for event matching and specify actions to be taken when an event meets those conditions. us
Create extension object
Creates a new extension in pagerduty, allowing for additional functionality or integrations to be added to your services. this endpoint is used to set up webhooks, custom integrations, or other specific features that enhance the capabilitie

30 actions · scroll to see them all

Frequently asked questions

Ceven uses OAuth 2.0 to connect to your PagerDuty account. When you initiate the connection, you are redirected to PagerDuty to authorize specific scopes. We never see or store your password. Once authorized, PagerDuty provides an access token and a refresh token. We store these tokens in an encrypted vault. The agent uses these tokens to make API calls on your behalf. You can revoke access instantly from the PagerDuty API access settings page, which kills the token and prevents any further actions by the agent. This ensures your security team maintains full control over who or what can trigger incidents.
Yes. The agent can interact with schedule layers and overrides to manage your rotations. You can tell the agent to swap a shift between two users or to add a temporary override for a holiday. It reads the current schedule to ensure there are no gaps before applying the change. For complex rotations involving multiple layers, the agent can identify who is currently primary and who is secondary. This removes the need for manual calendar updates and ensures that the right person is always paged without the admin having to click through the PagerDuty UI for every single change.
PagerDuty enforces strict rate limits on their API based on the account tier. If Ceven encounters a 429 Too Many Requests error, the agent implements an exponential backoff strategy. It will pause the workflow and retry the request after the duration specified in the Retry After header. For very high volume environments, we recommend using webhooks for event ingestion rather than polling the API. This reduces the load on your rate limit quota and ensures that critical incident triggers are processed with the lowest possible latency without being throttled by the PagerDuty API gateway.
Absolutely. Ceven can create and update status page posts based on the state of an incident. For example, when an incident is acknowledged, the agent can post a message saying the team is investigating. When the incident is resolved, it can automatically mark the status page as operational. You can define templates for these messages so they remain professional and consistent. This prevents the engineering team from having to leave their terminal to update stakeholders, ensuring that customers stay informed in real time while the engineers focus on restoring the service.
Yes. The agent can create and trigger response plays to standardize how your team handles specific failures. A response play can include adding specific users to an incident or triggering a set of diagnostic scripts. Ceven can be configured to trigger these plays based on the incident category or the service affected. This ensures that every sev one outage follows the same rigorous process regardless of who is on call. By automating the initial response steps, you reduce the mean time to resolution and eliminate the risk of human error during high pressure situations.
Yes. Because the agent has access to the PagerDuty API, it can perform bulk operations that would be tedious in the UI. For instance, you can ask the agent to add a specific tag to all services owned by a particular team or to update the escalation policy for a group of legacy services. The agent iterates through the list of services and applies the changes one by one. It provides a summary of the changes made and flags any services that could not be updated due to permission issues or missing data.
After an incident is marked as resolved in PagerDuty, Ceven can trigger a workflow to draft the postmortem. The agent pulls the entire incident timeline, including when the alert fired, who acknowledged it, and all the notes added by responders. It then uses this data to create a chronological narrative of the event. You can then review this draft, add the root cause analysis, and publish it to your status page. This eliminates the dreaded task of manually reconstructing a timeline from Slack messages and logs hours after the incident occurred.
The latency depends on whether you use polling or webhooks. When configured with PagerDuty webhooks, the notification reaches Ceven in near real time, typically within a few seconds. The agent then processes the event and executes the defined workflow. If you are using a polling mechanism, there will be a slight delay based on the polling interval. For mission critical infrastructure, we always recommend the webhook approach to ensure that automated response plays are triggered the instant an incident is created, minimizing the window of downtime for your users.

Alternatives to PagerDuty

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Opsgenie logoOpsgenieSplunk On Call logoSplunk On CallVictorOps logoVictorOps

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect PagerDuty and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free