Missing placeholder / hint text in "Run script" action (workflow_script) in Flow UI – Nextcloud 32

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Hi everyone,

I’m currently using Nextcloud AIO 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 the screenshots provided by the app developer.

In the documentation examples, when selecting “Run script” in the Flow configuration, there is usually a placeholder / hint in the input field showing how to enter the script path and variables (for example a sample command with placeholders like %f or similar variables).

On my installation, the Flow action can still be configured, but the placeholder / hint text does not appear at all in the command input field, so it is unclear how exactly the command should be formatted.


Environment

  • OS (host): Ubuntu 25.04 (plucky)

  • Kernel: Linux 6.14.0-35-generic x86_64

  • Deployment: Nextcloud All-in-One (AIO) in Docker

  • Docker containers (relevant):

    • nextcloud-aio-mastercontainer → image: ghcr.io/nextcloud-releases/all-in-one:latest

      • Ports: 80/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8080->8080/tcp
    • nextcloud-aio-apache → image: ghcr.io/nextcloud-releases/aio-apache:latest

      • Ports: 80/tcp, 127.0.0.1:11000->11000/tcp
    • nextcloud-aio-nextcloud → image: ghcr.io/nextcloud-releases/aio-nextcloud:latest

      • Ports: 9000/tcp
    • nextcloud-aio-database → image: ghcr.io/nextcloud-releases/aio-postgresql:latest

      • Ports: 5432/tcp (internal)
    • nextcloud-aio-redis → image: ghcr.io/nextcloud-releases/aio-redis:latest

      • Ports: 6379/tcp (internal)
    • nextcloud-aio-talk → image: ghcr.io/nextcloud-releases/aio-talk:latest

      • Ports: 0.0.0.0:3478->3478/tcp, 0.0.0.0:3478->3478/udp, :::3478->3478/tcp, :::3478->3478/udp
    • plus other AIO containers: nextcloud-aio-imaginary, nextcloud-aio-whiteboard, nextcloud-aio-notify-push, nextcloud-aio-onlyoffice

  • Nextcloud version (from inside nextcloud-aio-nextcloud container):

    From php occ status:

    • installed: true
    • version: 32.0.6.1
    • versionstring: 32.0.6
    • maintenance: false
    • needsDbUpgrade: false
  • **PHP version (inside Nextcloud container):

    PHP 8.3.30 (cli) (NTS)
    Zend Engine v4.3.30 with Zend OPcache v8.3.30
    
  • Workflow-related apps (from occ app:list | grep -i workflow):

    - workflow_pdf_converter: 3.0.0
    - workflow_script: 3.0.0
    - workflow_script_ui_fix: 0.1.0
    - workflowengine: 2.14.0
    
  • Log file:

    data/nextcloud.log (exists, size ~250 KB)
    

If needed, I can provide specific log excerpts relevant to opening the Flow page or saving the Flow.


What I’m trying to do

I want to set up a Flow using the Workflow Script app so that Nextcloud will run a shell script when a file is created or updated.

According to the screenshots and documentation of the app, in the “Run script” action there should be a placeholder or example text in the input field showing how to specify the script path and placeholders (e.g. a sample command with %f etc.).


Actual behavior

  • I go to Administration → Flow and create a new Flow.
  • I configure for example:
    • Trigger: File created / File updated
    • Filter: Custom mimetype = text/plain
    • Action: Run script (from the workflow_script app)
  • The action shows a command input field, but:
    • There is no placeholder / hint text inside the input field.
    • It is just an empty field without any example of how to write the command or which variables (like %f) are available.

So the workflow can be created, but I do not see the same helpful placeholder that is visible in the app’s documentation.


Expected behavior

  • When choosing the “Run script” action, I expect the input field to show a placeholder / hint that indicates:
    • a sample script path (e.g. /path/to/script.sh %f), and/or
    • which placeholder variables are available (like %f for the file, etc.).
  • This would make it clear how to format the command.

Questions

  1. Is this missing placeholder/hint expected behavior in recent versions of Nextcloud or the workflow_script app?
  2. Could this be related to:
    • my Nextcloud version (32.0.6),
    • the workflow_script version (3.0.0),
    • the additional workflow_script_ui_fix app,
    • or some missing configuration / dependency?
  3. Is there a known way to restore or enable the placeholder/hint in the Run script input field?

If screenshots or log snippets would help, I can provide them as well. Thanks in advance for any guidance!

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • replace me
  • Operating system and version (e.g., Ubuntu 24.04):
    • replace me
  • Web server and version (e.g, Apache 2.4.25):
    • replace me
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • replace me
  • Is this the first time you’ve seen this error? (Yes / No):
    • replace me
  • When did this problem seem to first start?
    • replace me
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • replace me
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • replace me

Summary of the issue you are facing:

[…]

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

To see the available variable, you need to click on the small arrow behind the word “documentation” which is shown below the path field:

grafik

I’m personally not a fan of calling scripts via a variable, instead I would recommend to use an absolute path, like “<path-to-the script-you want-to-call>/your-script.sh "%a" "%e" "%f" "%i" "%n" "%o" "%x"”, and append the variables you want to parse to the script.

BTW, you should search this forum for answer first before raising a new request :wink:

https://help.nextcloud.com/search?q=workflow_scripts%20%40j-ed

1 Like

Here is a picture of what i’m facing

Somehow the path field is not shown on your server. It should look like this:

I would recommend to clear caches, change web browser etc. to find put what is suppressing the field.

1 Like