AAI Support Bot Information
@1116029602800881785 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.
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.
AAI Response
To address the issue with the dynamic template data not being passed correctly in your BuildShip flow, it's important to ensure that the context path you are using to access the data from the Supabase webhook is indeed correct.
Here are a few checks you can perform to troubleshoot this issue:
Here are a few checks you can perform to troubleshoot this issue:
- Verify Context Path: Double-check the context path
${ctx['root']['supabase-webhook']['record'].first_name}to ensure it matches the structure of the data coming from the webhook. Sometimes, the data structure might be slightly different, and you should refer to your webhook data to confirm the path. - Output Logs: Use logging within your flow to output the value of
${ctx['root']['supabase-webhook']['record'].first_name}to verify that it is being retrieved correctly. This will help confirm whether the issue lies with data retrieval or with sending it to SendGrid. - SendGrid Template: Ensure that your SendGrid dynamic template is correctly set up to receive the
first_namefield. There should be a placeholder in the SendGrid template that corresponds tofirst_name. - Test Template Separately: As a test, try sending the email without BuildShip, using the same SendGrid template and data to verify if the issue persists outside of BuildShip. This helps isolate whether the problem is with BuildShip or the SendGrid template setup.
- Update Node Output: If your node logic has changed, ensure that you update the node's output schema to align with the current logic. This can prevent data mismatches during execution【4:4†source】.
BuildShip AI Support
•10/31/24, 3:27 PM