Run a single action
After you connect the Latenode MCP Server to your agent, you can run any action from the platform catalog and get the result back in chat immediately. No scenario is created: nothing appears on the canvas or in the Scenarios list.
Client setup: MCP Server.
How it works
Describe the action you want, and the agent runs it once:
- The agent finds the action in the catalog and fills in its fields.
- If the action needs an authorization, it reuses a saved one or asks you to create one.
- The action runs and the result comes back in the same chat.
A successful run appears in statistics. The Scenarios list stays unchanged.
In this mode the agent works through these MCP tools:
| Tool | What it does |
|---|---|
search_node_types | Finds the action in the catalog |
get_dynamic_node_parameters | Loads fields that appear after the first values are set |
search_connections, create_connection | Reuses an authorization or starts a new one |
run_action_node_once | Runs the action and returns the result |
Parameters and responses: MCP Tools Reference.
Authorizations
Actions that reach an app need an authorization, the same ones you use in the builder.
The agent tries your existing authorizations for that app, newest first. If none of them work, it sends a link to create one: finish it in the browser, then ask the agent again. Until the authorization is ready, the action will keep failing.
Example prompts
One prompt describes one action:
Send “Deploy is live” to the #ops channel in Slack.Create a Google Calendar event tomorrow at 15:00 titled “Sync with design”.Add a row to the Leads sheet: name Anna, email [email protected].Ask for several things at once and the agent runs several actions, one call each.
Limits
- A run is cancelled after 100 seconds.
- Missing required fields stop the call before the action runs.
- Statistics update after a successful run.
Related pages
MCP Tools Reference
Full reference for all tools exposed by the Latenode MCP Server.
Working with the built-in database
Built-in database: structured data in storages and collections; basics of the database and scenario nodes.
Need Help? Ask the community
If something on this page is missing or unclear, post on the Latenode community forum. Our team and other users usually reply quickly.