GitHub · Arazzo Workflow

GitHub Create Organization Repository and Open First Issue

Version 1.0.0

Create a repository inside an organization and open its first tracking issue.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub CodePipelinesPlatformSoftware DevelopmentSource ControlT1ArazzoWorkflows

Provider

github

Workflows

create-org-repository-and-issue
Create an organization repository then open a first issue in it.
Creates a repository owned by an organization and chains the returned owner and repository name into a follow-up call that opens the first issue.
2 steps inputs: description, githubToken, issueBody, issueTitle, name, org, private outputs: issueNumber, issueUrl, repositoryUrl
1
createOrgRepository
Create a new repository owned by the organization, initialized with a README so the default branch is created.
2
openFirstIssue
Open the first issue in the newly created organization repository using the owner and repository name returned by the create step.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: GitHub Create Organization Repository and Open First Issue
  summary: Create a repository inside an organization and open its first tracking issue.
  description: >-
    The organization equivalent of bootstrapping a new project. The workflow
    creates a repository owned by a named organization (auto initialized so the
    default branch exists), then opens a first issue in that repository to track
    initial work. Every step spells out its request inline so the flow can be
    read and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: issuesApi
  url: ../openapi/github-issues-api-openapi.yml
  type: openapi
- name: reposApi
  url: ../openapi/github-repos-api-openapi.yml
  type: openapi
workflows:
- workflowId: create-org-repository-and-issue
  summary: Create an organization repository then open a first issue in it.
  description: >-
    Creates a repository owned by an organization and chains the returned owner
    and repository name into a follow-up call that opens the first issue.
  inputs:
    type: object
    required:
    - githubToken
    - org
    - name
    - issueTitle
    properties:
      githubToken:
        type: string
        description: A GitHub token with repo and org scope, passed as a Bearer credential.
      org:
        type: string
        description: The login of the organization that will own the repository.
      name:
        type: string
        description: The name of the repository to create.
      description:
        type: string
        description: A short description of the repository.
      private:
        type: boolean
        description: Whether the repository is private.
      issueTitle:
        type: string
        description: The title of the first issue to open.
      issueBody:
        type: string
        description: The body of the first issue to open.
  steps:
  - stepId: createOrgRepository
    description: >-
      Create a new repository owned by the organization, initialized with a
      README so the default branch is created.
    operationId: repos/create-in-org
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.githubToken
    - name: org
      in: path
      value: $inputs.org
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.name
        description: $inputs.description
        private: $inputs.private
        auto_init: true
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      ownerLogin: $response.body#/owner/login
      repoName: $response.body#/name
      htmlUrl: $response.body#/html_url
  - stepId: openFirstIssue
    description: >-
      Open the first issue in the newly created organization repository using
      the owner and repository name returned by the create step.
    operationId: issues/create
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.githubToken
    - name: owner
      in: path
      value: $steps.createOrgRepository.outputs.ownerLogin
    - name: repo
      in: path
      value: $steps.createOrgRepository.outputs.repoName
    requestBody:
      contentType: application/json
      payload:
        title: $inputs.issueTitle
        body: $inputs.issueBody
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      issueNumber: $response.body#/number
      issueUrl: $response.body#/html_url
  outputs:
    repositoryUrl: $steps.createOrgRepository.outputs.htmlUrl
    issueNumber: $steps.openFirstIssue.outputs.issueNumber
    issueUrl: $steps.openFirstIssue.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/github-create-org-repository-and-issue-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.