Pipedream SendGrid steps in n8n

SendGrid is the transactional email step in many Pipedream workflows: a signup, an order or an alert sends one email. n8n has a native SendGrid node, and the most common Pipedream action converts without manual work.

The n8n side

SendGrid node (n8n-nodes-base.sendGrid):

Resource	Operations
Contact	Create/Update, Delete, Get (by ID or email), Get All
List	Create, Delete, Get, Get All, Update
Mail	Send

Mail → Send supports dynamic templates (template ID plus dynamic data), attachments from binary data, CC/BCC and send-at scheduling.

There is no SendGrid trigger node in n8n.

What maps where

Pipedream (app sendgrid)	In n8n	Status
Send Email Single Recipient	HTTP Request → POST /v3/mail/send with the SendGrid credential	automatic
Send Email Multiple Recipients	Mail → Send, or HTTP Request with personalizations	manual
Add or Update Contact	Contact → Create/Update	manual
Search Contacts, Delete Contacts	Contact → Get All / Delete	manual
Create Contact List	List → Create	manual
Add Email to Global Suppression, Validate Email	HTTP Request with the SendGrid credential	manual
New Events (Instant)	Webhook node + SendGrid Event Webhook settings	manual
New Contact (polling)	Schedule Trigger + Contact → Get All	manual

For the automatic step the converter builds the request body from the Pipedream props, so template IDs and dynamic data come along. You can later swap the HTTP Request for the SendGrid node if you prefer the form view; the result is the same API call.

SendGrid credentials in n8n

One type: API key. Create it in SendGrid under Settings → API Keys. The sender address must be a verified Single Sender or belong to an authenticated domain, otherwise mail/send returns 403 regardless of the key.

Typical migration: order confirmation

Pipedream: Shopify New Order → SendGrid Send Email Single Recipient (dynamic template). n8n: Shopify Trigger → HTTP Request (converted) with the same template ID and dynamic_template_data. Connect the SendGrid credential, run one test order, compare the email.

Event webhook

Pipedream's New Events (Instant) registered SendGrid's Event Webhook for you. In n8n:

1. Add a Webhook node (POST), activate the workflow, copy the production URL.
2. In SendGrid → Mail Settings → Event Webhook, paste the URL and pick events (delivered, bounce, open, click…).
3. SendGrid sends events as a JSON array; use Split Out to process one event per item.

SendGrid migration pitfalls

• Rate limits per endpoint. SendGrid limits each endpoint separately and returns 429; the endpoint stays blocked until the reset time in X-RateLimit-Reset. Contact searches inside loops are the usual cause.
• Marketing contacts are asynchronous. Contact → Create/Update returns a job ID; the contact appears a few seconds later. A Get right after Create can come back empty.
• One event webhook URL (unless you use SendGrid's multiple-webhooks feature): switching it to n8n stops Pipedream's source.

How to move your SendGrid workflows

1. Export the workflows from Pipedream.
2. Upload on /convert; the free report marks Send Email Single Recipient as automatic and lists the rest.
3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

Code steps that use @sendgrid/mail can be checked in the code step checker. Related: Mailgun, Mailchimp, Twilio.