Cross-Provider Workflow

Jira Issue Transition to Slack Notification

Version 1.0.0

Look up a Jira issue, transition its status, then notify Slack.

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

Providers Orchestrated

jira slack

Workflows

transition-notify
Fetch a Jira issue, transition it, then post to Slack.
Fetches a Jira issue by key, applies a workflow transition to it, and posts the status change to a Slack channel.
3 steps inputs: issueKey, slackChannel, transitionId outputs: issueKey, messageTs, transitionStatus
1
get-issue
$sourceDescriptions.jiraApi.getIssue
Fetch the Jira issue to confirm it exists and read its fields.
2
transition-issue
$sourceDescriptions.jiraApi.doTransition
Apply a workflow transition to the Jira issue.
3
notify-slack
$sourceDescriptions.slackChat.postChatPostmessage
Post the status change to a Slack channel.

Source API Descriptions

Arazzo Workflow Specification

itsm-ticket-to-jira-transition-notify.yml Raw ↑
arazzo: 1.0.1
info:
  title: Jira Issue Transition to Slack Notification
  summary: Look up a Jira issue, transition its status, then notify Slack.
  description: >-
    A cross-provider ITSM workflow that fetches a Jira issue, advances it through
    a workflow transition such as starting work or resolving, and notifies the
    team's Slack channel of the status change. Demonstrates orchestrating an issue
    tracker with a team messaging provider across an issue's lifecycle in a single
    Arazzo workflow.
  version: 1.0.0
sourceDescriptions:
  - name: jiraApi
    url: https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-cloud-platform-rest-api-openapi.yml
    type: openapi
  - name: slackChat
    url: https://raw.githubusercontent.com/api-evangelist/slack/refs/heads/main/openapi/slack-chat-openapi.yml
    type: openapi
workflows:
  - workflowId: transition-notify
    summary: Fetch a Jira issue, transition it, then post to Slack.
    description: >-
      Fetches a Jira issue by key, applies a workflow transition to it, and posts
      the status change to a Slack channel.
    inputs:
      type: object
      properties:
        issueKey:
          type: string
        transitionId:
          type: string
        slackChannel:
          type: string
    steps:
      - stepId: get-issue
        description: Fetch the Jira issue to confirm it exists and read its fields.
        operationId: $sourceDescriptions.jiraApi.getIssue
        parameters:
          - name: issueIdOrKey
            in: path
            value: $inputs.issueKey
        successCriteria:
          - condition: $statusCode == 200
        outputs:
          issueId: $response.body#/id
          issueKey: $response.body#/key
      - stepId: transition-issue
        description: Apply a workflow transition to the Jira issue.
        operationId: $sourceDescriptions.jiraApi.doTransition
        parameters:
          - name: issueIdOrKey
            in: path
            value: $steps.get-issue.outputs.issueKey
        requestBody:
          contentType: application/json
          payload:
            transition:
              id: $inputs.transitionId
        successCriteria:
          - condition: $statusCode == 204
        outputs:
          transitionStatus: $statusCode
      - stepId: notify-slack
        description: Post the status change to a Slack channel.
        operationId: $sourceDescriptions.slackChat.postChatPostmessage
        requestBody:
          contentType: application/x-www-form-urlencoded
          payload:
            channel: $inputs.slackChannel
            text: A Jira issue has changed status.
        successCriteria:
          - condition: $statusCode == 200
        outputs:
          messageTs: $response.body#/ts
    outputs:
      issueKey: $steps.get-issue.outputs.issueKey
      transitionStatus: $steps.transition-issue.outputs.transitionStatus
      messageTs: $steps.notify-slack.outputs.messageTs