nd solutions is by using the search function at the upper right.
If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
yeah so the nextcloud node’s share action doesn’t have a built-in field for custom share names. from what i can see in your screenshot, you’re limited to the standard options.
here’s what you can do instead:
**option 1: use the http request node**
skip the nextcloud node and hit the nextcloud api directly. that gives you way more control. the endpoint would be something like:
```
POST /ocs/v2.php/apps/files_sharing/api/v2/shares
```
with a body like:
```json
{
“path”: “/path/to/folder”,
“shareType”: 3,
“name”: “Your Custom Share Name”
}
```
you’d need your nextcloud instance url + api credentials in an http request node.
**option 2: rename after sharing**
if you just need the folder itself to have a different display name, you could create the share through n8n, then use a separate nextcloud “Update” action to rename the folder before/after sharing. depends on your workflow though.
what’s your end goal with the custom name? are you trying to make it display differently to users, or is this more about organization on your end? might help me suggest something more specific.
Well, since I originally posted this, Nextcloud has rolled out a new update where by default if a folder is shared, it generates an arbitrary link. I would like to be able to store/pull that link to be able to share it somewhere else. Now it cannot find the folder it created and the pathway is correct. I know the “file path” works because that is how the folder is created in the first place.
search function at the upper right.