Skip to main content
Question

Is it possible to get the current FME Flow connection from within a workspace running on FME Form?

  • May 14, 2026
  • 1 reply
  • 24 views
nic_ran
Contributor
Forum|alt.badge.img+18

Newer versions of FME Form can be connected to FME Flow for the purpose of obtaining Deployment Parameter values at runtime:

Given that FME Form is connected to Flow I was wondering if anyone knows of a way of obtaining details of that connection when a workspace is run in Form. It does not appear to be exposed anywhere.

A workaround would be to create a Deployment Parameter in my Flow instances and reference that in Form but it seems there should be an out of the box solution to this.

Specifically, what I want to do is to query the FME Flow API for the connected instance, without having to hard-code the FME Flow URL in the HTTPCaller.

1 reply

j.botterill
Influencer
Forum|alt.badge.img+58
  • j.botterillInfluencer
  • Influencer
  • May 15, 2026

First read up about all the current functionality of Deployment Parameters

 

UI method

Under Flow > Jobs - find the workspace you run and open log

Under the “Request Data”

Job request info

You will find the Deployment Parameters section, refer to the VALUES

 

REST API v4 method

To inspect jobs in the FME Flow REST API v4, use the Jobs endpoints:

  • List job history: GET /jobs (use limit + offset for pagination). This gives you job records you can filter/sort in your client code.
  • Inspect one job: GET /jobs/{id} to see details for a specific run.

Seems this endpoint only has the run, retrieve, cancel, job log and the status. Nothing about the request

 

To dive into the deployment parameters with REST… 

https://HOST.domain/fmeapiv4/docs/index.html#/dependencies

Seems to only be about creating and retrieve deployment parameters

 

In the v4 REST API docs (Help & Resources → REST API), create a token by signing in top right cnr. Then look under Repositories for the endpoint that returns the workspace file/content (download).

Build this out in FME Form

Once you have the .fmw, in a reader (fme workspace) you can parse it (it’s XML) and extract any deployment-parameter tokens/references.

Community Stats

32,561
Posts
123,625
Replies
40,848
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.