Update Schedule Rotation
Update the participants and time restrictions of a specific schedule rotation.
Make sure that the API key that's used to create the Opsgenie connection for this card is not team-specific. Otherwise, any input value in the Team ID or Team Name fields on this card will not override the team that's specified by a team-specific API key. It is recommended to create and manage API keys on the Opsgenie API key management page.
Options
| Field | Definition | Type | Required |
|---|---|---|---|
|
Schedule Identifier |
Type of schedule identifier for the team. Choose one of the following options:
|
Dropdown | TRUE |
|
Update Time Restriction? |
Specify if time restriction is updated. Choose one of the following options:
|
Dropdown | TRUE |
Input
These fields are dynamically generated based on the fields selected in Options.
| Field | Definition | Type | Required |
|---|---|---|---|
|
Rotation |
|||
|
Schedule ID |
Unique ID of the schedule. This field displays when |
Text | TRUE |
|
Schedule Name |
Name of the schedule. This field displays when |
Text | TRUE |
|
Rotation ID |
Unique ID of schedule rotation. |
Text | TRUE |
|
Name |
Name of the rotation. |
Text | FALSE |
|
Start Date |
Start date of the rotation. Date format as |
Date & Time | FALSE |
|
End Date |
End date of the rotation. Date format as |
Date & Time | FALSE |
|
Type |
Duration of rotation. Choose one of the following options:
|
Dropdown | FALSE |
|
Length |
Length of the rotation. Default value is 1. |
Number | FALSE |
|
Merge Participants? |
Indicates whether to merge the existing participants list with the input list. Choose one of the following options:
|
Dropdown | FALSE |
|
Participants |
List of escalations, teams, users or none which are used in a schedule. Each of them can be used multiple times and will be rotated in the order they are given. For user and team, optionally define ID or username properties. For example:
|
Array of Objects |
FALSE |
|
Time Restrictions |
Used to limit schedule rotation to a certain day and time of the week, using multiple start and end times for each day of the week. This allows for applying different scheduling rotations at different times. This field displays when |
Object | TRUE |
|
When Note: Hours are rounded down, and minutes are rounded to the closest 00/30. |
Number | TRUE | |
|
startHour - 0 to 23 |
Number | TRUE | |
|
startMinute - 00 or 30 |
Number | TRUE | |
|
endHour - 0 to 23 |
Number | TRUE | |
|
endMinute - 00 or 30 |
Number | TRUE | |
|
For example:
|
|||
|
When Note: Both day and time options are required. |
Array of Objects |
TRUE | |
|
startDay: monday to sunday |
Text | TRUE | |
|
startHour: 0 to 23 |
Number | TRUE | |
|
startMinute: 00 or 30 |
Number | TRUE | |
|
endDay: monday to sunday |
Text | TRUE | |
|
endHour: 0 to 23 |
Number | TRUE | |
|
endMinute: 00 or 30 |
Number | TRUE | |
|
For example:
|
|||
Output
| Field | Definition | Type |
|---|---|---|
|
Status Code |
Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example:
For a full list of possible status codes, see HTTP status codes. |
Number |
|
Result |
Result of the API call. For example, |
Text |