- Provides plugin components under
io.kestra.plugin.tencent. - Includes classes such as
QQTemplate,QQIncomingWebhook,QQExecution.
- What user problem does this solve? Teams need to tencent integrations for Kestra from orchestrated workflows instead of relying on manual console work, ad hoc scripts, or disconnected schedulers.
- Why would a team adopt this plugin in a workflow? It keeps Tencent steps in the same Kestra flow as upstream preparation, approvals, retries, notifications, and downstream systems.
- What operational/business outcome does it enable? It reduces manual handoffs and fragmented tooling while improving reliability, traceability, and delivery speed for processes that depend on Tencent.
Single-module plugin. Source packages under io.kestra.plugin:
templates
Infrastructure dependencies (Docker Compose services):
app
io.kestra.plugin.templates.Example
plugin-tencent/
├── src/main/java/io/kestra/plugin/templates/
├── src/test/java/io/kestra/plugin/templates/
├── build.gradle
└── README.md