Gitea · Arazzo Workflow

Gitea Provision Organization Repository With Webhook

Version 1.0.0

Create an organization, add a repository to it, and register a webhook.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub GitSource ControlDevOpsCI/CDCode HostingOpen-SourceSelf-HostedPackage RegistryIssue TrackingPull RequestsArazzoWorkflows

Provider

gitea

Workflows

org-repo-with-webhook
Create an org, create a repo in it, and register a webhook.
Creates an organization, creates a repository under it, then registers a gitea-type webhook on the repository.
3 steps inputs: authToken, orgFullName, orgUsername, repoDescription, repoName, webhookUrl outputs: hookId, orgId, repoId
1
createOrg
Create a new organization.
2
createOrgRepo
Create a repository owned by the new organization.
3
createWebhook
Register a gitea-type webhook on the new repository.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Gitea Provision Organization Repository With Webhook
  summary: Create an organization, add a repository to it, and register a webhook.
  description: >-
    Stands up a new organization workspace on Gitea. The workflow creates an
    organization, creates a repository owned by that organization, and registers
    a webhook on the repository so external systems receive push and pull
    request events. Each 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: organizationApi
  url: ../openapi/gitea-organization-api-openapi.yml
  type: openapi
- name: repositoryApi
  url: ../openapi/gitea-repository-api-openapi.yml
  type: openapi
workflows:
- workflowId: org-repo-with-webhook
  summary: Create an org, create a repo in it, and register a webhook.
  description: >-
    Creates an organization, creates a repository under it, then registers a
    gitea-type webhook on the repository.
  inputs:
    type: object
    required:
    - authToken
    - orgUsername
    - repoName
    - webhookUrl
    properties:
      authToken:
        type: string
        description: Authorization header value, e.g. "token <personal-access-token>".
      orgUsername:
        type: string
        description: Username (slug) of the organization to create.
      orgFullName:
        type: string
        description: Display name of the organization.
      repoName:
        type: string
        description: Name of the repository to create under the organization.
      repoDescription:
        type: string
        description: Description of the repository.
      webhookUrl:
        type: string
        description: Target URL the webhook delivers payloads to.
  steps:
  - stepId: createOrg
    description: Create a new organization.
    operationId: orgCreate
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authToken
    requestBody:
      contentType: application/json
      payload:
        username: $inputs.orgUsername
        full_name: $inputs.orgFullName
        visibility: public
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      orgId: $response.body#/id
      orgName: $response.body#/username
  - stepId: createOrgRepo
    description: Create a repository owned by the new organization.
    operationId: createOrgRepo
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authToken
    - name: org
      in: path
      value: $inputs.orgUsername
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.repoName
        description: $inputs.repoDescription
        auto_init: true
        private: false
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      repoId: $response.body#/id
      repoFullName: $response.body#/full_name
  - stepId: createWebhook
    description: Register a gitea-type webhook on the new repository.
    operationId: repoCreateHook
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authToken
    - name: owner
      in: path
      value: $inputs.orgUsername
    - name: repo
      in: path
      value: $inputs.repoName
    requestBody:
      contentType: application/json
      payload:
        type: gitea
        active: true
        events:
        - push
        - pull_request
        config:
          url: $inputs.webhookUrl
          content_type: json
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      hookId: $response.body#/id
  outputs:
    orgId: $steps.createOrg.outputs.orgId
    repoId: $steps.createOrgRepo.outputs.repoId
    hookId: $steps.createWebhook.outputs.hookId

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/gitea-org-repo-with-webhook-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.