Bring Gitea activity into Coherence
Start from a supported Gitea event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Commit
Finishes with
Create or update a Coherence record
Gitea
Self-hosted Git service
Gitea currently provides 4 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Developer Tools4 triggers4 actions
Triggers
(4)New Commit
Triggers when a new commit is pushed to a repository.
New Issue
Triggers when a new issue is created.
New Pull Request
Triggers when a new pull request is created.
Workflow Run Completed
Triggers when a workflow run is completed. Requires Gitea Actions to be enabled on your Gitea instance.
Actions
(4)Create Issue
Creates a new issue in a repository.
Add Comment to Issue/PR
Adds a comment to an issue or pull request.
Update Repository
Update repository settings.
Custom API Call
Make a custom API call to a specific endpoint
What can you automate with Gitea and Coherence?
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Act in Gitea from a Coherence workflow
Use a change in Coherence to run a supported Gitea action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Issue
Connect Gitea to the wider customer workflow
Combine Gitea with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
New Commit
Finishes with
Create Issue, then preserve the outcome in Coherence
How to connect Gitea
The exact authentication fields depend on Gitea. The workflow structure stays straightforward:
1
Connect the account
Authorize the Gitea account and permissions the workflow needs.
2
Choose a supported step
Select one of the current triggers or actions listed above and map its fields.
3
Test with a real record
Run a small test, inspect the result in both systems, and only then enable the workflow.
Related integrations for the same workflow
Explore apps that share a category with Gitea or provide a complementary trigger or action.
Gitea integration questions
What can I automate with the Gitea integration?
Gitea currently provides 4 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
How many Gitea triggers and actions are available?
Gitea currently lists 4 triggers and 4 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Can Gitea connect to other apps through Coherence?
Yes. A workflow can combine supported Gitea triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
Do I need to write code to connect Gitea?
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Ready to connect Gitea?
Start automating in minutes. No credit card required.