Integrations¶

This page describes how to connect AntFlow to AntFlow Spaces and AntFlow Trigger. Configure these optional integrations with configs.externalServices in the Helm chart; this maps to EXTERNAL_SERVICES in the browser configuration. The configuration keys are case-sensitive: use SPACES for AntFlow Spaces and TRIGGER for AntFlow Trigger.

Deploy AntFlow Spaces and AntFlow Trigger separately before configuring their integration. These settings do not deploy either service. Omit an integration you do not use.

These YAML blocks are configuration templates, not connections to hosted demo services. Replace each example.com service URL with the endpoint of the service you deployed. Keep the documented project and reference substitutions intact.

AntFlow Spaces¶

Set the GitLab topic used to discover space projects, the AntFlow Spaces health endpoint, and its deployment URL template under SPACES:

configs:
  externalServices:
    SPACES:
      topic: sharinghub:space
      healthzUrl: https://kdeployer.example.com/healthz
      deployUrl: https://kdeployer.example.com/deploy/<project_path>/ref/<project_ref>

Keep <project_path> and <project_ref> in the deployment URL: they identify the selected project and Git reference. This topic is independent of configs.topic, which filters workflow projects.

AntFlow Trigger¶

Set the AntFlow Trigger health endpoint and API base URL under TRIGGER:

configs:
  externalServices:
    TRIGGER:
      healthzUrl: https://antflow-trigger.example.com/health
      apiUrl: https://antflow-trigger.example.com

To enable both integrations, place both service entries under the same configs.externalServices map.

Connectivity and availability¶

The browser checks the configured health endpoints when AntFlow initializes. A service is marked available only when its check returns HTTP 200. If an integration is unavailable, check its health response and the browser's network console, then reload AntFlow after fixing the issue.

All endpoints must be reachable from users' browsers. For cross-origin requests, configure the external service's CORS policy to allow the AntFlow origin. Health checks are sent without cross-origin credentials, so they must not depend on a cross-origin session cookie. Use HTTPS endpoints when AntFlow is served over HTTPS to avoid browser mixed-content blocking.