Surface engagement in-app
Show team scores and trends inside your product.
Peakon Connector
Embed Peakon Employee Voice inside your app to surface engagement scores, export survey answers, and sync employee records so customers act on pulse data without leaving your product.
Export survey data
Automate bulk exports of survey answers and reports.
Provision employees
Create and update users using Peakon SCIM tokens.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What you can integrate or automate with Peakon
Integrate Peakon to read engagement scores, export survey answers and reports, and provision or update employees via SCIM. Use Cyclr to build in-app automations that fetch Pulse and survey exports, push employee updates, and trigger downstream workflows when actions or reports appear. (developer.peakon.com)
PRODUCT USE CASES
Top Use Cases for Peakon Integrations
Quickly create integrations between your SaaS application and Peakon with Cyclr’s low code integration builder. Publish your Peakon integration into your application using Cyclr’s white label embedded integration marketplace.
Automate employee provisioning with SCIM
Create, update and deactivate employee records in Peakon using the SCIM bearer token to keep HR data in sync.
Export survey answers to analytics
Schedule exports of survey answers and feed them into BI or data warehouses for custom reporting and analysis. (developer.peakon.com)
Surface engagement scores in your app
Fetch engagement overview and team-level scores so customers see Pulse and trends inside your application. (developer.peakon.com)
ORCHESTRATION
How Peakon works with Cyclr
Cyclr sits between your SaaS product and Peakon 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
Peakon
Peakon 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 Peakon methods you can orchestrate through Cyclr.
Employees4
Create Employee
ActionCreate a new employee.
Delete Employee
ActionDelete an employee by ID.
Get Employee
ActionGet an employee by ID.
List Employees
ActionGet a list of all employees.
TECHNICAL DETAILS
Peakon integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Peakon integrations in Cyclr.
API and authentication
- API host
https://{subdomain}.peakon.com/api/v1- Authentication
- Application token; Bearer token
- Credentials
Provide application access token or SCIM bearer token and Peakon subdomain.
- Method categories
Survey exports; Engagement reads; SCIM user provisioning; Segments and actions reads.
Pagination and rate limits
Pagination
Collection endpoints use per_page or JSON:API page[offset]/page[limit]; answers export supports per_page up to 20,000 records. (developer.peakon.com)
Rate limits
Rate limits are enforced per application but exact limits are not publicly published; handle 429 with backoff. (doc.workday.com)
IMPLEMENTATION
Authentication at a glance
Peakon issues per-application access tokens that are exchanged for a JWT. SCIM and admin APIs use separate bearer tokens created in Integrations settings. (developer.peakon.com)
- Authentication method
- Application token; Bearer token
- Credential required
Provide application access token or SCIM bearer token and Peakon subdomain.
Before you begin:
View setup guideEnable Data Export/Custom Apps in Peakon admin; SCIM token is separate.
COMMON QUESTIONS
Frequently asked questions
It can retrieve engagement overviews and survey answers, export raw survey data, read segments and actions, and provision employees via SCIM for automated HR workflows. (developer.peakon.com)
Peakon issues a per-application access token that you exchange for a JWT for API calls; SCIM and admin endpoints use separate bearer tokens generated in Integrations. (developer.peakon.com)
Yes. Use Cyclr to manage per-customer credentials and subdomains so flows run against each customer’s Peakon account while keeping orchestration reusable and governed.
Yes. Cyclr can expose selected Peakon calls (exports, reads, SCIM actions) as governed MCP tools and enforce access, versioning and tenant-specific credentials centrally.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorBambooHR
Related HR/payroll connector for customer-facing integration workflows.
Related connectorbob HR
Related HR/payroll connector for customer-facing integration workflows.
Related connectorBreathe HR
Related HR/payroll connector for customer-facing integration workflows.