SendGrid API Error Just Started

Questions
1

Describe the problem/error/question
Today on my SendGrid nodes they showed this error…these were all working and now do not. I created new API keys with FULL Access still don’t work. I checked my SendGrid account is paid and active and no issues there. Any thoughts

image
image2055×1007 100 KB

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

hello @CyberTigerTech

What’s inside the error message?

3

image
image1921×646 43.8 KB

Its strange these have been in place for months on multiple workflows. So I went into SendGrid made sure the account was in good standing. I have 100K limit and only send 6K this month so that is not it.

I created multiple new API keys with Full Access to troubleshoot and every key I create gets this message…I am at a loss and feel something change between N8N communication and SendGrid

4

Just for the sake of testing I just created a free trial account with sendgrid, got meself an api key and tried creating a Credential with it.

image
image1208×480 23.7 KB

I am running a self-hosted n8n v1.111.0

5

Forbidden means you have an issue with credentials. Maybe the token is not in the right format, or maybe you have copied some spaces/extra characters

6

Thanks I thought that but checked and I created at least a half dozen new keys to ensure each was new, full access.

7

Thanks man for going to that effort, yeah I am perplexed. This is a paid account with SendGrid that I have had for 7 years. I will try and create a new account and see what the results are.

8

That’s a good approach. If the new one works and the old one doesn’t, you will have something very solid to take to sendgrid’s support team.

9

I had this problem too. The API key doesn’t work with the node, so I moved to HTTP Request and it works well.

10

Eduardo thanks could you explain a little more not sure I follow how to setup

11

Well, you can’t say that it just doesn’t work. There is something that makes it work or not on sendgrid side for some. Works for me just fine on self-hosted 1.111.0.

12

How to send email via SendGrid using an n8n HTTP Request node (no SDK needed)

Quick setup

  1. Add an HTTP Request node

    • Method: POST

    • URL: https://api.sendgrid.com/v3/mail/send

  2. Headers

    • Authorization: Bearer {{$env.SENDGRID_API_KEY}}

    • Content-Type: application/json

    Tip: put your API key in an environment variable called SENDGRID_API_KEY (or hardcode while testing).

  3. Body → Raw → JSON

{
  "from": { "email": "[email protected]", "name": "Your App" },
  "personalizations": [
    { "to": [ { "email": "[email protected]" } ] }
  ],
  "subject": "Hello from n8n",
  "content": [
    { "type": "text/plain", "value": "It works" }
  ]
}

Expected response: 202 Accepted (SendGrid returns no body on success).

13

I have the same issue, api key works fine, suddenly not anymore.
After some digging, I read in this thread that the Sendgrid node uses a marketing/contacts api endpoint to test if the api key works. Now i see in my account that i don’t have access to this module, so maybe that’s the issue? @Jon Is this still the case? Maybe there is another endpoint that can be used to test the api key?