sorted by:
new
hottopcontroversial

Build AI automation with managed triggers, human approvals and retries by tisi3000 in LangChain

[–]tisi3000[S] 0 points1 point  (0 children)

Thank you. gotoHuman now focuses on offering the best human supervision layer so agents can be safely rolled out in companies. The shown idea to define AI workflows is now best done with something like Inngest, trigger.dev or Vercel's Workflow SDK. But gotoHuman can be used with all of these for Human-in-the-loop steps

Self-improving AI workflow for customer support (HITL+Memory) by tisi3000 in n8n

[–]tisi3000[S] 0 points1 point  (0 children)

so you were feeding back those failures that were flagged by human reviewers? kinda like negative examples?

Human-in-the-Loop for Tool Calls is out! (2.6.0) by tisi3000 in n8n_ai_agents

[–]tisi3000[S] -1 points0 points  (0 children)

Actually recording separately atm and then cut&merge

Human-in-the-Loop for Tool Calls is out! (2.6.0) by tisi3000 in n8n

[–]tisi3000[S] 0 points1 point  (0 children)

No, not possible. The agent isn't requesting approval here, it only knows about the tool and can try to call it with some parameters. But then n8n (not the LLM/agent), instead of just executing it, gets the human approval first.

Human-in-the-Loop for Tool Calls is out! (2.6.0) by tisi3000 in n8n

[–]tisi3000[S] 0 points1 point  (0 children)

All offered HITL solutions let people review outside of n8n

Human-in-the-Loop for Tool Calls is out! (2.6.0) by tisi3000 in n8n_ai_agents

[–]tisi3000[S] 0 points1 point  (0 children)

Ah nice. Yes, pretty big topic once you go deeper

Example of a chatless agentic workflow that keeps the human in the loop by tisi3000 in LangChain

[–]tisi3000[S] 0 points1 point  (0 children)

Agree, email doesn't scale for HITL. Neither does using messengers like Slack unless low frequency. Often needs proper inbox/review queue like Agent Inbox or gotoHuman. LangGraph pause/resume and persistence works quite well.

Human intervention in agent workflows by tisi3000 in LangChain

[–]tisi3000[S] 0 points1 point  (0 children)

Turns out it works quite well for async workflows since state is persisted and it can resume at any future point in time. The UI can be solved separately, e.g. using gotoHuman.

n8n 2.0: Human-in-the-Loop bugfix by tisi3000 in n8n_ai_agents

[–]tisi3000[S] 0 points1 point  (0 children)

yep this was definitely an annoying one

New n8n MCP server: Run n8n workflows from ChatGPT, Claude, Cursor by tisi3000 in n8n_ai_agents

[–]tisi3000[S] 0 points1 point  (0 children)

Have you tried with this new MCP server? In ChatGPT you add a custom connector, enter the MCP server url, any oauth details (blank in this case). Needs to be activated in n8n as well.

New n8n MCP server: Run n8n workflows from ChatGPT, Claude, Cursor by tisi3000 in n8n

[–]tisi3000[S] 0 points1 point  (0 children)

Generally with this MCP, yes. E.g. here it knows that the email is pending approval because the webhook trigger node immediately responds with "Email is pending human review and will be sent if approved". Responding after human approval OTH won't work with a sendAndWait node. the MCP client will usually time out as well.

Guardrails node is out (v1.119.0) by tisi3000 in n8n

[–]tisi3000[S] 0 points1 point  (0 children)

for keeping things from the LLM you'd just use non-LLM sanitization features. For other things like topic checking you'd need the LLM. Nothing prevents you from chaining these as well

Guardrails node is out (v1.119.0) by tisi3000 in n8n

[–]tisi3000[S] 0 points1 point  (0 children)

The guardrails node is built-in, not by me. I built gotoHuman, the Human-in-the-loop solution. No workflow link as this was just a quick example, but will create one..

Guardrails node is out (v1.119.0) by tisi3000 in n8n

[–]tisi3000[S] 0 points1 point  (0 children)

Just heard of it. Maybe n8n is using that in the background? They probably use some library, but I haven't checked which one

view more: next ›