What you can automate with BMC Remedy

Drag any of these 17 actions into a process — no code, no API wrangling.

Create Change Request

Create a change on CHG:Infrastructure Change

Create Entry

Create an entry on any form. Body must be {"values": {...field map...}}

Create Incident

Create an incident on HPD:Help Desk. Body must be {"values": {"Description": ..., "Status": "New", ...}}

Create Problem

Create a problem investigation on PBM:Problem Investigation

Delete Entry

Delete an entry by ID

Get Attachment

Download an attachment from a field on an entry

Get Entry

Get a single entry by ID from any form

Get Form Schema

Retrieve field definitions for a form

Login

Re-authenticate and refresh the AR-JWT token

Logout

Invalidate the current AR-JWT token on the server

Query Assets

Query AST:Asset (or the BMC_BaseElement CMDB form) with a qualification

Query Change Requests

Query CHG:Infrastructure Change with a qualification

Query Entries

Query a Remedy form. Use 'q' for the qualification (e.g. q='Status'="Open" AND 'Priority'<3) and 'fields' to project columns (e.g. fields=values(Incident Number,Status))

Query Incidents

Query HPD:Help Desk with a qualification (q param)

Query Problems

Query PBM:Problem Investigation with a qualification

Update Entry

Update an entry by ID. Body must be {"values": {...field map...}}

Update Incident

Update an HPD:Help Desk entry by ID

How the BMC Remedy connection works

1. Authenticate

BMC Remedy uses aPI token. Save the connection once and reuse it across every process.

2. Build the process

Drop BMC Remedy steps onto the process map alongside desktop, browser, Excel and email steps.

3. Run it attended or unattended

Trigger on a schedule, an email, or a file landing in a folder. Credentials stay encrypted and every run is audited.

Because BMC Remedy has an API, Automize talks to it directly in the cloud — no bot needed on a desktop. Where a system has no API, an Automize bot drives its interface instead.

BMC Remedy Integration