[GH-ISSUE #1550] Bulk Send Template via CSV #437

Closed
opened 2026-02-26 18:47:03 +03:00 by kerem · 5 comments
Owner

Originally created by @Mythie on GitHub (Dec 20, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1550

Originally assigned to: @Mythie on GitHub.

On the template view page /templates/[id] or when on the template table /templates we should have an option either in the top corner or within the actions menu to bulk send the given template using a CSV ("Bulk send via CSV"). This will display a dialog that will let the user upload a given CSV which contains the values needed for the bulk send operation.

The CSV upload dialog will also include an option to download a template CSV file that is pre-formatted with the correct number of columns for the template's recipients. This template CSV will also include a single row of example values to guide users in proper formatting.

The CSV file should align with the recipient order in the template editor. For instance, a single recipient template will require one column, while a template with multiple recipients will have columns like recipient_1, recipient_2, etc. Blank values in the uploaded CSV will default to the preset values in the template, supporting scenarios where some recipient data remains fixed while others are dynamically replaced.

To handle varying scales of uploads, the CSV processing will trigger a background task. This task will iterate over the file to create documents sequentially, with size limits of 4MB or 100 rows. Users will receive email notifications both upon completion and in case of any errors. This functionality is limited to the application UI, as API support for bulk sending is already achievable using custom logic.

Summary

  • Add a bulk send feature to templates view with a CSV upload dialog.
  • Include an option to download a template CSV with the correct recipient columns and example values.
  • Default blank CSV fields to preset template values.
  • Process uploads using a background task with file size and row count limits.
  • Notify users via email on task completion or errors.
  • Restrict the feature to the application UI with no additional API support.
Originally created by @Mythie on GitHub (Dec 20, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1550 Originally assigned to: @Mythie on GitHub. On the template view page `/templates/[id]` or when on the template table `/templates` we should have an option either in the top corner or within the actions menu to bulk send the given template using a CSV ("Bulk send via CSV"). This will display a dialog that will let the user upload a given CSV which contains the values needed for the bulk send operation. The CSV upload dialog will also include an option to download a template CSV file that is pre-formatted with the correct number of columns for the template's recipients. This template CSV will also include a single row of example values to guide users in proper formatting. The CSV file should align with the recipient order in the template editor. For instance, a single recipient template will require one column, while a template with multiple recipients will have columns like `recipient_1`, `recipient_2`, etc. Blank values in the uploaded CSV will default to the preset values in the template, supporting scenarios where some recipient data remains fixed while others are dynamically replaced. To handle varying scales of uploads, the CSV processing will trigger a background task. This task will iterate over the file to create documents sequentially, with size limits of 4MB or 100 rows. Users will receive email notifications both upon completion and in case of any errors. This functionality is limited to the application UI, as API support for bulk sending is already achievable using custom logic. ### Summary - Add a bulk send feature to templates view with a CSV upload dialog. - Include an option to download a template CSV with the correct recipient columns and example values. - Default blank CSV fields to preset template values. - Process uploads using a background task with file size and row count limits. - Notify users via email on task completion or errors. - Restrict the feature to the application UI with no additional API support.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 20, 2024):

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:2556136601 --> @github-actions[bot] commented on GitHub (Dec 20, 2024): 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)
Author
Owner

@FurquanAnwer commented on GitHub (Dec 24, 2024):

Please assign me this !

<!-- gh-comment-id:2560875890 --> @FurquanAnwer commented on GitHub (Dec 24, 2024): Please assign me this !
Author
Owner

@jooncheez commented on GitHub (Jan 6, 2025):

Really need this in order to bulk send documents for signing. Can't replace Docusign without it.

<!-- gh-comment-id:2572329072 --> @jooncheez commented on GitHub (Jan 6, 2025): Really need this in order to bulk send documents for signing. Can't replace Docusign without it.
Author
Owner

@ElTimuro commented on GitHub (Jan 9, 2025):

@FurquanAnwer Any Update here? :) Let us know, if you are working on this.

<!-- gh-comment-id:2580592882 --> @ElTimuro commented on GitHub (Jan 9, 2025): @FurquanAnwer Any Update here? :) Let us know, if you are working on this.
Author
Owner

@FurquanAnwer commented on GitHub (Jan 9, 2025):

I got stuck with some other problems. Please assign it to someone else

On Thu, 9 Jan, 2025, 9:08 pm Timur Ercan, @.***> wrote:

@FurquanAnwer https://github.com/FurquanAnwer Any Update here? :) Let
us know, if you are working on this.


Reply to this email directly, view it on GitHub
https://github.com/documenso/documenso/issues/1550#issuecomment-2580592882,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKUZMYP4RBWCPY7M3X3WJ3L2J2JZHAVCNFSM6AAAAABT6HLDIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBQGU4TEOBYGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:2580598730 --> @FurquanAnwer commented on GitHub (Jan 9, 2025): I got stuck with some other problems. Please assign it to someone else On Thu, 9 Jan, 2025, 9:08 pm Timur Ercan, ***@***.***> wrote: > @FurquanAnwer <https://github.com/FurquanAnwer> Any Update here? :) Let > us know, if you are working on this. > > — > Reply to this email directly, view it on GitHub > <https://github.com/documenso/documenso/issues/1550#issuecomment-2580592882>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKUZMYP4RBWCPY7M3X3WJ3L2J2JZHAVCNFSM6AAAAABT6HLDIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBQGU4TEOBYGI> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
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#437
No description provided.