Trigger the execution of a pipeline in a deployed project. This is useful when you want to automate pipeline runs without relying on Prophecy’s built-in scheduling.
Prophecy access token
Pipeline run trigger parameters
Unique identifier of the data fabric where the pipeline resides. You can find the ID in the URL of the fabric metadata page.
Name of the pipeline to be triggered.
Unique ID of the project where the pipeline resides. You can find this string in the URL of the project editor or metadata page.
Map of key-value pairs representing pipeline parameters. These will override default parameter values.
Specific branch of the pipeline to execute. If omitted, the current working branch is used.
Specific version of the project containing the pipeline. If omitted, the latest version is used.
Name of a specific gem within the pipeline. If provided, the pipeline will not run beyond this gem. If no processName is specified, the full pipeline is executed.
Pipeline run triggered successfully