Overview
This node integrates with the SendGrid Marketing API to create new contacts in a marketing list. It is useful for automating the addition of contact information into SendGrid's marketing platform, enabling streamlined email marketing campaigns and audience management.
Typical use cases include:
- Adding new subscribers collected from web forms or CRM systems directly into SendGrid.
- Automating contact creation as part of a larger marketing workflow.
- Enriching contact data with additional fields like first and last names.
For example, when a user submits their email and name on a website, this node can automatically add that person as a contact in SendGrid for future email campaigns.
Properties
| Name | Meaning |
|---|---|
| Primary email address of the contact to be created. | |
| Additional Fields | Optional extra information about the contact. Available options: First Name, Last Name. |
Output
The node outputs an array of JSON objects representing the response from the SendGrid API after attempting to create the contact(s). Each object corresponds to one execution iteration and contains the API's response data, typically including status information about the contact creation request.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the SendGrid Marketing API.
- The node makes HTTP PUT requests to
https://api.sendgrid.com/v3/marketing/contacts. - Proper configuration of the API key credential within n8n is necessary for successful authentication.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Providing improperly formatted email addresses may result in API errors.
- Network connectivity problems can prevent the node from reaching the SendGrid API.
Error messages:
- Authentication errors typically indicate invalid credentials; verify the API key setup.
- Validation errors from the API often point to missing required fields or invalid data formats; ensure the email is valid and required fields are provided.
- HTTP errors (e.g., 4xx or 5xx) suggest issues with the request or server; check the request payload and retry later if needed.