SendGrid n8n integrationAutomate SendGrid with n8n.

Sends one contact to SendGrid and lets the address decide the outcome: an unknown email creates the contact, a known email updates the record already stored.

• Email: the primary email of the contact (name@email.com), most often {{ $json.email }} when the address arrives from a form.
• List IDs: in Additional Fields, the lists the contact joins right away, which saves a second call later.
• First Name, Last Name, Country: optional identity fields a template can print back into the email.

Removes contacts from the SendGrid account. Two ways in: a list of identifiers, or the switch that clears everything at once.

• Contact IDs: the ID of the contact to remove, and several IDs separated by a comma when a cleanup batch arrives in a single item.
• Delete All: turned on, every contact goes. Leave it off unless erasing the whole audience really is the goal.

Pulls a single contact back, by identifier or by address, and hands the stored record to the next node.

• By: the lookup mode, id or email. It decides which of the next two fields the node reads.
• Contact ID: the ID of the contact, used by the id mode.
• Email: the email of the contact (name@email.com), used by the email mode, often {{ $json.email }}.

Reads contacts in bulk, with or without a search filter, and pushes one item per contact into the rest of the workflow.

• Return All: on, n8n walks through the pages of the SendGrid API until the last contact. Off, it stops at Limit.
• Limit: the maximum number of contacts to return while Return All stays off, which keeps a test run short.
• Query: in Filters, an SGQL expression, the SendGrid query language for searching a contact.

Creates an empty list in SendGrid and returns its identifier, which the following nodes use as a destination.

• Name: the name of the list, required, and the only field this operation asks for.

Drops a list from the account. A second switch decides what happens to the contacts sitting on it.

• List ID: the ID of the list, required, usually read from list.getAll rather than typed by hand.
• Delete Contacts: on, the contacts on that list are deleted too. Off, only the list goes.

Returns one list and its details, with the option of bringing back a sample of the contacts it holds.

• List ID: the ID of the list to read, required.
• Contact Sample: on, the response carries the contact sample, which is enough to eyeball what actually landed in the list.

Brings back the lists of the account, which is how a workflow finds an ID without anyone copying it out of the SendGrid interface.

• Return All: on, n8n pages through the API until every list has come back. Off, it stops at Limit.
• Limit: the maximum number of lists returned, handy while the workflow is still being built.

Renames an existing list. Both fields are required, so the node never sends an empty label to SendGrid.

• List ID: the ID of the list to rename, required.
• Name: the new name of the list, also required.

Sends the email itself, either with content written in the node or through a SendGrid dynamic template filled with workflow data.

• Dynamic Template: required. On, the email uses a template and its fields. Off, it uses the content written below.
• Message Body: required, the body of the email to send.
• Recipient Email, Sender Email, Subject: the comma-separated recipients, the sending address, the subject line.
• MIME Type: text/plain or text/html.
• Send At: the delivery moment, never more than 72 hours ahead.