Current resource for SendGrid - templates endpoint with a template id does not have the option to input parameters. I need at least the templiate_id to retrieve the response. Am I doing something wrong here? Or is there a better way to retrieve the HTML from my SendGrid templates?
Hey @Jay_Yu, can you share what version you are on? Tested this out on cloud and v3.20 and see the option to set the template ID in the path. Let me know and I can take a look. Thanks!
1 Like
Hey Joe, sorry for the late reply! As it goes with being busy.
I am not sure where you can find the Retool version that I am using but I looked at the GET /templates/{template_id} endpoint for the integrated SendGrid resource and it still does not have the option to input a template id. Maybe I am not understanding how to use this correctly?
Thanks!
Best,
Jay
Hey @Jay_Yu, I was finally able to reproduce the issue. Seems like this field doesn't immediately show up for all Sendgrid resources. I've submitted a bug report to and can update you here as I get any additional information on its status.
In the interim, I did find that switching the endpoint to a different one with a path variable and then switching back to the /templates/{template_id} endpoint showed the appropriate field. Can you give that a try and see if it shows up for you?
1 Like
I have been trying to use:
GET /marketing/singlesends/{id}
I have been trying to trick the sendgrid api for hours...
But I can't get any sendgrid GET resources that requires {id} to show queryParameter dropdown
1 Like
Hey @tech_ea, the eng team is looking into this. I'll update here as I get updates from them. Thanks.
Hey all, haven't visited the forum in a while but my update is that I have been using the REST Resource Query instead of the built in SendGrid Resource Query. Cheers
1 Like
Hey, any updates on this? I think otherwise we would need to switch for the REST query as it seems still broken. Little inconvinient to have Sendgrid resource but still needed to switch to REST query on some endpoints.
Hello @eljass,
Unfortunately no update. In our internal logs it appears that the issue is ready for work but has yet to be assigned.
Our engineers are very busy and we would like to apologize as it is not ideal to have to use a REST API in conjunction with a Sendgrid resource.
I just added your +1 to the ticket thread so this should add weight to the ticket and might raise its priority in getting assigned.
1 Like
Hi @Jack_T - want to follow up that I'm experiencing a very similar issue. I have a very short python script hitting the SendGrid API working totally fine but when I use Retool's SendGrid resource query, I'm getting a 400 error around the template_id even though it's in there. Do I need to switch to just using REST and bailing on the SendGrid resource?
Update here is that when using the SendGrid builder, Retool automatically puts the content field in which when provided with template_id breaks it with the error message you see. In my local test, I can reproduce this by including the line that's commented out. When I comment it out locally, it works, and I get the email, except when I use the JSON body to edit to remove the content param and create an identical payload as what I have successfully working locally it tells me I'm "forgetting to include a return statement." I'm not really sure what this means and can't reproduce it locally so I'm guessing it's a Retool thing?
Very related post: SendGrid - Get Request for templates with id - #10 by Alex_ModernFi
Final update: this is giving a 202 (Success) but also prints out the undefined warning. Not sure why, but it's working, just spent over an hour trying to figure out why it wasn't
1 Like
Hello @Alex_ModernFi,
Thank you so much for documenting your testing! Apologize again for the issue and confusion around this.
I haven't seen a "Did you forget to include a return statement" message before 
very odd.
Since from your first screen shot it looks like you are sending a POST request it shouldn't need a return, maybe our query thinks that it should have a body returned with the success code. In this case I could make a bug report to remove this incorrect IDE error warning.
From your first comment it seemed like it was an issue with the Retool adding in that content field. I am glad you were able to get the 202 success, despite this unintended modification of the payload. It seems the error message is not interfering with the API sending the email.
I just checked sendgrid's API docs it seems that if wanted, you can have confirmation data or error messages sent to a webhook such as a Retool workflow endpoint.
Thank you again for the patients and perseverance! If you run into any other issues with our sendgrid resource, definitely make a post in the forums with the steps to reproduce so we can help.
1 Like
Thanks for getting back to me so quickly! yea I definitely think a bu report to get rid of the incorrect IDE warning would be helpful. Same with the weird content appearing. Appreciate the help!
2 Likes
I second that it'd be useful to remove that spurious (or at least innocuous) warning!
Today was my first time setting up and using a SendGrid resource and after some other hiccups I saw that undefined and was about to despair but thankfully I noticed the email still sent and everything else worked 
Mine was also just a POST to v3/mail/send. I too noticed that the JSON tab returned metadata with relevant details:
1 Like
Hi @dguzzo,
Happy to hear that the email dispatched worked! Apologies again from the less than ideal UX 
Just added in another ping on this ticket to increase its weight. It looks like this will be part of a bigger initiative to overhaul several OpenAPI packages that need fixes.
That is good to see the JSON returned relevant metadata to confirm everything went smoothly as expected.
1 Like
Experiencing the same issue, no way to input the template id for GET /templates/{template_id} or GET /templates/{template_id}/version/{version_id}
Hi @jamesg31,
Sorry to hear that. Could you share a screenshot of the error you are getting? Or are those file path routes not included in the dropdown options list?
Yeah of course - as you can see in this screenshot there is no way to provide a template_id for this call.
I have seen a couple other sendgrid requests that are also missing their options.
.
Thank you for sharing that! Just added your +1 to that ticket.
Will keep this thread updated with any news I hear from our engineering team.