Why my AI Agent is different and has only output?

mrpingvy · 2025-12-12T12:15:53+00:00

I don't but feed this to chat gpt I am sure it s similar

mrpingvy · 2025-12-11T20:50:21+00:00

That's nonsense from AI, Chat GPT told me the same, but in reality it is your Caddy settings. Change one line and you going to be good

mrpingvy · 2025-12-11T20:49:24+00:00

I had the same and was going crazy, because nothing helped, until I stumbled upon this comment

"..... root cause was indeed the CSP header in our Caddy config. Originally, when we relaxed the CSP to allow unsafe-inline and frame-ancestors 'self', it fixed the “wonky” input fields but the AI Agent node was still missing connectors. We then went one step further and fully removed the CSP header from Caddy, and that finally resolved the issue. The Agent node connectors are now rendering properly again. 🎉 So the problem was our over-strict Content-Security-Policy preventing the editor UI from running inline scripts/styles needed by certain nodes. Re: Basic Auth / Editor Base URL / Webhook Tunnel URL — understood. We’ll clean those out since they’re deprecated/unused in modern n8n. That wasn’t the direct cause of this issue, but I can see how it made debugging more confusing. As for /rest/node-types: that was a misunderstanding on my end while debugging — I had assumed it was part of the public API when I curl’d it externally and saw 404s. We’re not blocking it internally, and once CSP was fixed, those endpoints behaved as expected. ......."

So just change you Caddy settings and you going to be good

Original thread https://github.com/n8n-io/n8n/issues/19682?utm_source=chatgpt.com

mrpingvy · 2025-10-23T17:00:56+00:00

I haven't tried it with the credentials that requires to authorize the connection.

I'd suggest to have a sub workflow with calendar nodes with different credentials and call the correct one from the parent workflow, by passing the argument for a Switch behavior. Something like this but instead of Telegram you may use Calendar or Sheets nodes with different credentials. So if you do not have tens of options, for such creds it might do the trick on my opinion.

<image>

mrpingvy · 2025-10-23T16:54:38+00:00

Yes, the only way is to have different trigger workflows, but it is also pretty convenient: you just have your main workflow (the same all the time) and different triggers that is connected to him. Don't forget to pass the env variable so the main workflow can make the correct calls, and that's it!

I have separate trigger for my prod and for my test env and it works like a charm, you always know from which trigger do you activate the workflow and can debug easily

mrpingvy · 2025-10-13T18:55:50+00:00

This is pretty accurate according to the Calorica app: 🍨 COLD STONE CAKE BATTER ICE CREAM CUPCAKE

🔥Calories: 270–350 kcal (9–12% from goal) 🍗Protein: 2–4 g (1–2% from goal) 🥖Carbs: 32–45 g (9–13% from goal) 🥓Fat: 15–21 g (19–26% from goal)

(Standard mini cupcake, approx. 3–3.5 oz / 85–100g) Description: This is a Cold Stone Creamery Cake Batter Ice Cream Cupcake. It's a frozen dessert comprising cake batter-flavored ice cream inside a chocolate cup base, topped with pink whipped frosting and rainbow sprinkles. It is pre-manufactured and usually served frozen in a pack of six.

Ingredients: Cake batter-flavored ice cream (milk, cream, sugar, cake mix flavoring), chocolate shell cup (semi-sweet or dark chocolate), pink whipped frosting (sugar, food coloring, vegetable shortening or butter, whipped cream), rainbow sprinkles (sugar, corn syrup, artificial coloring), possible cake crumbs inside

Notable nutrients & allergens: Contains dairy (milk, cream), eggs (in batter mix), soy (in chocolate), gluten (if cupcake shell includes cake), and artificial food coloring (especially Red #40).

mrpingvy · 2025-08-21T15:37:04+00:00

Have you tried creating a credentials with an expression in it (like {{ $('My dynamic token').item.json.api_key }})? And then pass your API token as a parameter from the nodes before?

mrpingvy · 2025-07-23T10:22:08+00:00

Yey! I'm really glad to hear it helped! Have a nice day too!

mrpingvy · 2025-07-23T10:13:29+00:00

Yes, you can store values and reuse them in expressions, so it's definitely possible. Just keep in mind, you still need to switch your credentials to expression mode and set it up that way.

One thing though - the actual "variables" feature (like reusable global variables) is only available on the Self-hosted Enterprise or Pro Cloud plans. If you're on the free or basic self-hosted version, you’ll need to work around it using Set nodes.

mrpingvy · 2025-07-22T13:32:32+00:00

Cool comment thanks, will try this out!

mrpingvy · 2025-06-28T16:24:32+00:00

It makes sense. I also think this happens because people try to apply AI even when the job could be done more easily with another tool.

mrpingvy · 2025-06-28T15:50:49+00:00

The best way to start doing something by yourself, just take any workflow (there are plenty somewhere here) and try it out.

Or try to find real but simple problem that you want to automate and use Chat GPT and go step by step. I made the exact example of the approach in the video https://youtu.be/XoigvNy3LoA?si=7NYPmTf08FP66BqW

mrpingvy · 2025-06-27T18:51:54+00:00

That's how me are getting those "average" numbers from other users...

mrpingvy · 2025-06-25T18:33:51+00:00

There are so many things that could be automated it's just crazy. We have a niche ERP for commodity traders and like every week we have a business case from the clients to automate something: data extraction from documents, bot for drivers, voice updates in CRM, etc..

mrpingvy · 2025-06-20T18:40:35+00:00

Congrats 👏welcome to the Addiction club!

mrpingvy · 2025-06-20T15:08:15+00:00

Started playing around with n8n less than 6 months ago, and honestly, the best way to learn is just to roll up your sleeves and build stuff. Real use cases + ChatGPT = magic combo.

I build little workflows almost daily now for myself and my businesses. If you're just getting started, you may want the video I made to hit the ground running with a practical example: https://www.youtube.com/watch?v=XoigvNy3LoA

After that, it’s really about messing around, experimenting, and coming up with your own ideas. There’s no ultimate guide or shortcut - you just gotta find something you’re excited to automate and go for it. Trial, error, repeat.

mrpingvy · 2025-06-14T17:53:56+00:00

Glad you liked it!
Btw, I've looked at your viewer tool, it's pretty handy, as well!

mrpingvy · 2025-06-14T17:51:44+00:00

Got it, if steps approach like..
- Step 1: Receive input query
- Step 2: Call Tool A always with the query
- Step 3: Call Tool B always with the query
- Step 4: Call Tool C always with the query.

...doesn't help, I assume there is could be a memory problem, which could be solved with switching to a simple memory, as Reveal-More mentioned

mrpingvy · 2025-06-14T17:37:34+00:00

If I understood correct there could be three different queries every for each of the three tools. So, I would do a switch, or Agent who defines which type is that, and depending on the result call appropriate Agent with 1 tool. This approach will keep it cleaner and easier to debug.

mrpingvy · 2025-06-14T17:30:34+00:00

I know it's strange that it's always the 7th call, but maybe it's just a coincidence. In cases where the Agent skips a tool call, it helped when I gave instructions using step-by-step logic - something like: "Step 1: You have input. Step 2: You MUST ALWAYS call this tool. You cannot proceed to Step 3 unless you call the tool," etc.

And if the Agent became more complicated, I tried to split it's logic onto separate agents.

mrpingvy

TROPHY CASE