The following doc contains input context available for each ticket gateway actions. Refer to the configuration guide to learn how to use it.
Requestor info is a class in Moveworks which stores the end users details. This allows you fetch ITSM related information for that user.
Example :
Input
ticket_id (string)Output
raw_ticketInput
requestor (User)
updated_start_ts (string)
Example: 2026-01-05T10:30:45.123456Z
updated_end_ts (string)
Example: 2026-01-05T10:30:45.123456Z
destination (dict)
Example: { "table_name": "test-table-name" }
Output
raw_ticketsInput
updated_start_ts (string)
Example: 2026-01-05T10:30:45.123456Z
updated_end_ts (string)
Example: 2026-01-05T10:30:45.123456Z
destination (dict)
Example: { "table_name": "test-table-name" }
Output
raw_ticketsInput
updated_start_ts (string)
Example: 2026-01-05T10:30:45.123456Z
updated_end_ts (string)
Example: 2026-01-05T10:30:45.123456Z
destination (dict)
Example: { "table_name": "test-table-name" }
pagination_info (dict)
Output
raw_ticketsInput
destination (dict)
Example: { "table_name": "test-table-name" }
payload (dict)
Example:
Output
raw_ticketInput
ticket (dict)
destination (dict)
Example: { "table_name": "test-table-name" }
payload (dict)
Output
raw_ticketInput
ticket (dict)payload as below:Output
raw_ticketInput
ticket (dict)
destination (dict)
Example: { "table_name": "test-table-name" }
payload as below:
Output
raw_ticketInput
ticket (dict)payload as below:Output
raw_ticketInput
ticket (dict)payload as below:Output
raw_ticketBoth add comment and add worknote will use post note ticket action.
comment or work_note will be populated in the context based on the action and will be identified with the flag is_comment which will be True for comment and false for work_note.
Input
ticket (dict)user ( User ) will only be present if there is user impersonation.payload as below:Output
raw_ticketInput context :
Input args :
File mapper in HTTP action :
Post process ticket action is used to add/update fields in ticket proto.
In context of ticket gateway, you’re provided with ticket proto and using the http_actions one can update the ticket and send back to internal service.
Example: define http_action to fetch comments for a ticket and map it to activity_log of ticket proto.
Input : Ticket ( dict )
Output : Ticket under the key raw_ticket
Tip: If your ITSM system doesn’t require any update on ticket. You’re still required to define this action as this is necessary for other query ticket actions. Just add fetch ticket http action and send back the ticket in input context
Ticket proto fields