Pipedream SendGrid → n8n

3 Pipedream SendGrid actions and 2 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: sendgrid.

Actions

Pipedream action	n8n	Fit	Notes
sendgrid-send-email-single-recipient	Send Grid mail → send	Check output	PD always sends content as text/html, so contentType is fixed to 'text/html'. n8n contentValue is required when dynamicTemplate=false. Attachments: PD dynamic props attachmentsName<i>/attachmentsPath<i> (URLs or /tmp paths) need preceding HTTP Request/Read…
sendgrid-send-email-multiple-recipients	Send Grid mail → send	Partial	Low confidence because of the privacy-relevant recipient grouping difference described in transforms.toEmails. Attachments are handled as for single recipient.
sendgrid-add-or-update-contact	Send Grid contact → upsert	Check output	Same endpoint and body shape (list_ids + contacts[0]). If only addressLine2 is set, n8n also sends address_line_1 as undefined (harmless).

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
sendgrid-new-contact	Schedule Trigger + polling	Partial	There is no SendGrid trigger in n8n. Recommend Schedule Trigger (PD timer interval) + SendGrid node resource 'contact', operation 'getAll' with filters.query (SGQL, e.g. created_at BETWEEN TIMESTAMP '<from>' AND TIMESTAMP '<to>') + Remove Duplicates on id.
sendgrid-events	Schedule Trigger + polling	Partial	There is no SendGrid trigger in n8n. Use a generic Webhook node (POST) and configure SendGrid's Event Webhook URL and event types manually; PD set these via the API, overwriting the account's single event webhook. Add a Split Out on the body array and a…

Credentials

Create a SendGrid credential in n8n (type sendGridApi). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a SendGrid node?+

Yes. 3 of the 3 Pipedream SendGrid actions listed here map to a native n8n node.

Will my Pipedream SendGrid connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a SendGrid credential in n8n (type sendGridApi) and select it on the converted nodes.

Are Pipedream SendGrid triggers supported in n8n?+

n8n has no trigger node for these SendGrid events. Converted workflows use a Schedule Trigger that polls the API, or a Webhook node registered in SendGrid.

What happens to code steps that call the SendGrid API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Asana Calendly ClickUp Discord Dropbox Email (SMTP)GitHub Gmail Google Calendar Google Drive Google Gemini All apps →