Create a Dosya sharing link in n8n

Create a Dosya sharing link in n8n is easier to verify when you use one controlled item and confirm the account, workspace, source, and destination at each step. This guide follows the current Dosya workflow and identifies the result you should see.

Before you start

• Open an n8n workflow with Dosya credentials in the current released client.
• Confirm the active account and workspace, then identify disposable file and explicit link settings.
• Use a small non-confidential test item and record its current state before changing it.
• Keep passwords, API keys, recovery codes, private links, personal data, and confidential file contents out of screenshots and support messages.

Steps: create a Dosya sharing link in n8n

1. Open an n8n workflow with Dosya credentials and confirm the active account and workspace.
2. Locate disposable file and explicit link settings and verify its name or identifying details.
3. Map the file identifier and access controls, run once, and test the returned link in a private browser.
4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
5. Confirm that the link exposes only the intended test file under the selected controls.
6. Refresh, fetch, or reopen the relevant view once to verify the result persisted.

Expected result

The controlled workflow completes and the link exposes only the intended test file under the selected controls. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

• Available controls depend on the current client version, account plan, workspace role, policy, and selected integration surface.
• Processing, indexing, background transfer, provider authorization, or storage accounting can delay a visible result.
• For destructive, access-changing, or automated actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to an n8n workflow with Dosya credentials, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error, delivery, or request identifier.

Related guides

• Connect Dosya to n8n
• Build an n8n workflow