Skip to content

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.

Connectorinvoke:What it does
Jirajira.*Issues, search (JQL), transitions, comments. JQL inputs are injection-validated.
Confluenceconfluence.*Pages, content, search.
Bitbucketbitbucket.*Repos, pull requests, pipelines.
GitHubgithub.*Repos, issues, PRs, actions.
GitLabgitlab.*Repos, MRs, pipelines.
TeamCityteamcity.*Trigger and query CI builds.
Terminal window
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}"
Connectorinvoke:What it does
Akeneo PIMakeneo.*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.

Connectorinvoke:What it does
Zabbixzabbix.*Query the Zabbix monitoring API.
Zabbix Senderzabbix-sender.*Push trapper items into Zabbix.
IISiis.*Manage IIS sites/app pools.
Nginx Proxy Managernginx-proxy-manager.*Manage proxy hosts and certificates.
Windowswindows.*Windows host operations (services, scheduled tasks, etc.).
Connectorinvoke:What it does
Human Taskhuman-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.