Build with AI

AI scenario helper is an AI assistant built into the Latenode Visual Builder. Describe your task in plain language and the assistant builds the scenario: it places nodes on the canvas, connects them, and fills in settings where possible.

The result is a normal Latenode scenario. You can open it, inspect it, edit it, test it, and publish it like any other scenario.

What it can do

You interact with the assistant in a chat inside the Visual Builder.

Build scenarios. Describe the task: the assistant proposes a structure and places nodes on the canvas. Refine, edit, and add conditions right in the chat.

Understand the canvas. The assistant sees what is currently open on your canvas. It can explain how any node works, walk you through the full scenario logic, and answer questions about platform features in context of what you have in front of you.

Debug. Something went wrong: describe the problem. The assistant finds where it broke and suggests how to fix it.

Before you start

Make sure that:

• You have a Latenode account and access to the workspace where you want to build.
• You know what should trigger the scenario and what the result should be.
• You are ready to connect authorizations for the apps the scenario needs.

The assistant works inside your account. It cannot access services or credentials you have not set up.

How to work with it

1. Describe your goal - what triggers the scenario, what data is involved, and what the result should be.
2. Review the plan - the assistant shows a numbered proposal before it changes the canvas.
3. Monitor the build - after you approve, the assistant adds nodes, connects them, and configures settings.
4. Review and refine - verify authorizations, required inputs, and assumptions; ask the assistant to adjust as needed.

Use Clear to reset the chat when you switch to an unrelated task. Starting a fresh conversation helps the assistant stay focused and can reduce unnecessary token use.

Approve the proposed scenario

After the assistant thinks through your request, it shows a Scenario approval card with a step-by-step plan: which nodes to add, how to wire them, and what it still needs from you (for example an SMTP connection).

• Click Approve to let the agent start building on the canvas.
• Click Request changes to describe what to adjust before any nodes are added.

While the agent works, the canvas is locked and the banner AI agent is controlling the scenario appears. Use Stop to interrupt the build.

Track PnP token usage

Using the AI scenario helper consumes PnP tokens. Below each assistant message you see the cost for that step as a coin icon with a number.

Hover over the cost badge to open Token usage:

Longer conversations, larger scenarios, and repeated iterations increase the session cost.

Write effective prompts

Specific prompts produce better results with fewer back-and-forth messages.

Include:

• what should trigger the scenario,
• which apps or services to use,
• what data to read, send, or update,
• what should happen on success or failure.

Example prompts

Create a scenario

Every day at 9 AM collect AI news via Perplexity and email a short digest to me.
Use a schedule trigger.

Debug a failed run

The last run failed on the Gmail node.
Explain what went wrong and suggest a fix before changing anything.

Update an existing scenario

Add a Slack notification when the HTTP node returns an error,
then keep the rest of the scenario unchanged.

Review AI-generated changes

Before you turn a generated scenario on in production:

• Review the scenario logic on the canvas.
• Check node settings and authorizations.
• Run a test with Run Once and inspect the output in Execution History.
• Confirm error handling matches what you expect.

Credentials and secrets

Do not paste API keys, passwords, or tokens into the chat.

When a node needs an app connection, set it up through the standard authorization flow in the node settings or on Authorizations. The assistant can tell you which connection is missing, but secrets stay in the authorization screens.