nextcloud / nextcloud/workflow_script
Workflow Script app does not show script path placeholder in Flow configuration in NextCloud 33
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 89
- Forks
- 19
- Avg merge
- 6h 38m
- Merged PRs (30d)
- 3
Description
I’m currently using Nextcloud with the workflow_script app to run external scripts when a file is created or updated.
However, I noticed something different from the documentation and examples provided by the app developer.
In the documentation screenshots, when selecting Run script in the Flow configuration, there is usually a placeholder field showing how to enter the script path and variables (for example placeholders like %f or other variables).
In my installation, the workflow can still be configured, but the placeholder hint or example path is not displayed in the input field, which makes it unclear how the command should be formatted.
Current configuration example:
Trigger: File created / File updated
Filter: Custom mimetype = text/plain
Action: Run script
But the input field only shows a blank command area without any example placeholder.
Has anyone encountered this issue before?
Is this related to the Nextcloud version, the workflow_script version, or a missing dependency?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Run script action in the Flow configuration on Nextcloud 33 with workflow_script, then compare the command field with the app documentation screenshots and examples. Identify where the placeholder is defined or omitted and verify whether it appears with the relevant versions. Done means the command field provides the documented path and variable guidance, or the version and dependency cause is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100