-
Notifications
You must be signed in to change notification settings - Fork 67
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
Sendgrid: Destination Connector #390
Comments
Hey @Mohith93 can pick this to work on, kindly assign to me |
Hi @deveshchatuphale7 , I hope you're doing well! I wanted to follow up on this issue, you've been working on. Could you provide an update on the current status or let me know if you’re facing any challenges? I'm happy to assist or answer any questions you may have. Thank you for your continued contributions to the project. Your efforts are greatly appreciated, and we’re excited to see your progress! |
Hey @Mohith93 I have set up local environment & presently currently working on API integration & field mapping. Might need help in testing, will reach out on slack |
Checking in with you for any updates that you might have. Let us know on our slack for any questions or concerns. |
Hey @Mohith93 Apologies for the delay. |
**Feature Request: SendGrid Destination Connector
Issue Type: New Feature / Connector Request
Description
We need to build a SendGrid Destination Connector that allows users to send email and other messaging data from Multiwoven to SendGrid. This connector will help users automate email marketing, transactional emails, and other communications by integrating data from Multiwoven into SendGrid.
Requirements
Authentication:
The connector should support API Key authentication to interact with the SendGrid API. Users will need to generate an API key from their SendGrid account.
Configuration:
The connector should require the following configuration parameters:
api_key
: SendGrid API key.from_email
: The sender's email address.reply_to_email
for specifying a reply-to address.Connector Features:
The destination connector should be able to:
API Interaction:
The connector should use the SendGrid Web API for sending messages. API documentation can be found here:
SendGrid API Documentation
Data Format:
The data sent to SendGrid must follow SendGrid’s required structure for emails, including recipients, subject, body, and other metadata (e.g., tracking and template IDs).
Error Handling:
The connector should handle errors gracefully, providing meaningful error messages for common issues like invalid API keys, email addresses, or rate limits.
Steps to Implement
Authentication Setup:
Connector Configuration:
api_key
,from_email
, and optionallyreply_to_email
.API Integration:
Field Mapping:
Error Handling & Logging:
Testing:
Documentation:
README.md
that explains how to configure and use the connector.Acceptance Criteria
Resources
The text was updated successfully, but these errors were encountered: