Consistent resources
Workflow, run and event resources share conventions.
Explore →Trigger, observe and govern coherent workflows with technically consistent examples and no external dependency.
const run = await nexora.workflows.trigger({
workflow: "lead-enrichment",
input: { email: "ava@example.test" }
});run = nexora.workflows.trigger(
workflow="lead-enrichment"
)curl -X POST https://api.example.test/v1/workflows/runThe code is fictional, harmless and designed for template demonstration.
const run = await nexora.workflows.trigger({
workflow: "lead-enrichment",
input: { email: "ava@example.test" }
});run = nexora.workflows.trigger(
workflow="lead-enrichment"
)curl -X POST https://api.example.test/v1/workflows/runCopy controls work locally where clipboard permissions allow.
{
"id": "run_demo_4821",
"status": "queued",
"workflow": "lead-enrichment",
"created_at": "2026-07-11T12:00:00Z"
}Precise examples, compact navigation and explicit states.
Architecture labels are placeholders, not claims about deployed infrastructure.
Validate identity, shape and rate policy.
Evaluate deterministic steps and retries.
Preserve run state for observation.
Return status and dispatch approved events.
Replace with measured values from the real platform.
Fictional SDK cards do not imply published packages.
Search, sidebars, code copy and related content are included.
const run = await nexora.workflows.trigger({
workflow: "lead-enrichment",
input: { email: "ava@example.test" }
});run = nexora.workflows.trigger(
workflow="lead-enrichment"
)curl -X POST https://api.example.test/v1/workflows/runThe static status page is not connected to monitoring infrastructure.
“The examples were compact enough to evaluate quickly and complete enough to understand the response model.”
No metering or checkout backend is included.
Fictional placeholder prices.
Adapt limits and behavior to the actual API.
No. All account, pricing, dashboard and form behavior is a frontend demonstration.
Yes. Central settings and CSS custom properties are documented.
No. Certification and SLA references are clearly marked placeholders.
Yes. Core pages work after opening the HTML files directly.
Use the documentation and request form to demonstrate the complete evaluation path.