WEWorkflow ExitFree report

Pipedream Gmail → n8n

10 Pipedream Gmail actions and 6 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 slugs: gmailgmail_custom_oauth.

Actions

Pipedream actionn8nFit
gmail-send-emailGmail
message → send
Check output
gmail-create-draftGmail
draft → create
Check output
gmail-find-emailGmail
message → getAll
Check output
gmail-modify-labelsHttp RequestCheck output
gmail-add-label-to-emailGmail
message → addLabels
Direct
gmail-remove-label-from-emailGmail
message → removeLabels
Direct
gmail_custom_oauth-send-emailGmail
message → send
Check output
gmail_custom_oauth-create-draftGmail
draft → create
Check output
gmail_custom_oauth-find-emailGmail
message → getAll
Check output
gmail_custom_oauth-add-label-to-emailGmail
message → addLabels
Direct

Triggers (event sources)

Pipedream triggern8nFit
gmail-new-email-receivedGmail Trigger
messageReceived
Check output
gmail-new-email-matching-searchGmail Trigger
messageReceived
Direct
gmail-new-labeled-emailGmail Trigger
messageReceived
Partial
gmail-new-sent-emailGmail Trigger
messageReceived
Check output
gmail_custom_oauth-new-email-receivedGmail Trigger
messageReceived
Check output
gmail_custom_oauth-new-email-matching-searchGmail Trigger
messageReceived
Direct

Credentials

Create a Gmail credential in n8n (type gmailOAuth2). 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 Gmail node?+

Yes. 9 of the 10 Pipedream Gmail actions listed here map to a native n8n node; 1 map to n8n's HTTP Request node with the Gmail credential.

Will my Pipedream Gmail connection move to n8n?+

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

Are Pipedream Gmail triggers supported in n8n?+

6 of the 6 Pipedream Gmail event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

What happens to code steps that call the Gmail 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