manage_change
Create, update, close, list, and move change requests in Freshservice, with options to filter, sort, and retrieve change fields.
Instructions
Unified change operations.
Args:
action: One of 'create', 'update', 'delete', 'get', 'list', 'filter',
'close', 'move', 'get_fields'
change_id: Required for get, update, delete, close, move
requester_id: Initiator ID (create — MANDATORY)
subject: Change subject (create — MANDATORY)
description: HTML description (create — MANDATORY)
priority: 1=Low, 2=Medium, 3=High, 4=Urgent
impact: 1=Low, 2=Medium, 3=High
status: 1=Open, 2=Planning, 3=Awaiting Approval, 4=Pending Release,
5=Pending Review, 6=Closed
risk: 1=Low, 2=Medium, 3=High, 4=Very High
change_type: 1=Minor, 2=Standard, 3=Major, 4=Emergency
group_id: Agent group ID
agent_id: Agent ID
department_id: Department ID
category: Category string
sub_category: Sub-category string
item_category: Item category string
planned_start_date: ISO datetime
planned_end_date: ISO datetime
reason_for_change: Planning field — reason (text/HTML)
change_impact: Planning field — impact analysis (text/HTML)
rollout_plan: Planning field — rollout plan (text/HTML)
backout_plan: Planning field — backout plan (text/HTML)
custom_fields: Custom fields dict
assets: Assets list (associated CIs), e.g. [{"display_id": 1}]
impacted_services: Impacted services list, e.g. [{"display_id": 167456}]
NOTE: This is different from 'assets'. Assets = associated CIs,
impacted_services = business services affected by the change.
maintenance_window_id: Maintenance Window ID to associate with
this Change. On create, applied via follow-up PUT. On update,
sent as {"maintenance_window": {"id": <value>}}.
Use this to link a Change to an existing Maintenance Window.
change_result_explanation: Result explanation (close)
workspace_id: Target workspace (move / list / filter)
query: Filter query string (list/filter)
view: View name or ID (list)
sort: Sort field (list)
order_by: 'asc' or 'desc' (list)
updated_since: ISO datetime (list)
page: Page number
per_page: Items per page 1-100
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| risk | No | ||
| sort | No | ||
| view | No | ||
| query | No | ||
| action | Yes | ||
| assets | No | ||
| impact | No | ||
| status | No | ||
| subject | No | ||
| agent_id | No | ||
| category | No | ||
| group_id | No | ||
| order_by | No | ||
| per_page | No | ||
| priority | No | ||
| change_id | No | ||
| change_type | No | ||
| description | No | ||
| backout_plan | No | ||
| requester_id | No | ||
| rollout_plan | No | ||
| sub_category | No | ||
| workspace_id | No | ||
| change_impact | No | ||
| custom_fields | No | ||
| department_id | No | ||
| item_category | No | ||
| updated_since | No | ||
| planned_end_date | No | ||
| impacted_services | No | ||
| reason_for_change | No | ||
| planned_start_date | No | ||
| maintenance_window_id | No | ||
| change_result_explanation | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |