Community managed lightweight code hosting solution written in Go
Community managed lightweight code hosting solution written in Go On Nagent, Gitea is exposed as a fully-configurable developer tools integration that any agent can call — 19 actions, and API key authentication. No code is required to wire Gitea into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Gitea to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Gitea into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Gitea, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GITEA_ACTIVITYPUB_PERSONTool to retrieve the ActivityPub Person actor for a Gitea user. Use when you need to fetch a user's ActivityPub representation for federation purposes or to get ActivityStreams-formatted user data.
Input parameters
The numeric user ID of the Gitea user whose ActivityPub Person actor should be retrieved
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_GENERAL_API_SETTINGSTool to retrieve the Gitea instance's global API settings including pagination limits and response size constraints. Use when you need to understand API rate limits or configuration parameters.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_GENERAL_ATTACHMENT_SETTINGSTool to retrieve the Gitea instance's global settings for file attachments including enabled status, allowed file types, size limits, and file count limits. Use when you need to understand the attachment configuration of the instance.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_GENERAL_REPOSITORY_SETTINGSTool to retrieve the Gitea instance's global settings for repositories including feature flags for mirroring, HTTP Git, migrations, stars, time tracking, and LFS. Use when you need to understand which repository features are enabled or disabled at the instance level.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_GENERAL_UI_SETTINGSTool to retrieve the Gitea instance's global settings for UI including default theme, allowed reactions, and custom emojis. Use when you need to understand the UI configuration of the instance.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_GITIGNORE_TEMPLATE_INFOTool to retrieve information about a specific gitignore template. Use when you need the content of a gitignore template for repository creation or configuration.
Input parameters
Name of the gitignore template to retrieve (e.g., 'Go', 'Python', 'Node', 'Java').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_LABEL_TEMPLATE_INFOTool to retrieve all labels from a specific label template. Use when you need to view the predefined label set for repository configuration.
Input parameters
The name of the label template to retrieve (e.g., 'Default', 'Advanced'). This is the template identifier. Common templates include 'Default' and 'Advanced'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_LICENSE_TEMPLATE_INFOTool to retrieve information about a specific license template. Use when you need the content and details of a license template for repository creation or configuration.
Input parameters
The name of the license template to retrieve. This should be the unique identifier for the license (e.g., 'mit', 'apache-2.0', 'gpl-3.0').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_NODE_INFOTool to retrieve the nodeinfo of the Gitea application. Use when you need standardized metadata about the Gitea server following the NodeInfo specification.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_SIGNING_KEYTool to retrieve the default GPG signing key used by Gitea to sign commits. Use when you need to verify commits signed by the Gitea instance or import the public key to trust Gitea-generated commits.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_GET_VERSIONTool to retrieve the version of the Gitea application. Use when you need to check the Gitea server version.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_LIST_GITIGNORE_TEMPLATESTool to retrieve all available gitignore templates. Use when creating a repository to select an appropriate .gitignore template.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_LIST_LABEL_TEMPLATESTool to retrieve all available label templates. Use when you need to discover which predefined label sets are available for repositories.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_LIST_LICENSE_TEMPLATESTool to retrieve all available license templates. Use when creating a repository to select an appropriate license template.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_ORG_GET_ALLTool to retrieve a paginated list of all organizations in the Gitea instance. Use when you need to list all organizations or browse organizations with pagination support.
Input parameters
Page number of results to return (1-based). If not specified, returns the first page.
Page size of results (number of organizations per page). If not specified, uses server default.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_ORG_LIST_ACTIONS_SECRETSTool to list all action secrets for an organization. Use when you need to retrieve the list of secrets configured at the organization level. Note that secret values are never returned through the API for security purposes.
Input parameters
Name of the organization
Page number of results to return (1-based). Default pagination starts at page 1.
Page size of results (number of items per page). Default is typically 50.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_RENDER_MARKDOWNTool to render a markdown document as HTML with configurable rendering modes and context. Use when you need to convert markdown to HTML with specific rendering contexts like comments, wiki pages, or files.
Input parameters
Rendering mode that specifies the context for rendering. Options: 'markdown' (default/standard), 'comment' (for issues/pull requests), 'wiki' (wiki pages), 'file' (file content).
The markdown content to be rendered into HTML. Supports standard markdown syntax.
DEPRECATED: Legacy flag indicating wiki page content. Use mode='wiki' instead.
URL path for resolving relative links to issues, media, and files. Expected format: /subpath/{user}/{repo}/src/{branch,commit,tag}/{identifier/path}/{file/dir}
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_RENDER_MARKDOWN_RAWTool to render raw markdown text as HTML. Use when you need to convert markdown content to HTML format for display or processing.
Input parameters
Raw markdown text to render as HTML. Supports standard markdown syntax including headers, bold, italic, lists, links, images, code blocks, etc.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GITEA_RENDER_MARKUPTool to render a markup document as HTML with support for multiple markup formats. Use when you need to convert markup content (Markdown, AsciiDoc, etc.) to HTML with specific rendering contexts like comments, wiki pages, or files.
Input parameters
Rendering mode that specifies the context for rendering. Options: 'markdown' (default/standard), 'comment' (for issues/pull requests), 'wiki' (wiki pages), 'file' (file content with extension detection).
The markup content to be rendered into HTML. Supports various markup formats including Markdown, AsciiDoc, and others depending on the mode.
DEPRECATED: Legacy flag indicating wiki page content. Use mode='wiki' instead.
URL path for resolving relative links to issues, media, and files. Expected format: /subpath/{user}/{repo}/src/{branch,commit,tag}/{identifier/path}/{file/dir}
File path for detecting the markup extension when using mode='file'. Used to determine the appropriate markup renderer based on file extension.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 52 agents privately built on Nagent that already use Gitea.
Build on Nagent
Connect Gitea to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Gitea, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Gitea is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Gitea is connected, you configure its 19 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Gitea steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Gitea event fires, the agent kicks off automatically.
Every Gitea action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Gitea ships with 19 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Gitea together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Gitea-based workflows tailored to your business.