Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Gitea connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using `@activepieces/piece-gitea@0.1.0` and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

Gitea Integration & Workflow Automation

Connector

Gitea

Self-hosted Git service

Get Started Talk to an Expert

CategoryDeveloper Tools

Authenticationcustom

Objects8 supported

Actions4 supported

Technical ReferenceView technical reference

Overview

What you can do with Gitea.

Connected capability

Self-hosted Git service

Technical Reference

Gitea

Self-hosted Git service

View technical reference

Similar connectors

Continue exploring.

View all connectors

Algolia

Manage your Algolia search indices, add, browse, and delete records.View details

Amazon S3

Scalable storage in the cloudView details

AWS Secrets Manager

AWS Secrets Manager integration for Flows360 workflows.View details

Azure DevOps

Track work, code, and ship software with Azure Boards, Repos, and Pipelines.View details

Next step

Connect Gitea through Flows360.

Talk through the connector, the systems around it and the outcome you need.

Get Started Talk to an Expert

Find the right connection faster.

What you can do with Gitea.

Connected capability

Gitea

Continue exploring.

Connect Gitea through Flows360.