Overview
LogicGate Risk Cloud is a configurable GRC workflow platform. The Automize connector reads the structure a tenant has built — applications, workflows, steps, fields and workflow maps — and creates, reads, updates and progresses the records that move through it.
Setting up the connection
Auth type: login_exchange.
- Get the environment subdomain from the Risk Cloud URL: for https://acme.logicgate.com it is acme. Sandbox tenants usually carry their own subdomain.
- In Risk Cloud, create an API key pair. It has two halves — a Client key and a Secret key.
- In Automize, open Settings → Connectors → LogicGate Risk Cloud → Add connection and paste both halves. Automize exchanges them for a short-lived bearer token on each run.
- Leave the optional pre-issued token blank in normal use. Risk Cloud tokens are short-lived, so a pasted one stops working and the exchange is what keeps a scheduled process running.
Available operations
18 operations available. Click any row to jump to its detail.
| Operation | Category | What it does |
|---|---|---|
| Create Record | General | Create a record on a step, optionally with field values and an assignee. fields is a list of {fieldId, values:[...]} — every value is a STRING, including booleans and numbers. |
| Get Application | General | Get one application by its ID |
| Get Record | General | Get one record by its ID |
| Get Step | General | Get one step by its ID |
| Get Workflow | General | Get one workflow by its ID |
| List Access Audits | General | List access-audit entries |
| List Applications | General | List applications the API user has Build access to |
| List Fields | General | List field definitions — the source of the fieldId values a record write needs |
| List Linked Records | General | List the records linked to a given record |
| List Records | General | List records the API user can read. Filter with application-id, workflow-id, step-id or updated-min (epoch milliseconds). |
| List Steps | General | List steps, optionally scoped to one workflow |
| List Workflow Maps | General | List workflow maps (how workflows relate to one another) |
| List Workflows | General | List workflows, optionally scoped to one application |
| Login | General | Re-authenticate with the key pair and refresh the bearer token |
| Move Record (force) | General | Force a record onto another step WITHOUT validating required fields. Use progress_record when the workflow's own validation should apply. |
| Progress Record (validated) | General | Advance a record along its workflow, honouring required-field validation. Refused if the record is incomplete — that refusal is the point. |
| Search Records by Field Value | General | Find records whose field holds a given text or numeric value (v1) |
| Update Record | General | Update a record's field values. The body is a bare LIST of {"fieldId": "...", "values": ["..."]} — not an object. |
Operations
Create Record
Create a record on a step, optionally with field values and an assignee. fields is a list of {fieldId, values:[...]} — every value is a STRING, including booleans and numbers.
| Parameter | Required | Type | Description |
|---|---|---|---|
Step ID stepId | Yes | string | |
Assignee email assigneeEmailAddress | No | string | Email address of the Risk Cloud user to assign the new record to. |
Due date recordDueDate | No | string | Epoch seconds, or 'MM-DD-YY HH:MM:SS'. |
Field values fields | No | list | List of {"fieldId": "...", "values": ["..."]}. Values are always strings. |
Get Application
Get one application by its ID
| Parameter | Required | Type | Description |
|---|---|---|---|
Application ID id | Yes | string |
Get Record
Get one record by its ID
| Parameter | Required | Type | Description |
|---|---|---|---|
Record ID id | Yes | string |
Get Step
Get one step by its ID
| Parameter | Required | Type | Description |
|---|---|---|---|
Step ID id | Yes | string |
Get Workflow
Get one workflow by its ID
| Parameter | Required | Type | Description |
|---|---|---|---|
Workflow ID id | Yes | string |
List Access Audits
List access-audit entries
No input parameters.
List Applications
List applications the API user has Build access to
No input parameters.
List Fields
List field definitions — the source of the fieldId values a record write needs
No input parameters.
List Linked Records
List the records linked to a given record
| Parameter | Required | Type | Description |
|---|---|---|---|
Record ID id | Yes | string |
List Records
List records the API user can read. Filter with application-id, workflow-id, step-id or updated-min (epoch milliseconds).
| Parameter | Required | Type | Description |
|---|---|---|---|
Application ID application-id | No | string | |
Workflow ID workflow-id | No | string | |
Step ID step-id | No | string | |
Updated since (epoch ms) updated-min | No | string | Milliseconds since the Unix epoch. Only records modified after this are returned. |
List Steps
List steps, optionally scoped to one workflow
No input parameters.
List Workflow Maps
List workflow maps (how workflows relate to one another)
No input parameters.
List Workflows
List workflows, optionally scoped to one application
No input parameters.
Login
Re-authenticate with the key pair and refresh the bearer token
| Parameter | Required | Type | Description |
|---|---|---|---|
Client key client_key | No | string | |
Secret key secret_key | No | password |
Move Record (force)
Force a record onto another step WITHOUT validating required fields. Use progress_record when the workflow's own validation should apply.
| Parameter | Required | Type | Description |
|---|---|---|---|
Record ID record-id | Yes | string | |
Target step ID step-id | Yes | string |
Progress Record (validated)
Advance a record along its workflow, honouring required-field validation. Refused if the record is incomplete — that refusal is the point.
| Parameter | Required | Type | Description |
|---|---|---|---|
Workflow ID workflowId | Yes | string | |
Target step ID stepId | Yes | string | |
Record ID record-id | Yes | string | |
Application ID application-id | Yes | string | |
Assignee user ID userId | No | string | Risk Cloud user id to assign the record to on arrival. Left unset, the step's own assignment rules apply. |
Target step type stepType | No | string |
Search Records by Field Value
Find records whose field holds a given text or numeric value (v1)
| Parameter | Required | Type | Description |
|---|---|---|---|
Field ID field | Yes | string | |
Text value textValue | No | string | |
Numeric value numericValue | No | number |
Update Record
Update a record's field values. The body is a bare LIST of {"fieldId": "...", "values": ["..."]} — not an object.
| Parameter | Required | Type | Description |
|---|---|---|---|
Record ID record-id | Yes | string | |
Field values fields | Yes | list | List of {"fieldId": "...", "values": ["..."]}. Values are always strings. |
FAQ
- What is the difference between Move Record and Progress Record?
- Progress Record (validated) advances a record the way the UI does — Risk Cloud runs the step's validation first and refuses the move if the record does not satisfy it. Move Record (force) puts the record on a step regardless. Prefer the validated one; reach for force only when deliberately repairing a stuck record.