Cross-Provider Workflow

Palo Alto Cortex XDR Incident to GitHub Issue

Version 1.0.0

Pull a Cortex XDR incident with extra data and open a GitHub tracking issue.

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

Providers Orchestrated

palo-alto-networks github

Workflows

xdr-incident-to-issue
Get a Cortex XDR incident and its detail, then open a GitHub issue.
Retrieves incidents from Cortex XDR, pulls extra data for an incident, and creates a GitHub issue to track the investigation.
3 steps inputs: incidentId, owner, repo outputs: issueUrl, severity
1
get-incidents
$sourceDescriptions.cortexXdrApi.getIncidents
Retrieve open incidents from Cortex XDR.
2
get-incident-detail
$sourceDescriptions.cortexXdrApi.getIncidentExtraData
Fetch extended detail for the targeted Cortex XDR incident.
3
open-issue
$sourceDescriptions.githubRepoIssuesApi.createAnIssue
Open a GitHub issue to track the Cortex XDR incident.

Source API Descriptions

Arazzo Workflow Specification

sec-palo-cortex-xdr-incident-to-github-issue.yml Raw ↑
arazzo: 1.0.1
info:
  title: Palo Alto Cortex XDR Incident to GitHub Issue
  summary: Pull a Cortex XDR incident with extra data and open a GitHub tracking issue.
  description: >-
    A security operations workflow that retrieves open incidents from Palo Alto Networks
    Cortex XDR, fetches the extended detail for the most relevant incident, and opens a
    GitHub issue so the engineering team can track investigation and remediation.
    Demonstrates orchestrating an extended detection and response platform with a code host
    in a single Arazzo workflow.
  version: 1.0.0
sourceDescriptions:
  - name: cortexXdrApi
    url: https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/openapi/palo-alto-networks-incidents-api-openapi.yml
    type: openapi
  - name: githubRepoIssuesApi
    url: https://raw.githubusercontent.com/api-evangelist/github/refs/heads/main/openapi/_original/github-repo-issues-api-openapi.yml
    type: openapi
workflows:
  - workflowId: xdr-incident-to-issue
    summary: Get a Cortex XDR incident and its detail, then open a GitHub issue.
    description: >-
      Retrieves incidents from Cortex XDR, pulls extra data for an incident, and creates a
      GitHub issue to track the investigation.
    inputs:
      type: object
      properties:
        incidentId:
          type: string
        owner:
          type: string
        repo:
          type: string
    steps:
      - stepId: get-incidents
        description: Retrieve open incidents from Cortex XDR.
        operationId: $sourceDescriptions.cortexXdrApi.getIncidents
        requestBody:
          contentType: application/json
          payload:
            request_data:
              filters: []
        successCriteria:
          - condition: $statusCode == 200
        outputs:
          totalCount: $response.body#/reply/total_count
      - stepId: get-incident-detail
        description: Fetch extended detail for the targeted Cortex XDR incident.
        operationId: $sourceDescriptions.cortexXdrApi.getIncidentExtraData
        requestBody:
          contentType: application/json
          payload:
            request_data:
              incident_id: $inputs.incidentId
        successCriteria:
          - condition: $statusCode == 200
        outputs:
          severity: $response.body#/reply/incident/severity
          description: $response.body#/reply/incident/description
      - stepId: open-issue
        description: Open a GitHub issue to track the Cortex XDR incident.
        operationId: $sourceDescriptions.githubRepoIssuesApi.createAnIssue
        parameters:
          - name: owner
            in: path
            value: $inputs.owner
          - name: repo
            in: path
            value: $inputs.repo
        requestBody:
          contentType: application/json
          payload:
            title: Cortex XDR incident requires investigation
            body: A Cortex XDR incident was detected and needs engineering follow-up.
            labels:
              - security
              - incident
        successCriteria:
          - condition: $statusCode == 201
        outputs:
          issueNumber: $response.body#/number
          issueUrl: $response.body#/html_url
    outputs:
      severity: $steps.get-incident-detail.outputs.severity
      issueUrl: $steps.open-issue.outputs.issueUrl

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/sec-palo-cortex-xdr-incident-to-github-issue"
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.