Integrations
Dedicated connectors for the services teams integrate most often. Each wraps the service’s API behind a typed contract, with credentials on the connection.
Project & code management
Section titled “Project & code management”| Connector | invoke: | What it does |
|---|---|---|
| Jira | jira.* | Issues, search (JQL), transitions, comments. JQL inputs are injection-validated. |
| Confluence | confluence.* | Pages, content, search. |
| Bitbucket | bitbucket.* | Repos, pull requests, pipelines. |
| GitHub | github.* | Repos, issues, PRs, actions. |
| GitLab | gitlab.* | Repos, MRs, pipelines. |
| TeamCity | teamcity.* | Trigger and query CI builds. |
using: - environment/prod - zenvara/jira
output: issues: !obj-list
steps: - $hot: invoke: jira.search-issues on: jira with: jql: "priority IN ('High','Critical') AND status != 'Closed'"
- return: issues: "${hot.issues}"PIM & commerce
Section titled “PIM & commerce”| Connector | invoke: | What it does |
|---|---|---|
| Akeneo PIM | akeneo.* | Products, reference entities, attribute groups. Tuned for batch sync (BatchSize, MaxConcurrency, AutoSanitizeCodes). |
The join: transformer’s lookup-by: mode is built with Akeneo reference-entity enrichment in mind — see Transformers.
Infrastructure & monitoring
Section titled “Infrastructure & monitoring”| Connector | invoke: | What it does |
|---|---|---|
| Zabbix | zabbix.* | Query the Zabbix monitoring API. |
| Zabbix Sender | zabbix-sender.* | Push trapper items into Zabbix. |
| IIS | iis.* | Manage IIS sites/app pools. |
| Nginx Proxy Manager | nginx-proxy-manager.* | Manage proxy hosts and certificates. |
| Windows | windows.* | Windows host operations (services, scheduled tasks, etc.). |
Human-in-the-loop
Section titled “Human-in-the-loop”| Connector | invoke: | What it does |
|---|---|---|
| Human Task | human-task.* | Pause a flow for human approval/input, then resume with the response as typed payload. |
human-task is what turns a flow into an approval workflow: the flow blocks at the task, a person responds through the product or an API, and execution continues with their answer in the payload.
The exact actions and fields for each connector are in its <name>.connector.yaml and surfaced as editor autocomplete by the type provider. An MCP-aware assistant can list them against your live installation.