Update Problem
freshservice.update_problem
ActionBusiness appsconnection required
Calls the Freshservice API with the connection's credentials.
Change the attributes of an existing Freshservice problem.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Freshservice
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- domain, workspace_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
12 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
problem_id The Freshservice problem to act on, by its numeric id. | string | Yes | — | — | 1 |
subject Subject line of the record. | string | No | — | — | Unable to reach the email server |
description Body of the record; Freshservice stores and renders it as HTML. | string | No | — | — | — |
priority Priority: 1 Low, 2 Medium, 3 High, 4 Urgent. | number | No | — | 1–4 | 2 |
status Problem status: 1 Open, 2 Change Requested, 3 Closed. | number | No | — | 1–3 | — |
impact Impact: 1 Low, 2 Medium, 3 High. | number | No | — | 1–3 | — |
due_by When the problem is due, as a UTC timestamp. | string | No | — | iso8601 format | — |
agent_id Numeric id of the agent the record is assigned to. | string | No | — | — | — |
group_id Numeric id of the agent group the record is assigned to. | string | No | — | — | — |
known_error Record the problem as a known error. | boolean | No | — | — | — |
custom_fields Custom field values as a JSON object keyed by the field's Freshservice name. | object | No | — | — | — |
attributes Any other documented attribute for this record, as a JSON object merged into the request. | object | No | — | — | — |
- At least one of subject, description, priority, status, impact, due_by, agent_id, group_id, known_error, custom_fields, attributes must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"priority": 2,
"problem_id": "1",
"subject": "Unable to reach the email server"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id Numeric id of the problem. | number | — |
subject Subject line of the problem. | string | — |
status Status: 1 Open, 2 Change Requested, 3 Closed. | number | — |
priority Priority: 1 Low, 2 Medium, 3 High, 4 Urgent. | number | — |
impact Impact: 1 Low, 2 Medium, 3 High. | number | — |
known_error True when the problem is recorded as a known error. | boolean | — |
requester_id User id of whoever raised the problem. | number | — |
agent_id User id of the agent the problem is assigned to. | number | — |
group_id Id of the agent group the problem is assigned to. | number | — |
due_by When the problem is due. | string | — |
associated_change Id of the change raised from this problem, if any. | number | — |
workspace_id Workspace the problem belongs to. | number | — |
created_at When the problem was created. | string | — |
updated_at When the problem was last updated. | string | — |
{
"agent_id": 0,
"associated_change": 0,
"created_at": "",
"due_by": "",
"group_id": 0,
"id": 0,
"impact": 0,
"known_error": false,
"priority": 0,
"requester_id": 0,
"status": 0,
"subject": "",
"updated_at": "",
"workspace_id": 0
}See Update Problem run in a workflow.
In a technical demo we add the Freshservice connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.