Skip to content
finn.
Integrations BMC Helix ITSM

Integration · IT and identity

BMC Helix ITSM + Finn.

BMC Helix ITSM integration with Finn. BMC Helix ITSM manages IT incidents, service requests, and support knowledge.

Discuss this integration Explore the workflows

The work behind the connection

What you can do with BMC Helix ITSM.

BMC Helix ITSM manages IT incidents, service requests, and support knowledge.

Resolve a failing employee application and close the support loop

Finn takes a familiar employee technology problem from the initial report through the documented repair, using BMC Helix ITSM to preserve the evidence and the final result.

Typically handled byEmployee IT support desk

Starts when

An employee reports a failing employee application through an existing service channel.

What Finn handles

  1. Record the symptoms, affected employee, and relevant device in BMC Helix ITSM.
  2. Use published support guidance and Jamf device information to identify the applicable routine fix.
  3. Run the approved action through Jamf, arranging any required restart with the employee.
  4. Check the returned device result and employee confirmation, then save the resolution and close the incident.

The result

The employee's working setup is restored and the support record explains the action that resolved it.

Complete a new hire's technology setup

Finn coordinates the digital work behind an employee's first day, turning approved hiring details into completed access and device tasks with one accountable service record.

Typically handled byIT onboarding coordinator

Starts when

Workday records an approved hire whose start date is approaching.

What Finn handles

  1. Create the onboarding request in BMC Helix ITSM using the employee's role, manager, location, and start date.
  2. Provision the approved application groups through connected Okta and request any role exceptions from their owners.
  3. Apply the assigned computer's approved setup through Jamf and track the returned deployment results.
  4. Send the employee their setup instructions and record completed accounts, device details, and remaining physical delivery dependencies.

The result

The digital onboarding work is completed and the service record clearly separates ready systems from outstanding delivery tasks.

Fulfill a request for Salesforce

Finn completes the access-request workflow around Salesforce, carrying the employee's business need through the required decision and the resulting application assignment.

Typically handled byApplication access administration team

Starts when

An employee asks for Salesforce access through BMC Helix ITSM.

What Finn handles

  1. Identify the employee, requested access level, business reason, and applicable service-catalog requirements.
  2. Obtain the required manager or application-owner approval using the organization's approval process.
  3. Apply the approved assignment through connected Okta, which owns the application's user provisioning.
  4. Confirm the assignment result, notify the employee, and complete the BMC Helix ITSM request with the approval and access references.

The result

The employee receives the authorized application access and the service record shows who approved it and what changed.

Complete the digital part of employee departure

Finn follows an approved departure through access removal, device follow-up, and service-record completion so the IT team does not rely on a chain of manual reminder emails.

Typically handled byIT offboarding and identity operations team

Starts when

Workday records an authorized employee departure and its effective time.

What Finn handles

  1. Open the departure workflow in BMC Helix ITSM and identify the employee's accounts, device, and approved timing.
  2. At the effective time, suspend the accounts and revoke supported sessions through connected Okta.
  3. Apply the authorized device action through Jamf, keeping any data-retention or transfer decision with its owner.
  4. Record the returned access and device results, issue equipment-return instructions, and track the physical return separately.

The result

Digital access changes are completed and evidenced, while asset recovery remains visible until the equipment is actually returned.

Carry an approved change through execution and review

Finn manages the operational work around a controlled technology change, keeping the approved scope, execution evidence, and final service result connected in BMC Helix ITSM.

Typically handled byIT change coordinator

Starts when

A service owner requests a routine change with an established implementation procedure.

What Finn handles

  1. Create the change record with affected services, schedule, impact, implementation steps, and the agreed rollback procedure.
  2. Route the change through the required approval path and wait for its authorized execution window.
  3. Start the approved job in connected GitHub Actions or Jamf, whichever owns the change.
  4. Check the job result and service observations, then record the outcome and close or retain the change for its actual exception.

The result

The change has a recorded authorization, execution result, and service assessment instead of an unverified status update.

Run the service-desk response to a shared outage

Finn connects employee reports to the operational incident, keeps affected people informed, and resolves the related service work when the underlying recovery is confirmed.

Typically handled byMajor incident coordinator and service desk

Starts when

Multiple BMC Helix ITSM incidents report the same unavailable business service.

What Finn handles

  1. Group the related reports by service and symptoms, preserving each employee's affected work.
  2. Connect the service incident to PagerDuty for response ownership and Datadog for current service observations.
  3. Send confirmed progress updates and run only the remediation steps authorized by the incident procedure.
  4. After the response system records recovery, check outstanding reports and resolve the BMC Helix ITSM incidents that are settled.

The result

The outage has a coordinated employee response, linked operational evidence, and a documented recovery across affected cases.

Turn repeated incidents into a verified permanent fix

Finn works the operational problem-management cycle behind recurring tickets, connecting the evidence, approved remediation, and follow-up checks instead of repeatedly closing the same symptom.

Typically handled byProblem management and platform operations team

Starts when

Repeated BMC Helix ITSM incidents show the same failure pattern across employees or devices.

What Finn handles

  1. Collect the matching incidents, working temporary fixes, affected assets, and available monitoring evidence.
  2. Create or update the problem investigation with the confirmed findings and the proposed repair owner's decision.
  3. Carry the approved repair through the change process and execute its configured action in Jamf or GitHub Actions.
  4. Check the observations after execution and update the problem and linked incidents with the result.

The result

The recurring problem has a tracked repair and evidence of its outcome, with unresolved causes kept explicit.

Track a replacement device through delivery and setup

Finn handles the coordination around a replacement computer, connecting the service request, asset assignment, shipment updates, and device readiness rather than leaving employees to chase several teams.

Typically handled byIT asset fulfillment coordinator

Starts when

An approved BMC Helix ITSM request calls for a replacement device.

What Finn handles

  1. Match the approved request to available inventory and record the assigned replacement asset.
  2. Create the authorized shipment through connected ShipStation while the fulfillment team performs physical packing and dispatch.
  3. Apply the approved device setup through Jamf and follow both shipment and setup results.
  4. Confirm receipt and the working replacement with the employee, then update asset assignments and record the old device's return status.

The result

The replacement journey is documented through delivery and readiness, with equipment still awaiting return clearly tracked.

Publish the working answer from a resolved incident

Finn turns a proven service resolution into maintained support guidance, keeping the original evidence, review decision, and published answer connected in BMC Helix ITSM.

Typically handled byIT knowledge manager

Starts when

A resolved incident exposes a missing or incorrect answer in the service knowledge base.

What Finn handles

  1. Review the confirmed repair, affected environment, prerequisites, and limitations from the original incident.
  2. Write the reusable procedure without employee-specific details and link it to the supporting resolution.
  3. Obtain the required knowledge-owner review before publishing new or materially changed operational instructions.
  4. Publish the approved guidance and update the original incident or service resource with its article reference.

The result

The knowledge base gains a reviewed procedure based on a completed repair that the support team can reuse.

Finish the routine work in an aging service queue

Finn takes responsibility for stalled requests whose next action is already known, completing the work and leaving real dependencies with a named owner instead of merely summarizing overdue tickets.

Typically handled byService desk queue manager

Starts when

A scheduled queue review finds aging BMC Helix ITSM tickets with missing information or uncompleted routine actions.

What Finn handles

  1. Read each case's history, due date, request type, and the concrete action preventing completion.
  2. Ask focused questions where information is missing and execute already authorized actions through the connected owning system.
  3. Update the requester when work completes and resolve cases supported by an actual result.
  4. For remaining exceptions, record the specific dependency, responsible owner, and agreed next step in BMC Helix ITSM.

The result

The queue contains current obligations and completed resolutions rather than stale tickets that require repeated manual inspection.

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 BMC Helix ITSM.

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 BMC Helix ITSM integration to work.

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

Discuss your workflow Get started