Cross-Provider Workflow

ServiceNow Trouble Ticket to Jira to Email

Version 1.0.0

Open a ServiceNow trouble ticket, create a Jira issue, then email stakeholders.

1 workflow 3 source APIs 3 providers
View Spec View on GitHub ArazzoWorkflowsCross-Provider

Providers Orchestrated

servicenow jira sendgrid

Workflows

trouble-to-jira-email
Create a trouble ticket, open a Jira issue, then email stakeholders.
Creates a ServiceNow trouble ticket, opens a Jira issue referencing it, and emails stakeholders a summary of the new ticket and issue via SendGrid.
3 steps inputs: description, fromEmail, jiraProjectKey, name, stakeholderEmail outputs: emailStatus, issueKey, troubleTicketId
1
create-trouble-ticket
$sourceDescriptions.servicenowTrouble.createTroubleTicket
Log a new ServiceNow trouble ticket.
2
create-issue
$sourceDescriptions.jiraApi.createIssue
Open a Jira issue referencing the trouble ticket.
3
email-stakeholders
$sourceDescriptions.sendgridMail.SendMail
Email stakeholders a summary via SendGrid.

Source API Descriptions

Arazzo Workflow Specification

itsm-trouble-ticket-to-jira-to-email.yml Raw ↑
arazzo: 1.0.1
info:
  title: ServiceNow Trouble Ticket to Jira to Email
  summary: Open a ServiceNow trouble ticket, create a Jira issue, then email stakeholders.
  description: >-
    A cross-provider ITSM workflow that logs a ServiceNow trouble ticket, opens a
    corresponding Jira engineering issue, and emails stakeholders a summary of the
    new ticket and issue via SendGrid. Demonstrates orchestrating an enterprise
    ITSM platform, an issue tracker, and a transactional email provider in a
    single Arazzo workflow.
  version: 1.0.0
sourceDescriptions:
  - name: servicenowTrouble
    url: https://raw.githubusercontent.com/api-evangelist/servicenow/refs/heads/main/openapi/servicenow-trouble-ticket-api-openapi.yml
    type: openapi
  - name: jiraApi
    url: https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-issues-api-openapi.yml
    type: openapi
  - name: sendgridMail
    url: https://raw.githubusercontent.com/api-evangelist/sendgrid/refs/heads/main/openapi/sendgrid-mail-send-api-openapi.yml
    type: openapi
workflows:
  - workflowId: trouble-to-jira-email
    summary: Create a trouble ticket, open a Jira issue, then email stakeholders.
    description: >-
      Creates a ServiceNow trouble ticket, opens a Jira issue referencing it, and
      emails stakeholders a summary of the new ticket and issue via SendGrid.
    inputs:
      type: object
      properties:
        name:
          type: string
        description:
          type: string
        jiraProjectKey:
          type: string
        stakeholderEmail:
          type: string
        fromEmail:
          type: string
    steps:
      - stepId: create-trouble-ticket
        description: Log a new ServiceNow trouble ticket.
        operationId: $sourceDescriptions.servicenowTrouble.createTroubleTicket
        requestBody:
          contentType: application/json
          payload:
            name: $inputs.name
            description: $inputs.description
            priority: High
        successCriteria:
          - condition: $statusCode == 201
        outputs:
          troubleTicketId: $response.body#/id
      - stepId: create-issue
        description: Open a Jira issue referencing the trouble ticket.
        operationId: $sourceDescriptions.jiraApi.createIssue
        requestBody:
          contentType: application/json
          payload:
            fields:
              project:
                key: $inputs.jiraProjectKey
              summary: $inputs.name
              description: $inputs.description
              issuetype:
                name: Bug
        successCriteria:
          - condition: $statusCode == 201
        outputs:
          issueKey: $response.body#/key
      - stepId: email-stakeholders
        description: Email stakeholders a summary via SendGrid.
        operationId: $sourceDescriptions.sendgridMail.SendMail
        requestBody:
          contentType: application/json
          payload:
            personalizations:
              - to:
                  - email: $inputs.stakeholderEmail
                subject: New trouble ticket and Jira issue opened
            from:
              email: $inputs.fromEmail
            content:
              - type: text/plain
                value: A trouble ticket has been logged and a Jira issue opened.
        successCriteria:
          - condition: $statusCode == 202
        outputs:
          emailStatus: $statusCode
    outputs:
      troubleTicketId: $steps.create-trouble-ticket.outputs.troubleTicketId
      issueKey: $steps.create-issue.outputs.issueKey
      emailStatus: $steps.email-stakeholders.outputs.emailStatus

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/itsm-trouble-ticket-to-jira-to-email"
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.