Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node allows you to create a new issue in a specified repository on a Gitea server via its API. It is useful for automating issue tracking workflows, such as automatically opening issues from error logs, user feedback, or integration with other tools. For example, you could use this node to create an issue when a monitoring system detects a problem or when a customer submits a bug report through a form.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the issue will be created.
Repo The name of the repository where the issue will be created.
Assignee (Deprecated) A single user to assign the issue to.
Assignees A JSON array of usernames to assign the issue to.
Body The detailed description or content of the issue.
Closed Boolean indicating whether the issue should be created as closed (true) or open (false).
Due Date The due date for the issue, as a string (typically in ISO 8601 format).
Labels A JSON array of label IDs to associate with the issue.
Milestone The milestone ID to associate the issue with.
Ref Reference string related to the issue (e.g., commit SHA or branch name).
Title The title or summary of the issue.

Output

The node outputs the response from the Gitea API after creating the issue. This typically includes the full JSON representation of the newly created issue, containing fields such as issue ID, URL, state, assignees, labels, and timestamps.

If the node supports binary data output, it is not indicated here; the main output is JSON data representing the created issue.

Dependencies

  • Requires access to a Gitea instance with API enabled.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the Gitea API must be set in the credentials configuration.

Troubleshooting

  • Authentication errors: Ensure the API token is valid and has sufficient permissions to create issues in the target repository.
  • Invalid repository or owner: Verify that the owner and repo names are correct and accessible by the authenticated user.
  • Malformed JSON in Assignees or Labels: When providing JSON arrays, ensure the syntax is correct to avoid parsing errors.
  • Closed property confusion: Setting Closed to true creates the issue in a closed state, which might be unexpected; verify if you want the issue open or closed upon creation.
  • API rate limits: If many issues are created rapidly, the Gitea server may throttle requests; handle retries accordingly.

Links and References

Discussion