Email verification with sendgrid

I’m reaching out for help with an issue I’ve encountered when trying to send transactional emails using SendGrid via Adalo’s Custom Actions. Here’s an overview of what I’m trying to achieve, what I’ve done so far, and where the issue lies:

What I’m Trying to Do:

  • I’m implementing an email verification flow using SendGrid.
  • After a user signs up in Adalo, I want to trigger a POST request to SendGrid’s API to send a verification email with a dynamic link.

Current Configuration:

  • API Endpoint: https://api.sendgrid.com/v3/mail/send
  • Headers:
    • Authorization: Bearer SG.xxxxxx... (using the full API key)
    • Content-Type: application/json
  • Body (Sample):

i used the code from an adalo expert youtuber who did what i was trying to do. for reference: https://www.youtube.com/watch?v=Ss6ow34uM38&ab_channel=PaoloMontemurro

{
  "personalizations": [
    {
      "to": [
        {
          "email": "Recipient Email",
          "name": "Recipient Name"
        }
      ],
      "subject": "Email Subject"
    }
  ],
  "from": {
    "email": "Your Email",
    "name": "Your Name"
  },
  "content": [
    {
      "type": "text/plain",
      "value": "Your OTP: Email Body"
    }
  ]
}

What I’ve Checked:

  1. The same API request works successfully when tested using cURL (with the same API key, payload, and endpoint).
  2. My SendGrid API key has Full Access and the sender email address is verified via Single Sender Verification.
  3. In Adalo:
  • The API request results in a 401 Unauthorized error.
  • I’ve confirmed there are no typos or trailing spaces in the API key.
  • I tested hardcoding the "email", "name", and "value" fields to rule out dynamic text issues.
  • I recreated the custom action from scratch, but the error persists.

Request:

Could you please help me identify why the request works in cURL but fails with a 401 in Adalo? Are there any known issues with SendGrid integration or additional configurations I need to make in Adalo’s Custom Actions?

Thank you in advance for your assistance!

Hi @Hoov,

As the response is 401 Unauthorized, most probably there is an issue with the Authorization in the custom action config.
It is difficult to guess what exactly could be the issue without any screenshots or screen recordings.

Best,
Victor.

Thanks for the reply… i think i sorted myself out!