Using $fromAI in a HTTP Request tool

Hi there,

I am trying to use this url in a HTTP Request tool

https://3.basecampapi.com/4488205/buckets/{{ $fromAI(‘projectId’) }}/todosets/{{ $fromAI(‘todosetId’) }}/todolists.json

It seems that if I try to send it as a text message via telegram, the AI gets it and populate vars,

But somehow, when it comes to HTTP Request url, the AI is either not triggered or doesn’t know how to populate vars.

Is this a known problem ? Is there a whay around ?

Thanks !

instance information

Debug info

core

  • n8nVersion: 1.83.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.3
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 7f877407-8aab-4d95-86d2-d489d9034e3e

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/130.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2025-03-18T11:49:45.937Z

hello @Basile_Bernard

Please, share the workflow.

You can select all nodes with ctrl+a, copy it with ctrl+c. Then past the content here after pressing button </> with ctrl+v.

Here it is :slight_smile:

You can see that I use either the http request or the telegram to do the same thing, (generate the url from $fromai) and it only works with telegram, not http request)

and yes, when I try (copy paste) with the value that comes out of telegram, the http request works, hence the $fromai gives the correct values

More explicitly, the response when I try to test is
“no execution data available”

yet, when I try the same exact url as a message with telegram, works like a charm

Can you provide a screenshot of the issue? Seems the AI Agent node is custom (I don’t have that node)


and anyway, I can’t get it to work because I get this error message

try that one

@barn4k I ran into the same issue. Your fix worked, but only once I changed the AI Agent from a Plan and Execute Agent to a Tools Agent. I’m not sure what it happened.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.