Low-code orchestration
Connect, compose and ship AI features faster.
PagerDuty Integrations
Build & publish in-app integrations with our PagerDuty connector
Multi-tenant deployment
Isolate customer credentials and configurations at scale.
Governed access
Apply policies, field controls and audit trails across usage.
Embedded experience
Deliver workflows natively inside your product.
CONNECTOR OVERVIEW
Create automations with our PagerDuty connector
Cyclr is a rapid approach to delivering native PagerDuty integrations directly in your application. Saving you and your developers time to focus on your core product. Using Cyclr’s low code tools you can build repeatable and manageable in-app integrations with a low-engineering overhead.
PRODUCT USE CASES
Top Use Cases for PagerDuty Integrations
Cyclr is designed to help you with delivering integration functionality within your platform, for your users. You’ll be able to build and deploy automated workflows in minutes using Cyclr’s drag and drop builder, and our embedded marketplace. Initiating easy, seamless deployment.
Developer Tools
- Combine external data sources and tools with your application's development environment to enhance your data
- Add additional data and tools to your application using low code tools
DevOps
- Create advanced processing reports across multiple data sources
- Create your own uptime monitoring solutions, combining external tools and 3rd and 1st party data
ORCHESTRATION
How PagerDuty works with Cyclr
Cyclr sits between your SaaS product and PagerDuty to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
PagerDuty
PagerDuty processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore PagerDuty methods you can orchestrate through Cyclr.
Users3
List Audit Records for User
ActionLists the audit records with changes to the identified user.
List Users Sessions
ActionList active sessions of a PagerDuty user.
List Users
ActionList the users.
Change Events2
List Change Events
ActionList all Change Events.
List Updated Change Events
ActionList Updated Change Events since last run cycle.
Incidents3
List Incidents
ActionList existing incidents.
List New and Updated Incidents
ActionList incidents created, or whose status has changed since last run.
Create Incident
ActionCreates an Incident
TECHNICAL DETAILS
PagerDuty integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing PagerDuty integrations in Cyclr.
API and authentication
- API host
Not specified- Authentication
- See Connector in Console
- Credentials
Review the connector installation fields in Cyclr Console.
- Method categories
See available methods
Pagination and rate limits
Pagination
Method-specific behavior should be confirmed before implementation.
Rate limits
Refer to the vendor API documentation for current limits.
IMPLEMENTATION
Authentication at a glance
Authentication requirements and any available connection options are shown when installing this connector in Cyclr Console.
- Authentication method
- See Connector in Console
- Credential required
Review the connector installation fields in Cyclr Console.
KEEP EXPLORING