Hi @Candace Low ,
Can you elaborate more on how you want to customize the webhook URL? Do you want to change the parameter values when running the workspace?
The Webhook URL contains all the required information to run a particular workspace from the web: the FME Flow (Server) domain, web service, repository, workspace, and any parameters and their values follow in a query string. This article may be a helpful resource for submitting a job through FME Flow webhook URLs.
Hope this helps!
Kezia
Hi @Candace Low ,
Can you elaborate more on how you want to customize the webhook URL? Do you want to change the parameter values when running the workspace?
The Webhook URL contains all the required information to run a particular workspace from the web: the FME Flow (Server) domain, web service, repository, workspace, and any parameters and their values follow in a query string. This article may be a helpful resource for submitting a job through FME Flow webhook URLs.
Hope this helps!
Kezia
Hello, we'd like to append something at the end to identify 'which' type of workspace is being run. This will be customer facing so we kind of want to use it like an api
Ex: https://fmecloudurl/?id=39688brb9-xxx/routes
OR
https://fmecloudurl/?id=887188brb9-xxx/addresses
Hello, we'd like to append something at the end to identify 'which' type of workspace is being run. This will be customer facing so we kind of want to use it like an api
Ex: https://fmecloudurl/?id=39688brb9-xxx/routes
OR
https://fmecloudurl/?id=887188brb9-xxx/addresses
@Candace Low , thanks for the examples.
This is not something I've run into before but in my testing, if you add "&/routes" or "&/addresses", it should still run fine.
Please note that this has not been thoroughly tested so I'd advise testing with your workspaces before pushing to PROD.
Hope this helps!
Kezia