(gemini): SendGrid - Send Email Action

[swerner]

Sends an email using SendGrid. Requires SendGrid API key, sender email, recipient email, subject, and body. Useful for sending notifications, reports, or summaries generated by AI processes to users.

[augmentations-ai]

This looks good! To ensure it's working as expected, could you add a section detailing how to manually test this action? Specifically, please include:

1. Setup: Instructions on setting the SENDGRID_API_KEY environment variable.
2. Execution: An example of how to instantiate and call SendgridSendEmailAction with sample data.
3. Verification: Steps to confirm the email was sent successfully (e.g., checking the recipient's inbox, reviewing SendGrid logs).
4. Error Handling: How to induce and verify the error handling (e.g., using an invalid API key). This is important to verify that error logging and re-raising exceptions is implemented correctly.

For example:

Manual Testing Instructions:

1. Setup:

   • Set the SENDGRID_API_KEY environment variable with your SendGrid API key:

     export SENDGRID_API_KEY="YOUR_SENDGRID_API_KEY"

2. Execution:

   • Instantiate and call the action in a Rails console or a test script:

     sender_email = "test@example.com" # Replace with your sender email
     recipient_email = "recipient@example.com" # Replace with your recipient email
     subject = "Test Email from SendGrid Action"
     body = "This is a test email sent using the SendGrid action."
     
     action = SendgridSendEmailAction.new(sender_email: sender_email, recipient_email: recipient_email, subject: subject, body: body)
     status_code = action.call
     
     puts "Email sent. Status code: #{status_code}"

3. Verification:

   • Check the recipient's inbox (recipient@example.com) to confirm the email was received.
   • Review your SendGrid activity feed to ensure the email was sent without errors.

4. Error Handling:

   • Set an invalid SENDGRID_API_KEY (e.g., export SENDGRID_API_KEY="invalid").
   • Run the same Ruby code as in step 2.
   • Verify that the action raises a StandardError and that the error is logged by Sublayer.configuration.logger.