Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation updates an existing organization variable in a specified organization. It allows users to modify the name and/or value of a variable associated with an organization. This is useful for managing configuration or environment variables dynamically within an organization's context, such as updating API keys, feature flags, or other settings without manual intervention.

Practical examples:

  • Changing the value of a deployment environment variable for an organization.
  • Renaming a variable to better reflect its purpose while keeping its value intact.
  • Automating updates to organizational settings based on external triggers or workflows.

Properties

Name Meaning
Org The name of the organization where the variable exists and will be updated.
Variablename The current name of the variable that you want to update.
Name New name for the variable. If left empty, the variable's name remains unchanged.
Value The new value to assign to the variable. This is required and will overwrite the old value.

Output

The node outputs JSON data representing the updated organization variable after the operation completes successfully. This typically includes the variable's current name and value reflecting the changes made.

If the node supports binary data output (not indicated here), it would represent any file or media content related to the variable update, but this operation deals only with JSON data.

Dependencies

  • Requires an API key credential to authenticate requests against the target service's API.
  • Needs the base URL of the API endpoint configured in credentials.
  • Relies on the external service's API to perform the update operation on organization variables.

Troubleshooting

  • Common issues:

    • Incorrect organization or variable names may cause "not found" errors.
    • Missing or invalid API authentication can lead to authorization failures.
    • Providing an empty value for the required "Value" property will likely cause validation errors.

  • Error messages and resolutions:

    • "Variable not found" — Verify the organization and variable names are correct.
    • "Unauthorized" or "Authentication failed" — Check that the API key credential is valid and has sufficient permissions.
    • "Invalid input" — Ensure all required fields, especially "Value," are provided and correctly formatted.

Links and References

  • Refer to the API documentation of the target service for details on organization variable management endpoints.
  • n8n documentation on creating and using credentials for API authentication.
  • Best practices for managing environment and configuration variables in automation workflows.

Discussion