Unable to send dynamic email from Supabase trigger
Hi,
I setup a supabase trigger on insertion and was able to pull the record. I fetch the email address and name from the trigger and pass that as an input variable to the sendgrid send dynamic email node. Unfortunately I am running into an error when I test the send grid implementation.
Error: Bad Request
I tried running a the same node in a different workflow by manually adding the input values and it worked.
Any idea on how I could debug this?
5 Replies
AI Support Bot Information
<@430452502861709332> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
To troubleshoot the "Bad Request" error you are experiencing when using the SendGrid node with a Supabase trigger, consider the following steps:
1. Double-check Input Data: Ensure that the data passed to the SendGrid node from the Supabase trigger matches the expected format and type. Input issues such as missing required fields or incorrect data types could lead to errors.
2. Logs and Debugging: Review the logs to identify any discrepancies in the data being passed to the SendGrid node. Logs can often provide insights into what might be going wrong.
3. Input Validation: Verify if there are any validation rules applied to the inputs. Errors may arise if the inputs do not conform to the expected patterns or constraints.
4. Manual Test: As you already successfully tested the node manually, compare the inputs between the manual test and the automated run to identify any differences.
5. Error Details: Some APIs provide detailed error messages in the response body when a "Bad Request" error occurs. Check if SendGrid returns any additional information that can guide debugging.
Unfortunately, there isn't any information in the documentation or FAQ that directly addresses this specific issue. If the above steps do not resolve your problem, you might want to utilize BuildShip's support options for further assistance【6:0†buildship-docs.json】.
BuildShip AI Support
Jam
Jam | Console logs, network requests, and more
Click this link to see the video on app.buildship.com, with console logs, network tab and device information.
cc @Luis can you help check if the node requires update?
Solution
this has been fixed, thank you Luis and Gaurav