@vinit I was wondering if you could peek at this and determine why I’m getting a 400 error on this API call. I repeated everything from Sendgrid’s “try it out” feature to add a recipient to my contacts list and it works there with my API key, but once I try the exact same set up in the bot I get this error.
I’ve tried a few variations to see if I could get past the error, but haven’t been successful. On the flip side, if I change this from POST to GET, it pulls in my contact list from the SendGrid account just fine. So I know the API authentication and URL are correctly set up.
I would be using JSON that would look like this in the bot (I just used their example for test to remove variables):
[
{
“email”: “{{ursp.email}}”,
“first_name”: “{{ursp.name}}”
}
]
Hi Levi,
It may be the formatting of the code you are using. I tried several versions and modifications from sendgrid docs until I got this one to work:
Hi Mark,
Funny story, my ticket submission bot uses that api from SendGrid to send it’s auto-reply with the user’s unique reference code.The previous code you referenced has a duplicate “personalization” in the documentation, which causes the hiccup.
What I’m trying to do is add a receipent to a SendGrid contact list in my account. This will be used to send a single email to subscribers when appointments for REAL ID in Montana will be available. The email will be off of their templated email response. It will include a link directly to the scheduler to set up their appointment, and a link to download a custom document checklist (it also has an automated bot counterpart that can step you through to find out if you have the correct documents or not).
Only problem is the api is not working in the bot. As far as I can tell, everything is configured to SendGrid’s exact specifications on this other api.
Hi Levi,
Oh, got it! That’s a cool setup! Haven’t worked with the sendgrid contact lists yet. Sounds like a great application for what you’re trying to accomplish. I will watch this thread to see how it works out for you, maybe Vinit will have some insights. And yes, noticed some inconsistencies in their docs in places. I’m really loving this sendgrid API integration overall as it’s making the bots even more effective for my applications, and sounds like for you as well. Cheers!
It looks like the Data Body Format is correct. Certainly no issue with JSON syntax, otherwise the in-gambit editor would cry.
Maybe double check the API token (Authorization Header)
Also, try to make the same API call using POSTMan Client. See if you are facing the same issue. If yes, then something wrong with the Sendgrid API, maybe deprecated. Ping them a message.
I ran it in POSTman and it worked without an issue. I copied everything from the bot into POSTman to keep it consistent. It must be something on the bot’s end. Very strange…
We eventually came up with a solution to this using our WordPress site to first collect the user information through a gravityforms api. We ran that to pull the user’s first name and email address and store it into the wordpress site as a contact. Then we connected Sendgrid to the contact list and ran the API through that.
It successfully added new submissions to the sendgrid account. We signed up 1,200 people this way, and we sent them automated emails to new contacts weekly and then the whole group received our announcement that appointments were available. Every step was automated except for creating the email templates that were sent out to people (only two templates to handle everything).
Had we actually advertised this service with a little money, I have no doubt that we could have tripled our numbers, but still a great turn out for little work on our end!
