Skip to main content
This walkthrough creates a Component, validates it in the Sandbox, and exposes it as an HTTP Endpoint. You will finish with one versioned unit of logic and one callable interface rather than code hidden inside a route.

​
Before you start

You need permission to create Components and Endpoints in the target instance. Use Sandbox or a non-production environment for the first run. Keep any credential in Secrets; this example does not require one.
1

Create a component

Open Build → Components, create a JavaScript Component, and add one code element. Name it so its business purpose remains clear when it is later reused by a Job, Event, or Agent plugin.
2

Run it in the Sandbox

Open the debugger, provide an input object, and run the component.
Expect a result shaped like { "message": "Hello, RevoEngine!", "executionId": "…" }. Inspect the result, logs, execution ID, and timing before saving the version.
3

Create an endpoint

Open Build → Endpoints, select the Component, choose POST and a route such as /hello, then configure input validation and a bounded timeout. Activate the Endpoint only after the validation preview succeeds.
4

Call the endpoint

Use the endpoint URL shown by the platform. Authentication and the exact base URL depend on the endpoint policy configured for your instance.

​
Verify the result

Confirm all four conditions before treating the quickstart as complete:
  • the Endpoint returns 2xx for the valid request;
  • the JSON response contains the submitted name and an execution identifier;
  • the Component execution is visible in operational evidence;
  • an invalid request follows the configured validation contract instead of failing as an unstructured runtime error.
If the call returns 401 or 403, check the Endpoint authentication policy and caller identity. If it returns 404, verify the active route and environment. If it returns 5xx, use the returned execution identifier to inspect logs and trace evidence rather than retrying blindly.

​
Continue with your preferred workflow

Stay in the Web IDE

Edit components with runtime-aware types, library navigation, and integrated debugging.

Use the CLI

Pull components into a local workspace, review drift, debug, and push changes safely.

Use custom Node.js

Build a hosted component with an injected Revo runtime and npm dependencies.

Integrate with the SDK

Call RevoEngine from a standalone Node.js service or from hosted custom code.
Last modified on September 23, 2026