Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: bulk send templates via csv #1578

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Mythie
Copy link
Collaborator

@Mythie Mythie commented Jan 11, 2025

Description

Implements a bulk send feature allowing users to upload a CSV file to create multiple documents from a template. Includes CSV template generation, background processing, and email notifications.

image image image

Changes Made

  • Added TemplateBulkSendDialog with CSV upload/download functionality
  • Implemented bulk send job handler using background task system
  • Created email template for completion notifications
  • Added bulk send option to template view and actions dropdown
  • Added CSV parsing with email/name validation

Testing Performed

  • CSV upload with valid/invalid data
  • Bulk send with/without immediate sending
  • Email notifications and error handling
  • Team context integration
  • File size and row count limits

Resolves #1550

Adds the ability to bulk send a template using a CSV.

Uses a background job for processing the CSV and its rows with an email
being sent at the end containing all successful and errored entries.
Copy link

vercel bot commented Jan 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
stg-app ❌ Failed (Inspect) Jan 28, 2025 1:59am
stg-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 28, 2025 1:59am
5 Skipped Deployments
Name Status Preview Comments Updated (UTC)
prd-app ⬜️ Ignored (Inspect) Jan 28, 2025 1:59am
prd-docs ⬜️ Ignored (Inspect) Visit Preview Jan 28, 2025 1:59am
prd-marketing ⬜️ Ignored (Inspect) Jan 28, 2025 1:59am
prd-openpage-api ⬜️ Ignored (Inspect) Visit Preview Jan 28, 2025 1:59am
stg-marketing ⬜️ Ignored (Inspect) Jan 28, 2025 1:59am

Copy link
Contributor

coderabbitai bot commented Jan 11, 2025

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)
  • coderabbit

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

This pull request introduces a comprehensive bulk send feature for document templates. The implementation spans multiple components and services, enabling users to upload a CSV file to send multiple documents simultaneously. The feature includes a new dialog for bulk sending, job definitions for processing, and a TRPC router method to handle the upload and job triggering. The system supports file validation, recipient processing, and provides detailed email notifications about the bulk send operation.

Changes

File Change Summary
apps/web/src/app/(dashboard)/templates/[id]/template-page-view.tsx Added TemplateBulkSendDialog import and component instance
apps/web/src/app/(dashboard)/templates/data-table-action-dropdown.tsx Integrated new "Bulk Send via CSV" action with TemplateBulkSendDialog
apps/web/src/components/templates/template-bulk-send-dialog.tsx Created new dialog component for bulk CSV document sending
packages/email/templates/bulk-send-complete.tsx Added email template for bulk send completion notifications
packages/lib/jobs/client.ts Added BULK_SEND_TEMPLATE_JOB_DEFINITION to job definitions
packages/lib/jobs/definitions/emails/send-bulk-complete-email.ts Created job definition for sending bulk complete emails
packages/lib/jobs/definitions/internal/bulk-send-template.handler.ts Implemented handler for processing bulk send jobs
packages/lib/jobs/definitions/internal/bulk-send-template.ts Defined job definition for bulk template sending
packages/trpc/server/template-router/router.ts Added uploadBulkSend method to template router
packages/trpc/server/template-router/schema.ts Created schema for bulk send template mutation

Sequence Diagram

sequenceDiagram
    participant User
    participant BulkSendDialog
    participant TemplateRouter
    participant JobSystem
    participant DocumentProcessor
    participant EmailNotifier

    User->>BulkSendDialog: Upload CSV
    BulkSendDialog->>TemplateRouter: Submit bulk send request
    TemplateRouter->>JobSystem: Trigger bulk send job
    JobSystem->>DocumentProcessor: Process CSV rows
    DocumentProcessor-->>JobSystem: Track processing results
    JobSystem->>EmailNotifier: Send completion notification
    EmailNotifier-->>User: Bulk send summary email
Loading

Possibly related PRs

Suggested Labels

coderabbit, 🚨 e2e changes 🚨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added apps: web Issues related to the webapp version bump 👀 labels Jan 11, 2025
@Mythie Mythie requested a review from Copilot January 11, 2025 00:48
@Mythie
Copy link
Collaborator Author

Mythie commented Jan 11, 2025

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Jan 11, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 6 out of 12 changed files in this pull request and generated no comments.

Files not reviewed (6)
  • packages/lib/package.json: Language not supported
  • packages/lib/jobs/client.ts: Evaluated as low risk
  • apps/web/src/app/(dashboard)/templates/[id]/template-page-view.tsx: Evaluated as low risk
  • apps/web/src/app/(dashboard)/templates/data-table-action-dropdown.tsx: Evaluated as low risk
  • packages/trpc/server/template-router/schema.ts: Evaluated as low risk
  • packages/lib/jobs/definitions/internal/bulk-send-template.handler.ts: Evaluated as low risk
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 11

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6520bbd and 2877aff.

⛔ Files ignored due to path filters (2)
  • package-lock.json is excluded by !**/package-lock.json, !**/*.json
  • packages/lib/package.json is excluded by !**/*.json
📒 Files selected for processing (10)
  • apps/web/src/app/(dashboard)/templates/[id]/template-page-view.tsx (2 hunks)
  • apps/web/src/app/(dashboard)/templates/data-table-action-dropdown.tsx (3 hunks)
  • apps/web/src/components/templates/template-bulk-send-dialog.tsx (1 hunks)
  • packages/email/templates/bulk-send-complete.tsx (1 hunks)
  • packages/lib/jobs/client.ts (2 hunks)
  • packages/lib/jobs/definitions/emails/send-bulk-complete-email.ts (1 hunks)
  • packages/lib/jobs/definitions/internal/bulk-send-template.handler.ts (1 hunks)
  • packages/lib/jobs/definitions/internal/bulk-send-template.ts (1 hunks)
  • packages/trpc/server/template-router/router.ts (3 hunks)
  • packages/trpc/server/template-router/schema.ts (2 hunks)
🔇 Additional comments (6)
packages/lib/jobs/definitions/internal/bulk-send-template.ts (1)

1-37: Job definition is properly implemented

The job definition and schema are correctly defined, and the handler is appropriately imported and invoked.

packages/lib/jobs/definitions/emails/send-bulk-complete-email.ts (1)

1-39: Email job definition is correctly structured

The schema and job definition for sending bulk completion emails are well-implemented, ensuring type safety and adherence to the expected structure.

packages/lib/jobs/client.ts (1)

9-9: LGTM! Clean integration of bulk send job.

The bulk send template job definition is properly integrated into the jobs client.

Also applies to: 25-25

packages/email/templates/bulk-send-complete.tsx (1)

17-91: LGTM! Well-structured email template.

The component is well-organized with proper i18n support and conditional rendering of error messages.

apps/web/src/app/(dashboard)/templates/[id]/template-page-view.tsx (1)

115-115: LGTM! Clean integration of bulk send feature.

The TemplateBulkSendDialog is properly integrated with the required props.

apps/web/src/components/templates/template-bulk-send-dialog.tsx (1)

61-81: 🧹 Nitpick (assertive)

Consider using Blob URL cleanup in useEffect.

The URL.revokeObjectURL call should be in a cleanup function to ensure proper resource management.

+ import { useEffect } from 'react';

  const onDownloadTemplate = () => {
    // ... existing code ...
    const url = window.URL.createObjectURL(blob);
+   useEffect(() => {
+     return () => {
+       window.URL.revokeObjectURL(url);
+     };
+   }, [url]);
-   window.URL.revokeObjectURL(url);
  };

Likely invalid or redundant comment.

Comment on lines +129 to +134
}).catch((err) => {
console.error(err);

throw new AppError('DOCUMENT_SEND_FAILED');
});
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Include original error when sending document fails

Capture and include the original error message to aid in debugging.

Apply this diff:

     await sendDocument({
       documentId: document.id,
       userId,
       teamId,
       requestMetadata,
     }).catch((err) => {
       console.error(err);
-      throw new AppError('DOCUMENT_SEND_FAILED');
+      throw new AppError('DOCUMENT_SEND_FAILED', { cause: err });
     });
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
}).catch((err) => {
console.error(err);
throw new AppError('DOCUMENT_SEND_FAILED');
});
});
}).catch((err) => {
console.error(err);
throw new AppError('DOCUMENT_SEND_FAILED', { cause: err });
});
});

Comment on lines +79 to +82
const results = {
success: 0,
failed: 0,
errors: Array<string>(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Initialize errors array directly

You can initialize the errors array using shorthand syntax.

Apply this diff:

 const results = {
   success: 0,
   failed: 0,
-  errors: Array<string>(),
+  errors: [],
 };
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const results = {
success: 0,
failed: 0,
errors: Array<string>(),
const results = {
success: 0,
failed: 0,
errors: [],

Comment on lines +24 to +30
const ZRecipientRowSchema = z.object({
name: z.string().optional(),
email: z.union([
z.string().email({ message: 'Value must be a valid email or empty string' }),
z.string().max(0, { message: 'Value must be a valid email or empty string' }),
]),
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Simplify email validation schema

The email field in ZRecipientRowSchema can be simplified to allow for empty strings more concisely.

Apply this diff:

 const ZRecipientRowSchema = z.object({
   name: z.string().optional(),
-  email: z.union([
-    z.string().email({ message: 'Value must be a valid email or empty string' }),
-    z.string().max(0, { message: 'Value must be a valid email or empty string' }),
-  ]),
+  email: z.string().email({ message: 'Value must be a valid email' }).or(z.literal('')),
 });
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const ZRecipientRowSchema = z.object({
name: z.string().optional(),
email: z.union([
z.string().email({ message: 'Value must be a valid email or empty string' }),
z.string().max(0, { message: 'Value must be a valid email or empty string' }),
]),
});
const ZRecipientRowSchema = z.object({
name: z.string().optional(),
email: z.string().email({ message: 'Value must be a valid email' }).or(z.literal('')),
});

Comment on lines +47 to +49
if (!template) {
throw new Error('Template not found');
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Use consistent error handling with AppError

Instead of throwing a generic Error, use AppError for consistency and to provide meaningful error codes.

Apply this diff:

 if (!template) {
-  throw new Error('Template not found');
+  throw new AppError('TEMPLATE_NOT_FOUND');
 }

Committable suggestion skipped: line range outside the PR's diff.

Comment on lines +7 to +15
export interface BulkSendCompleteEmailProps {
userName: string;
templateName: string;
totalProcessed: number;
successCount: number;
failedCount: number;
errors: string[];
assetBaseUrl?: string;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Consider using a more specific type for errors.

Instead of using string[], consider defining an error interface to make the error structure more maintainable.

-  errors: string[];
+  errors: Array<{
+    message: string;
+    row?: number;
+    column?: string;
+  }>;
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export interface BulkSendCompleteEmailProps {
userName: string;
templateName: string;
totalProcessed: number;
successCount: number;
failedCount: number;
errors: string[];
assetBaseUrl?: string;
}
export interface BulkSendCompleteEmailProps {
userName: string;
templateName: string;
totalProcessed: number;
successCount: number;
failedCount: number;
errors: Array<{
message: string;
row?: number;
column?: string;
}>;
assetBaseUrl?: string;
}

Comment on lines +152 to +157
export const ZBulkSendTemplateMutationSchema = z.object({
templateId: z.number(),
teamId: z.number().optional(),
csv: z.string().min(1),
sendImmediately: z.boolean(),
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add CSV validations for better error handling.

Consider adding these validations to prevent issues during processing:

 export const ZBulkSendTemplateMutationSchema = z.object({
   templateId: z.number(),
   teamId: z.number().optional(),
-  csv: z.string().min(1),
+  csv: z.string()
+    .min(1)
+    .max(5 * 1024 * 1024) // 5MB limit
+    .refine(
+      (csv) => csv.includes('email,name'),
+      'CSV must include email and name headers'
+    ),
   sendImmediately: z.boolean(),
 });
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export const ZBulkSendTemplateMutationSchema = z.object({
templateId: z.number(),
teamId: z.number().optional(),
csv: z.string().min(1),
sendImmediately: z.boolean(),
});
export const ZBulkSendTemplateMutationSchema = z.object({
templateId: z.number(),
teamId: z.number().optional(),
csv: z.string()
.min(1)
.max(5 * 1024 * 1024) // 5MB limit
.refine(
(csv) => csv.includes('email,name'),
'CSV must include email and name headers'
),
sendImmediately: z.boolean(),
});

Comment on lines +83 to +112
const onSubmit = async (values: TBulkSendFormSchema) => {
try {
const csv = await values.file.text();

await uploadBulkSend({
templateId,
teamId: team?.id,
csv: csv,
sendImmediately: values.sendImmediately,
});

toast({
title: _(msg`Success`),
description: _(
msg`Your bulk send has been initiated. You will receive an email notification upon completion.`,
),
});

form.reset();
onSuccess?.();
} catch (err) {
console.error(err);

toast({
title: 'Error',
description: 'Failed to upload CSV. Please check the file format and try again.',
variant: 'destructive',
});
}
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add client-side CSV validation.

The CSV content is only validated server-side. Adding client-side validation would improve user experience by catching format issues early.

Consider adding CSV parsing and validation before submission:

const validateCSV = async (file: File) => {
  const content = await file.text();
  const rows = content.split('\n').map(row => row.split(','));
  
  if (rows.length > 100) {
    throw new Error('CSV exceeds 100 rows limit');
  }
  
  // Validate header row matches template
  const headers = rows[0];
  const expectedHeaders = recipients.flatMap((_, index) => [
    `recipient_${index + 1}_email`,
    `recipient_${index + 1}_name`,
  ]);
  
  if (!headers.every((h, i) => h === expectedHeaders[i])) {
    throw new Error('Invalid CSV format');
  }
};

Comment on lines +27 to +30
const ZBulkSendFormSchema = z.object({
file: z.instanceof(File),
sendImmediately: z.boolean().default(false),
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Add file size and row count validation to form schema.

The UI mentions limits (4MB, 100 rows) but the form schema only validates file type.

Add these validations to prevent unnecessary server requests:

 const ZBulkSendFormSchema = z.object({
-  file: z.instanceof(File),
+  file: z.instanceof(File).refine(
+    (file) => file.size <= 4 * 1024 * 1024,
+    'File size exceeds 4MB limit'
+  ),
   sendImmediately: z.boolean().default(false),
 });
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
const ZBulkSendFormSchema = z.object({
file: z.instanceof(File),
sendImmediately: z.boolean().default(false),
});
const ZBulkSendFormSchema = z.object({
file: z.instanceof(File).refine(
(file) => file.size <= 4 * 1024 * 1024,
'File size exceeds 4MB limit'
),
sendImmediately: z.boolean().default(false),
});

Comment on lines +509 to +519
await jobs.triggerJob({
name: 'internal.bulk-send-template',
payload: {
userId: user.id,
teamId,
templateId,
csvContent: csv,
sendImmediately,
requestMetadata: extractNextApiRequestMetadata(ctx.req),
},
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Consider rate limiting bulk operations.

The bulk send operation could be resource-intensive. Consider adding rate limiting.

Add a rate limit check before triggering the job:

const BULK_SEND_RATE_LIMIT = 5; // operations per minute
const rateLimitKey = `bulk-send:${user.id}`;

// Add rate limiting logic before triggering job
const currentCount = await redis.incr(rateLimitKey);
if (currentCount === 1) {
  await redis.expire(rateLimitKey, 60);
}

if (currentCount > BULK_SEND_RATE_LIMIT) {
  throw new TRPCError({
    code: 'TOO_MANY_REQUESTS',
    message: 'Rate limit exceeded for bulk operations',
  });
}

Comment on lines +489 to +494
if (csv.length > 4 * 1024 * 1024) {
throw new TRPCError({
code: 'BAD_REQUEST',
message: 'File size exceeds 4MB limit',
});
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add content type validation for CSV.

The file size check is good, but additional content validation would improve security.

Add basic CSV content validation:

+ const isValidCSV = (content: string) => {
+   const firstLine = content.split('\n')[0];
+   return firstLine.includes(',') && /^[^<>]*$/.test(content);
+ };

  if (csv.length > 4 * 1024 * 1024) {
    throw new TRPCError({
      code: 'BAD_REQUEST',
      message: 'File size exceeds 4MB limit',
    });
  }
+ 
+ if (!isValidCSV(csv)) {
+   throw new TRPCError({
+     code: 'BAD_REQUEST',
+     message: 'Invalid CSV format',
+   });
+ }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if (csv.length > 4 * 1024 * 1024) {
throw new TRPCError({
code: 'BAD_REQUEST',
message: 'File size exceeds 4MB limit',
});
}
const isValidCSV = (content: string) => {
const firstLine = content.split('\n')[0];
return firstLine.includes(',') && /^[^<>]*$/.test(content);
};
if (csv.length > 4 * 1024 * 1024) {
throw new TRPCError({
code: 'BAD_REQUEST',
message: 'File size exceeds 4MB limit',
});
}
if (!isValidCSV(csv)) {
throw new TRPCError({
code: 'BAD_REQUEST',
message: 'Invalid CSV format',
});
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apps: web Issues related to the webapp version bump 👀
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bulk Send Template via CSV
1 participant