ServiceNow · Arazzo Workflow

ServiceNow Create Trouble Ticket Then Update

Version 1.0.0

Create a trouble ticket, read it back by id, then update its status and severity.

1 workflow 1 source API 1 provider
View Spec View on GitHub AutomationCloud ServicesDigital WorkflowsEnterprise PlatformITSMProcessesT1Workflow-AutomationWorkflowsArazzoWorkflows

Provider

servicenow

Workflows

create-trouble-ticket-then-update
Open a trouble ticket and progress its status.
Creates a trouble ticket, reads it back by id, and updates its status and severity.
3 steps inputs: description, name, newSeverity, newStatus, severity, ticketType outputs: status, ticketId
1
createTicket
Create a trouble ticket record in the Case, Incident, or Service Problem Case table per the supplied ticket type.
2
getTicket
Retrieve the trouble ticket by its id to confirm it persisted before updating it.
3
updateTicket
Update the trouble ticket's status and severity as it progresses.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: ServiceNow Create Trouble Ticket Then Update
  summary: Create a trouble ticket, read it back by id, then update its status and severity.
  description: >-
    The TM Forum-style trouble-ticket lifecycle exposed by ServiceNow over the
    Case, Incident, and Service Problem Case tables. The workflow creates a
    trouble ticket, retrieves it by its returned id to confirm persistence, and
    then updates its status and severity as the ticket progresses. Unlike the
    Table API, the Trouble Ticket API returns each ticket as a flat object
    keyed by id rather than wrapping it under a result object. Every request is
    written inline.
  version: 1.0.0
sourceDescriptions:
- name: troubleTicketApi
  url: ../openapi/servicenow-trouble-ticket-api-openapi.yml
  type: openapi
workflows:
- workflowId: create-trouble-ticket-then-update
  summary: Open a trouble ticket and progress its status.
  description: >-
    Creates a trouble ticket, reads it back by id, and updates its status and
    severity.
  inputs:
    type: object
    required:
    - name
    - ticketType
    properties:
      name:
        type: string
        description: The title of the trouble ticket.
      description:
        type: string
        description: The full description of the trouble ticket.
      severity:
        type: string
        description: The initial severity of the ticket.
      ticketType:
        type: string
        description: The ticket type — one of Case, Incident, or Service Problem Case.
      newStatus:
        type: string
        description: The status to set during the update.
      newSeverity:
        type: string
        description: The severity to set during the update.
  steps:
  - stepId: createTicket
    description: >-
      Create a trouble ticket record in the Case, Incident, or Service Problem
      Case table per the supplied ticket type.
    operationId: createTroubleTicket
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.name
        description: $inputs.description
        severity: $inputs.severity
        ticketType: $inputs.ticketType
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      ticketId: $response.body#/id
  - stepId: getTicket
    description: >-
      Retrieve the trouble ticket by its id to confirm it persisted before
      updating it.
    operationId: getTroubleTicketById
    parameters:
    - name: id
      in: path
      value: $steps.createTicket.outputs.ticketId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      currentStatus: $response.body#/status
  - stepId: updateTicket
    description: >-
      Update the trouble ticket's status and severity as it progresses.
    operationId: updateTroubleTicket
    parameters:
    - name: id
      in: path
      value: $steps.createTicket.outputs.ticketId
    requestBody:
      contentType: application/json
      payload:
        status: $inputs.newStatus
        severity: $inputs.newSeverity
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      ticketId: $response.body#/id
      status: $response.body#/status
      lastUpdate: $response.body#/lastUpdate
  outputs:
    ticketId: $steps.updateTicket.outputs.ticketId
    status: $steps.updateTicket.outputs.status

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/servicenow-create-trouble-ticket-then-update-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.