How can I dynamically inject an email into an HTTP Request node without encountering 'No Execution Data Available'?

Below is an explanation of what’s happening and how you can resolve the issue:

Why the Error Occurs

The $fromAI() function is designed to work only with app nodes that are connected to the Tools Agent (for example, Gmail, Notion, or Slack nodes). The HTTP Request node does not support the use of $fromAI() directly because it isn’t integrated with the Tools Agent’s context. As a result, the expression isn’t resolving and you’re getting the "No execution data available" error.

Recommended Approaches

1. Use a Set or Code Node:
   Capture the email output in a node that supports expressions (like a Set or Code node) before you call the HTTP Request node. For example, you could use a Set node to store the email obtained from $fromAI() and then reference that field later in the HTTP Request.

   Example Using a Set Node:

   JAVASCRIPTCopied
   // In a Set node, add a field 'user_email' with the value:
   {{ $fromAI("email", "ask for the user email") }}

   Then, in your HTTP Request node, reference the email from the previous node:

   JAVASCRIPTCopied
   {{ $json.user_email }}

2. Change the Node Type:
   If your use-case allows it, consider switching to an app node that directly supports dynamic inputs via the Tools Agent, rather than using the HTTP Request node.

Summary

Since the $fromAI() function only operates within the context of supported app nodes, the expression does not resolve correctly when used directly in an HTTP Request node. Using an intermediary node (like Set or Code) will allow you to capture the email output and then pass that value dynamically to your Bubble API.

This approach should resolve the error and enable your workflow to process the dynamic email as intended.

When you use the expression

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

in the HTTP Request node, the function doesn’t resolve because the $fromAI() helper is only supported in app nodes connected to the Tools Agent (such as Slack, Gmail, or Notion nodes). The HTTP Request node isn’t one of those, which is why it complains "No execution data available".

To work around this, you can capture the output of the $fromAI() call in an earlier step (for example, using a Set or Code node) that supports evaluating it. Once the email is stored as part of the workflow’s data, you can reference that value in your HTTP Request node using a standard expression (e.g., {{ $json.email }}).

In summary, you’ll need to:

1. Use a node that supports the $fromAI() expression (like an app node connected to the Tools Agent or a Set node if configured correctly) to get the email value.
2. Save the output (say, under the key “email”) from that node.
3. In the HTTP Request node, reference the stored value (for example, in the body parameter: {{ $json.email }}).

This approach ensures that the dynamic input from $fromAI() is captured properly before being passed to the HTTP Request node.