Orchestration Trigger Queue V2

Trigger to start a Keboola Orchestration V2 across different Keboola Connection projects.

Authorization

Authorization is done with a KBC Storage API token. Generate a dedicated Limited Access SAPI Token with restricted access and custom access to the Orchestrator component.

Configuration

Create a new configuration of the Orchestration Trigger Queue V2 Application.

Screenshot - Incremental fetching

  • Fill in the KBC Storage API token with the Limited Access SAPI token.
  • Fill in the KBC stack based on your stack, you can find this out from the link to your keboola project
  • Fill in the Orchestration ID
  • Check or uncheck the checkbox for “Wait for job finish and check jobs status”. If checked, the job of the trigger will only finish when the Orchestration is finished. If unchecked, the job of the trigger will be finished as soon as the orchestration is started.

Note on Orchestration V2

If the link to your of your orchestration contains orchestrations-v2 :

…keboola.com/admin/projects/{ProjectID}/orchestrations-v2/{OrchID}

Your orchestration is V2. If the link to your of your orchestration contains orchestrations, your orchestration is NOT V2, and you should use the keboola.app-orchestrator-trigger application