nextcloud / nextcloud/integration_documenso

⁠Return signed documents to Nextcloud after completion in Documenso

Open
#138 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
12
Forks
2
PR merge metrics
No merged PRs in 30d

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: (see administration page)

Nextcloud: 33.0.5 (self hosted)
Documenso: 2.11.0 (self hosted)
integration_documenso: 2.1.0

Is your feature request related to a problem? Please describe.

When sending a document for signing via the Documenso integration, the workflow is currently one-directional: files go from Nextcloud to Documenso, but once all parties have signed, there is no way to get the completed document back into Nextcloud automatically. To retrieve the signed PDF, you have to log in to Documenso separately and download it manually. This breaks the flow for anyone who uses Nextcloud as their primary document storage.

Describe the solution you'd like

Once a document sent through this integration reaches a completed state in Documenso, it should find its way back into Nextcloud without requiring manual action from the user.

Describe alternatives you've considered

Using a middleware tool (like n8n) to listen for Documenso webhook events and upload the signed document back via WebDAV. This works, but adds significant setup complexity and external dependencies for what feels like a core part of the integration's usefulness.

Additional context

Documenso supports webhooks for document lifecycle events (including completion) and has an API endpoint to download completed documents. Nextcloud's own webhook listener functionality could also be relevant here. The right approach is up to the maintainers, but the building blocks seem to be available on both sides.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing Nextcloud-to-Documenso sending workflow, then compare Documenso completion webhooks and its completed-document download API with Nextcloud's webhook listener and WebDAV upload options. The work is done when completed signed PDFs are returned to the appropriate Nextcloud location without manual retrieval, with the integration's existing behavior preserved.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.