mercell/Workflow Dispatch and wait
Trigger and chain GitHub Actions workflows with workflow_dispatch events and wait for result
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit May 20, 2025
- License
- MIT
Pinned Snippet
uses: mercell/workflow-dispatch@a304ec90d7cb793fb974c282eaecb9c0a5a7bddb # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| workflow | Name or ID of workflow to run | yes | — |
| display-title | Display title to filter the target workflow run | no | — |
| token | GitHub token with repo write access, can NOT use secrets.GITHUB_TOKEN, see readme | yes | — |
| inputs | Inputs to pass to the workflow, must be a JSON string. All values must be strings (even if used as boolean or number) | no | — |
| ref | The reference of the workflow run. The reference can be a branch, tag, or a commit SHA | no | — |
| repo | Repo owner & name, slash separated, only set if invoking a workflow in a different repo | no | — |
| run-name | If specified will select the run ID based on the run name | no | — |
| display-workflow-run-url | Get the URL of the triggered workflow and display it in logs (useful to follow the progress of the triggered workflow) | no | true |
| display-workflow-run-url-interval | The time to wait (+unit) between two polls to get the URL of the workflow run | no | 1m |
| display-workflow-run-url-timeout | Maximum amount of time (+unit) to wait for the URL of the workflow run. If the timeout is reached, it is just ignored | no | 10m |
| wait-for-completion | Block until the triggered workflow has finished | no | true |
| wait-for-completion-timeout | Maximum amount of time (+unit) to wait to mark workflow as timed out | no | 1h |
| wait-for-completion-interval | Time to wait (+unit) between two polls to get run status | no | 1m |
| workflow-logs | Indicate what to do with logs of the triggered workflow. `ignore` do not retrieve logs from tiggered workflow. `print` retrieves logs from triggered workflow and print in the workflow that triggered the other workflow. `output` retrieves logs from triggered workflow and set them as `workflow-logs` output. `json-output` retrieves logs from triggered workflow and return a json array groupped by job name. | no | ignore |
Outputs
| name | description |
|---|---|
| workflow-conclusion | Conclusion of the triggered workflow |
| workflow-id | ID of the triggered workflow |
| workflow-url | URL of the triggered workflow |
| workflow-runs-found | Number of workflow runs found (while searching for the triggered workflow run) |
| workflow-logs | Logs of the triggered workflow. Based on `inputs.workflow-logs`, format is set to: - `output`: Multiline logs formatted as: '<job-name> | <datetime> <message>' - `json-output`: JSON logs formatted as: '{"<job-name>": [{"<datetime>": "<message>"}]' |