Latenode

Expose external workflows over a Latenode MCP webhook

This template is an HTTP front door for workflows that already live in another engine. A webhook receives list, add, remove, or execute.

JavaScript calls that engine's REST API and keeps a small registry of workflow ids. The webhook response returns JSON. Put the engine base URL and API key in the JavaScript node.

Updated Sep 16, 2026Est. run: 35sEst. cost: $0.0022
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Lets agents list and run external workflows through one Latenode URL
  • Calls the engine REST API from JavaScript with the key in that node
  • Stores the workflow registry in Redis over HTTP or Latenode key-value
  • Returns JSON from the webhook response

How it works

1
Trigger

Receive the request

A webhook accepts operation, workflow ids, and parameters from the client.

2
Logic

Route the operation

A router sends list, add, remove, or execute down separate paths.

3
Logic

Call the engine and persist ids

Use a JavaScript node to call the external workflow engine REST API with the base URL and API key stored in that node, then read and write the tool registry (Redis over HTTP, or Latenode key-value storage).

4
Action

Respond

The webhook response returns JSON (tools list, execute result, or error).

Setup guide

1

Add the webhook

Add a webhook trigger and a webhook response. This URL is what MCP clients or scripts will call.

2

Store engine credentials in JavaScript

Put the workflow engine base URL and API key in the JavaScript node (Latenode Secrets) and call its REST API for list and execute.

3

Choose a registry

Persist ids in JavaScript via Redis REST, or use Latenode key-value storage if you prefer not to run Redis.

4

Route operations

Add a router for list, add, remove, and execute. Send each branch into JavaScript, then return JSON with a webhook response.

Requirements

A workflow engine base URL and API key stored in the JavaScript node
A place to persist the tool registry (Redis HTTP or Latenode key-value)
Callers that POST JSON operations to the Latenode webhook

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.