# A native, two-way Slack App for Gitea (ChatOps + Unfurling)

**URL:** <https://forum.gitea.com/t/a-native-two-way-slack-app-for-gitea-chatops-unfurling/12080>\
**Category:** Ecosystem\
**Created:** [April 30, 2026, 12:44pm UTC](https://forum.gitea.com/t/a-native-two-way-slack-app-for-gitea-chatops-unfurling/12080 "2026-04-30T12:44:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![saurabhb-dev](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/saurabhb-dev/32/7392_2.png) [@saurabhb-dev](https://forum.gitea.com/u/saurabhb-dev)\
**Post date:** [April 30, 2026, 12:44pm UTC](https://forum.gitea.com/t/a-native-two-way-slack-app-for-gitea-chatops-unfurling/12080/1 "2026-04-30T12:44:53Z")

</div>

Hey everyone,

I’ve been looking into the current state of Gitea-to-Slack integrations and noticed most teams are relying on standard, one-way outbound webhooks or custom n8n pipelines.

I’m exploring building a dedicated Slack App specifically for Gitea, similar to the native GitHub/Slack integration. The goal is to move beyond simple notifications and enable actual ChatOps.

The MVP I’m mapping out would allow you to:

- Get rich link unfurling in Slack (previewing PRs, issues, and code snippets).

- Pull request notification

- Issue creation and taking actions on it directly from Slack via interactive buttons (Close, Re-open, comment).

- Properly map Gitea usernames to Slack `@` mentions.

Before I start writing the OAuth and webhook routing logic, I wanted to get a pulse check from the community:

1. Is this a pain point for your team, or are standard webhooks sufficient for your workflow?

2. If you had a two-way Slack app, what is the #1 action you’d want to trigger without leaving chat?

Would love to hear how you are currently handling this!