Skip to content
finn.
Integrations PingID

Integration · IT and identity

PingID + Finn.

PingID integration with Finn. PingID provides multifactor authentication for employee access to business systems.

Discuss this integration Explore the workflows

The work behind the connection

What you can do with PingID.

PingID provides multifactor authentication for employee access to business systems.

Complete new-hire authentication enrollment

Finn takes a new employee through the authentication setup their role requires, connecting the invitation, device activation, and enrollment result to the onboarding request.

Typically handled byIdentity onboarding support team

Starts when

The employee's account is ready and their onboarding checklist requires PingID enrollment.

What Finn handles

  1. Match the Workday hire and existing identity-provider account to the correct PingID user.
  2. Send the enrollment instructions through the organization's verified employee channel and explain the required device setup.
  3. Guide the employee through PingID's activation and verification steps without asking them to reveal authentication secrets.
  4. Check the enrollment result and complete the related ServiceNow onboarding task with the registered method's status.

The result

The employee finishes authentication enrollment, and the onboarding record shows the method is ready for use.

Replace an employee's authentication phone

Finn completes the recovery process for a lost or replaced sign-in phone, keeping the verification decision and the replacement's activation connected to the employee's support case.

Typically handled byAuthentication device recovery desk

Starts when

An employee reports that their registered phone is lost, damaged, or being replaced.

What Finn handles

  1. Complete the organization's identity-verification process and establish which registered device the request concerns.
  2. Apply the device removal or reactivation authorized by that recovery process in PingID.
  3. Guide the employee through enrollment of the replacement using the provider's activation procedure and the designated channel.
  4. Confirm the new method's recorded state and the employee's sign-in result, then close the ServiceNow request.

The result

The employee has a working replacement method and the previous phone's treatment is documented in the recovery record.

Resolve a failed authentication attempt

Finn investigates why an employee cannot complete their second sign-in step and carries the documented remedy through verification, without weakening the organization's authentication requirements.

Typically handled byMultifactor authentication service desk

Starts when

An employee reports repeated PingID failures despite reaching the sign-in challenge.

What Finn handles

  1. Verify the employee and review the authentication event, user state, and enrolled-device information.
  2. Identify the documented issue, such as incomplete activation or a device registration needing recovery.
  3. Complete the permitted enrollment repair or recovery action, retaining any security-driven restriction for its owner's decision.
  4. Have the employee retry the normal sign-in flow and record the result and repair in ServiceNow.

The result

The authentication problem is resolved through the established controls or retained as a specific security exception.

Finish the authentication portion of a departure

Finn closes out the authentication work after an authorized employee departure, coordinating device registrations with the primary identity-provider action and retaining the required service evidence.

Typically handled byIdentity offboarding operations team

Starts when

HR confirms a departure and the identity team authorizes its authentication cleanup.

What Finn handles

  1. Match the departing employee's Workday event to their PingID account and registered authentication methods.
  2. Confirm the primary identity-provider offboarding action in connected Okta at the approved effective time.
  3. Remove or retire the PingID registrations specified by the organization's departure policy, preserving required records.
  4. Record the completed authentication cleanup and any remaining primary-application access work in the ServiceNow departure request.

The result

The departing employee's authentication registrations follow the authorized lifecycle decision, with the primary access result separately recorded.

Complete an authentication rollout for a defined group

Finn runs the operational work of an enrollment campaign, helping each employee finish setup and giving the rollout owner a record of completed enrollments and real exceptions.

Typically handled byAuthentication rollout coordinator

Starts when

IT authorizes PingID enrollment for a named employee group and target date.

What Finn handles

  1. Identify the eligible employees from the approved identity-provider group and their current enrollment states.
  2. Send the enrollment instructions and answer setup questions using the provider's published guidance.
  3. Follow incomplete enrollments with targeted help and complete verified recovery actions where a device problem prevents setup.
  4. Record each enrollment result in the rollout's ServiceNow work and identify employees blocked by a specific unresolved decision.

The result

The campaign produces completed employee enrollments and an actionable exception list rather than repeated generic reminder messages.

Retire an authentication device after a security decision

Finn executes the authentication-device portion of a confirmed security response, connects it to the broader identity incident, and follows the employee's authorized recovery through completion.

Typically handled bySecurity response and identity support team

Starts when

The security owner identifies a registered device that must no longer be used for authentication.

What Finn handles

  1. Match the incident's device and employee to the correct PingID registration and containment decision.
  2. Remove the specified registration, while connected Okta handles any separately authorized account or session containment.
  3. After the security owner authorizes recovery, take the employee through the established verification and replacement enrollment process.
  4. Write the removal, replacement state, and remaining incident obligations into the linked ServiceNow security case.

The result

The identified authentication device is retired and any authorized replacement is recorded without treating device removal as universal account containment.

Connection setup

Set up the connection around your work.

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from PingID.

The Finn platform

Finn Agents

Help customers. Work with your team. Finish the job.

Explore Agents

Finn Systems

Business apps for the work behind the conversation.

Explore Systems

Finn AI Gateway

Control connected AI apps, models, access, and spending.

Explore AI Gateway

Meet Finn

Put your PingID integration to work.

Tell us which records, actions, and teams the connection needs to support.

Discuss your workflow Get started