Integrations
Connect PerformSpark with approved employee systems and workplace tools to keep data, assignments, and performance workflows aligned. Confirm current availability, supported fields, sync direction, and setup requirements during evaluation. Plan each connection alongside security and data protection, reporting and analytics, and the broader PerformSpark integration catalog.
Connect approved employee and reporting data from your system of record. Confirm supported fields, sync frequency, manager-change handling, and exception ownership for each connection.

Ask about current HiBob connection options and the employee and organization fields supported.

Ask about current Rippling connection options, sync direction, and supported employee fields.
Confirm current Personio availability, authentication requirements, and supported employee data.

Confirm current Humaans connection options and how employee and manager changes are handled.
Ask which BambooHR fields, employee events, and sync schedules are currently supported.
Confirm current Gusto connection availability, required permissions, and supported data scope.

Ask about current ADP connection options, supported employee fields, and implementation requirements.

Confirm current UKG availability, supported data objects, sync behavior, and error handling.
Deliver workflow prompts through supported workplace channels where configured. Confirm channel availability, message content, permissions, and fallback behavior. When Slack or Microsoft Teams is part of the process, review performance notification workflows and check-in and 1-on-1 workflows before deciding which events should create alerts.
Ask about current Slack notification options and the performance workflow events supported.
Confirm current Microsoft Teams notification options, permissions, and supported workflow events.
Review current Zoom or calendar connection options when meeting workflows are in scope.
Discuss required business-system connections, approved data flows, authentication, and ownership with the implementation team. Map approved data to the workflows it supports, including performance reviews, goal management, and individual development plans.
Confirm whether a current Salesforce connection is available for the required use case and data scope.
Ask whether Pipedrive can support the required approved workflow and which data fields are available.
Confirm current HubSpot connection options, supported objects, permissions, and sync behavior.
FAQs
Review these questions during vendor evaluation and require a demonstration using the systems and fields your organization actually needs.
Review the systems, fields, permissions, sync behavior, and implementation responsibilities required for your performance workflows.
They are controlled connections that exchange approved employee, organization, identity, or workflow data between a performance platform and another system. The exact scope varies by connector, so verify fields, direction, frequency, permissions, and error handling.
Available integrations can change. Review the current integration catalog and ask for a demonstration of the exact HRIS, identity, calendar, email, Slack, Teams, or other connection required. A logo alone does not confirm every field or workflow.
Common needs include employee ID, active status, manager, department, job title, location, and eligibility fields. Use only the data required for the workflow and define which system remains the source of truth for every field.
It depends on the connector and approved workflow. Many implementations only need inbound employee and manager data. Confirm source of truth, direction, write-back fields, sync frequency, conflict handling, and approval requirements.
A reliable connection can reduce duplicate entry and repeated assignment updates when source data are accurate. It does not remove the need for data governance, validation, monitoring, and a process for resolving failed or conflicting records.
Connection options depend on the learning platform and use case. Confirm whether links, assignments, completion data, or other fields are supported and how those records appear within the employee development workflow.
Timing depends on connector availability, required fields, authentication, data quality, security review, testing, and customer and vendor responsibilities. Ask for a requirements-based implementation plan rather than a universal setup promise.
Review the source and target systems, fields, sync direction, frequency, manager changes, leave and termination handling, permissions, encryption, logs, error ownership, support, cost, data retention, and exit requirements.
Bring approved employee data and performance workflows together through verified, controlled connections.
Make performance reviews your growth lever
No credit card required • Setup and training included • Annual contract minimums may apply

PIPs, reviews, self-appraisals, and 360 feedback — ready to download and edit today.
JUST LAUNCHED
Free HR templates are live