[GH-ISSUE #1695] Template CSV Bulk Send, Merge Fields #480

Open
opened 2026-02-26 18:47:14 +03:00 by kerem · 1 comment
Owner

Originally created by @matmurdock on GitHub (Mar 11, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1695

Feature Description

Now the you can bulk send documents using the bulk send option, the next logical feature is for the CSV file to also dynamically update fields in the document. I imagine you could use the placeholder name as the column name in the CSV file.

Use Case

The use case would be to quickly send out bulk, customized documents.

Proposed Solution

I imagine you could use the placeholder name as the column name in the CSV file.

Alternatives (optional)

No response

Additional Context

No response

Please check the boxes that apply to this feature request.

  • I have searched the existing feature requests to make sure this is not a duplicate.
  • I have provided a detailed description of the requested feature.
  • I have explained the use case or scenario for this feature.
  • I have included any relevant technical details or design suggestions.
  • I understand that this is a suggestion and that there is no guarantee of implementation.
  • I want to work on creating a PR for this issue if approved
Originally created by @matmurdock on GitHub (Mar 11, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1695 ### Feature Description Now the you can bulk send documents using the bulk send option, the next logical feature is for the CSV file to also dynamically update fields in the document. I imagine you could use the placeholder name as the column name in the CSV file. ### Use Case The use case would be to quickly send out bulk, customized documents. ### Proposed Solution I imagine you could use the placeholder name as the column name in the CSV file. ### Alternatives (optional) _No response_ ### Additional Context _No response_ ### Please check the boxes that apply to this feature request. - [x] I have searched the existing feature requests to make sure this is not a duplicate. - [x] I have provided a detailed description of the requested feature. - [x] I have explained the use case or scenario for this feature. - [x] I have included any relevant technical details or design suggestions. - [x] I understand that this is a suggestion and that there is no guarantee of implementation. - [x] I want to work on creating a PR for this issue if approved
Author
Owner

@github-actions[bot] commented on GitHub (Mar 11, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

<!-- gh-comment-id:2712671062 --> @github-actions[bot] commented on GitHub (Mar 11, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#480
No description provided.