Help with Dynamic Email Input in HTTP Request Node Failing with “No Execution Data Available

[sylvioavilla1]

Hi everyone,

I’m trying to dynamically pass an email value in an HTTP Request node using the following expression in the body parameters:

={{ $fromAI("email", "ask for the user email") }}

The goal is for the flow to request the email dynamically (e.g., using AI or another method) and then send it in the user_email field to my Bubble API. However, whenever I use this expression, I get the following error:

{
  "errorMessage": "No execution data available",
  "errorDetails": {},
  "n8nDetails": {
    "itemIndex": 0,
    "runIndex": 0,
    "parameter": "parametersBody.values",
    "time": "23/01/2025, 17:06:56",
    "n8nVersion": "1.74.3 (Cloud)",
    "binaryDataMode": "filesystem",
    "cause": [
      {
        "name": "Type",
        "valueProvider": "fieldValue",
        "value": "purchase_info"
      },
      {
        "name": "user_email",
        "valueProvider": "fieldValue",
        "value": "={{ $fromAI(\"email\", \"ask for the user email\") }}"
      }
    ]
  }
}

However, if I replace the user_email value with a static email (e.g., [email protected]), the flow works perfectly.

Here’s a quick breakdown of my setup:

Node: HTTP Request (POST Method)
API: Bubble.io endpoint
Headers: Authorization (Bearer token)
Body Parameters:
Type → Static value: purchase_info
user_email → Dynamic value: ={{ $fromAI("email", "ask for the user email") }}
I suspect the problem is that {{ $fromAI(...) }} is not resolving properly, but I’m not sure how to dynamically collect and inject the email value into the body.

I’ve tried:

Using the expression as is
Testing with a static email (works perfectly)
Checking execution data logs, which suggest the user_email value is unavailable.
Any ideas on how to properly collect the email dynamically or resolve this issue? Should I use a Set or Code node, or is there a better way to make this work with AI-like inputs?

Thank you in advance for your help!

Information on your n8n setup
**n8n version: 1.76.1 (Latest Beta)
**Database (default: SQLite):default
**n8n EXECUTIONS_PROCESS setting (default: own, main):default
**Running n8n via (Docker, npm, n8n cloud, desktop app):cloud
**Operating system:windows

[Joffcom]

Hey @sylvioavilla1,

We have created an internal ticket to look into this which we will be tracking as "N8N-8220"

[sylvioavilla1]

Tks Em qui., 23 de jan. de 2025 18:53, Jon ***@***.***> escreveu:

…

Hey @sylvioavilla1 <https://github.com/sylvioavilla1>, We have created an internal ticket to look into this which we will be tracking as "N8N-8220 <https://linear.app/n8n/issue/N8N-8220>" — Reply to this email directly, view it on GitHub <#12820 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ6M3QNQLJPWFH7EPE7U2X32MFQEDAVCNFSM6AAAAABVYK4332VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJRGA4TGMJYGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>