AI Customer's Feedback Organisation

Built with n8n
1
2

I reviewed the workflow and found a few issues that could prevent it from working correctly:

  1. Email Converter Node Issue

    • The Email Converter node references data.urgencyColor, but I can’t see where urgencyColor is created in any previous node.

    • This will result in an undefined value and may break the email formatting.

    • Either create the field before this node or replace it with the existing color logic from the HTML Beautifier node.

  2. Gmail Message Node

    • The Info Message node sends:

      {{ $json.html }}

    • However, the previous node generates html_email, not html.

    • Verify the field names match all the way through the workflow.

  3. AI Agent Output Parsing

    • Your JSON formatter relies on strict formatting:

      Category:
Urgency:
Summary:
Sentiment:
Sender_Email:

    • If Gemini ever changes the format slightly, the regex parser will fail.

    • A more reliable approach is to force structured JSON output from the AI Agent instead of parsing text with regex.

  4. Merge Node Configuration

    • You’re merging data from Email, Typeform, and Webhook sources.

    • If more than one source triggers simultaneously, the Merge node may not behave as expected.

    • Consider separate processing branches or using a Switch node before merging.

  5. Google Sheets Node

    • The Google Sheets node appears to have empty documentId and sheetName values.

    • If these aren’t configured, data won’t be written to the sheet.

  6. Workflow Link

    • The button in the HTML email points to:

      http://localhost:5678/workflow/PAnBgczV5o605QSF

    • This only works on your local machine.

    • Anyone receiving the email won’t be able to access it. Replace it with a public or internal URL.

My biggest recommendation is to change the AI Agent to return JSON directly. That will eliminate the need for the regex parsing node and make the workflow much more reliable.