The /sendgrid command enables you to send emails and manage email campaigns through SendGrid. Perfect for:

• Sending transactional emails
• Managing email templates
• Scheduling emails
• Sending bulk emails
• Adding attachments

​

Basic Usage

Use the command to interact with SendGrid:

/sendgrid send email to recipient@example.com from sender@example.com subject "Hello!" message "Welcome to our service"

/sendgrid send email using template d-template123456 to user@example.com

/sendgrid schedule email to customer@example.com for tomorrow at 9am subject "Reminder"

​

Key Features

​

Email Sending

• Send to single or multiple recipients
• Add CC and BCC recipients
• Plain text or HTML content
• Use dynamic templates
• Schedule delivery

​

Template Management

• List email templates
• Use dynamic templates
• Personalize content
• Version control

​

Attachments

• Add file attachments
• Multiple file types
• Inline attachments
• Base64 encoding

​

Sender Management

• Verified senders
• Sender authentication
• From name customization

​

Example Commands

​

Basic Email

/sendgrid send to john@example.com from noreply@company.com subject "Welcome" body "Thanks for signing up!"

​

Multiple Recipients

/sendgrid send to recipient1@example.com cc recipient2@example.com, recipient3@example.com subject "Team Update"

​

Using Template

/sendgrid send using template ID d-abc123 to customer@example.com with data: name="John", amount="$50"

​

With Attachment

/sendgrid send to client@example.com subject "Invoice" body "Please find attached" attach invoice.pdf

​

Scheduled Email

/sendgrid schedule email for December 25 at 9am to list@example.com subject "Holiday Greetings"

​

List Templates

/sendgrid list all dynamic email templates

​

Email Content Types

• text/plain: Plain text emails
• text/html: HTML formatted emails
• multipart: Both text and HTML

​

Template IDs

SendGrid templates use prefixes:

• d-: Dynamic template ID
• v-: Version ID
• s-: Sender ID

​

Tips

• Verify sender addresses before sending
• Use templates for consistent branding
• Schedule emails using Unix timestamps
• Test with small batches before bulk sending