What features do you need to go live?

[ElTimuro]

• What features do you need to go live tomorrow?
• What workflows do you need?
• Is the developer preview enough for you to go live, feature-wise?

[philippeauriach]

Hello 👋
Some features that would be mandatory in one of our case:

• A way to generate documents to be signed using an API (for integration with an existing internal tool or even zappier for example)
• A way to sign documents in a mobile app (might be achievable using webviews?)

Sorry if those are already developed / planned, I did not see mention of them :)

[ElTimuro]

Hey, thanks for the input :) API is not explicitly mentioned yet, but of course, planned. There will be a more detailed product roadmap soon, I'll be sure to include some specifics. Zapier is a great idea, if you have specific zaps in mind feel free to post them, I would add them to the backlog. Would you prefer Zapier or a generic REST API first?

Not sure what you mean by "in a mobile app". As part of a native android app workflow for example? Since the signing links require no login this should be straightforward with web views (disclaimer I'm not an app developer) or an in-app browser. If there is something else, let me know 👌

[philippeauriach]

Zapier was just an idea like this, we could imagine a contract to be sent after filling a typeform or something. I would definitely prefer a generic API !

If no login is needed then as long as the UI is responsive, a webview should be straightforward indeed (getting the signing link from the API mentioned before)

thanks a lot, will follow the project!

[ElTimuro]

Glad to hear it 🚀 Let me know if you have questions at any point.

[treed593]

I will chime in as another vote for a Generic REST API. We do most of our custom integrations without Zapier or similar tools and have been looking for something like Documenso

[bramkn]

As soon as a REST API is available, a node for n8n will follow soon.
Already have some interest from some of my n8n clients for it. :-)

[fmerian]

@bramkn awesome!

for the record, there's an open issue for the n8n integration (#110).

[treed593]

It would be nice, if we could generate a "sign" link without the need to connect Documenso to an email provider. So each signer would still have a unique link, but we could send that manually in a separate process

[ElTimuro]

Good Idea. The would be the same as in the Emai IMO so it would just need to be copyable from the recipients from. Added an Issue here: #36

[yl-chow]

For my organisation's use case, the following are crucial:

1. Generate signing session via API (we prefer REST API but if that's not possible in the near future, could you consider making it available on Make (formerly Integromat)?)
2. From point number 1 above, generate signing link for each signer so that we can embed the links in our client-facing dashboards or send the links to clients via email/WhatsApp API
3. Signing sequence
4. Ability to control types of signature (e.g. turning off typed signatures; allowing only drawn signatures)
5. Audit trail
6. Ability to split audit trail from the signing document (in my market, some banks/government agencies are fussy about not having the audit trail attached with the main doc)

[fmerian]

@yl-chow hi YL, thanks for this detailed workflow!!

[apptologyindia]

@ElTimuro Do you have API documentation which can be made available ?
Also, how about Multi-Tenant Approach - E.g. We run a SAAS based model where we would like to offer this as a plugin to each Tenant to work independently using their own URL's , SMTP etc.

[fmerian]

@apptologyindia hello there! we don't have API documentation just yet as we're currently doing a rewrite (see roadmap here and learn more about the rewrite there). it will definitely come up with the release tho. thanks!

[gillistephan]

For our use case in order to switch to a hosted Documenso solution immediately, the following would be required:

1. Generate a signing session via an API by providing a previously generated PDF document with defined fields (preferrably based on PDF form fields - which is pretty common in our industry - banks/insurance). Comparable to docusign tabs concept, but less complicated.

2. Define a predefined signing sequence in API call from 1) - for our industry, order matters.

3. Ability to generate a Signing-Link for each Signer

Nice to have:

1. Embeddable React-Widget, which receives a Signing-Session or any other props, to be able to directly embedd the Signing in our product, to provide a seamless customer experience.
2. Ability to get notified (Webhooks) / request information about a document status (overall status, who has signed)

[fmerian]

@gillistephan thanks, Stephan! seems similar to @yl-chow's use case. also love the idea of embedding for less context-switching and notifications.

keep an eye on the roadmap!

[Aj7Ay]

Hello,
Modify the existing signature field feature to accept and display user initials instead of the full name. When signing a document, users should input their initials instead of a complete name. Ensure that the system sends and stores the provided initials correctly for document signing purposes.

[tankerkiller125]

Generic OIDC SSO, or at least more options than just Google.

[jinnatar]

Have this same requirement, logged it as an FR after a bit of investigation: #1090

[PhilippvH1]

• API ✅
• LTV
• Force users to sign using a hand/drawn signature every time
• German tranlsation