Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve the current tracked times for a user. It is useful in scenarios where you want to monitor or analyze time tracking data associated with a user, such as generating reports on work durations, auditing time logs, or integrating time tracking data into other workflows.

For example, you could use this node to fetch all time entries updated within a specific date range or paginate through large sets of time tracking records for a particular user.

Properties

Name Meaning
Page The page number of results to return (1-based). Useful for paginating through multiple pages.
Limit The number of results per page (page size). Controls how many time entries are returned.
Since Filter to only show time entries updated after this timestamp (RFC 3339 format).
Before Filter to only show time entries updated before this timestamp (RFC 3339 format).

Output

The node outputs JSON data containing the list of current tracked times for the specified user. Each item in the output typically represents a time entry with details such as start time, end time, duration, and possibly related metadata like project or task identifiers.

If the API supports it, the output may be paginated according to the Page and Limit parameters.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • The node expects the base URL of the Gitea API to be configured in the credentials.
  • The node uses standard HTTP headers for JSON content negotiation (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Empty results: Ensure that the Since and Before timestamps are correctly formatted in RFC 3339 and that there are actually time entries within that range.
  • Pagination issues: If you receive fewer results than expected, verify the Page and Limit values; remember that Page is 1-based.
  • Authentication errors: Confirm that the API key credential is valid and has sufficient permissions to access user time tracking data.
  • API connectivity: Check the base URL configuration and network connectivity to the Gitea server.

Links and References

Discussion