Dedicated form for manual workflow dispatch

[frederic-kneier]

Select Topic Area

Question

Body

Is there a dedicated url for manually dispatching workflows just like the "Run workflow" popup dialog, that allows to fill in input values using query parameters? Having something like the "/issues/new" or "releases/new" page, that allows to set field using query parameters like "/issues/new?title=Test&body=content" would be very helpful.

This way we could create links to partially or fully prepare certain manual workflow dispatches. An example could look like this:

https://github.com/<company>/<repo>/actions/workflows/deploy.yml/dispatch?branch=main&version=1.2.3&environment=dev

This could just show the same content like the "Run workflow" dialog and just fill in the values. And such links could then be created and displayed in other workflows or even in readme files to allow prepared manual executions.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[UtkarshTrivedi2934]

As of now, GitHub does not support a dedicated URL for pre-filling inputs in the "Run workflow" manual dispatch UI via query parameters, similar to how issues or releases can be pre-filled (e.g., /issues/new?title=...). The manual dispatch UI under Actions > Workflows > Run workflow does not currently accept query parameters to prepopulate inputs like branch, version, or environment.

Current Options and Workarounds:
✅ 1. Manual Dispatch via GitHub API
You can manually trigger workflows with input values using the GitHub REST API v3:

curl -X POST \ -H "Authorization: token YOUR_GITHUB_TOKEN" \ -H "Accept: application/vnd.github.v3+json" \ https://api.github.com/repos/<owner>/<repo>/actions/workflows/<workflow_file>.yml/dispatches \ -d '{"ref":"main","inputs":{"version":"1.2.3","environment":"dev"}}'

You could wrap this in a simple web UI or script to simulate a prefilled "Run workflow" experience.

✅ 2. GitHub Actions Workflow Badge + Documentation
You can create documentation or README links that explain how to use the "Run workflow" feature and include the required input parameters, even if you can’t pre-fill them directly in the UI.

Example README snippet:

`### 🚀 Deploy Workflow
To deploy a version manually, go here and use:

• version: e.g. 1.2.3
• environment: e.g. dev or production
  `

🚫 Not Supported Yet:
URLs like https://github.com///actions/workflows/deploy.yml/dispatch?version=1.2.3 do not work.

There is no UI-based workaround to prefill these fields using query parameters at this time.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[MPV]

See:

• https://github.com/orgs/community/discussions/51159