Skip to content

Egress FTP

Responsibility

FTP/FTPS capability provider for workflow service_call steps.

Capabilities:

  • ftp.call — upload / download / list (POST /ftp)
  • ftp.connection — connection type

Note the capability name is ftp.call (no egress. prefix).

Architecture

Capability provider (see Deploy integration contract):

  • Registers with capability-registry at startup
  • Orchestrator discovers the endpoint via the registry
  • No first-class type: ftp workflow step — use service_call

Inbound Authentication

  • internal-only service, called by orchestrator after registry lookup

Outbound Authentication

  • FTP user/password or FTPS endpoint credentials from connection/step payload

Example workflow step

- id: list_remote
  type: service_call
  capability_name: ftp.call
  capability_version: "^1.0"
  path: /ftp
  connection: my_ftp
  payload: |
    {
      "action": "list",
      "remote_path": "/inbox"
    }
  timeout_seconds: 60

Key Config

  • network reachability to target FTP hosts

Health

  • GET /healthz
  • GET /readyz
  • GET /internal/capabilities