Skip to content

Core concepts / 5 minute guide

Flows, Apps, and capabilities

Understand the definition, runnable application, and callable function behind an Elyxis outcome.

Last verified 2026-10-19

Start with the function you need

A capability is a callable function with an input and output contract. For example: accept ticket text, then return an urgency level and a short explanation as JSON.

A Flow describes the processing steps and their connections. An App is the application that can run that work with its resolved configuration. These resources are related, but creating a definition is not the same as executing it.

From definition to execution

Flow: what the steps do and how data moves
  → Draft App: prepare the application and its configuration
  → App: build and run the application
  → Capability call: send input and receive a result

Elyxis calls the process of resolving and preparing the executable result materialization. It can reuse compatible resources instead of creating another copy for every request.

Plugins provide the building blocks. Settings and Keystores supply the Environment configuration those blocks need.

Ask to create, then ask to run

Specify the input and output when asking for a new capability:

Create a capability that accepts support-ticket text and returns JSON with urgency and reason.

After reviewing the result and completing any remaining setup, ask for a run with sample input:

Run that capability with this ticket: "All customers are unable to complete a payment."

The Assistant may need clarification, configuration, approval, or additional runtime preparation. Use the returned resource name or ID to identify the capability when there are several candidates.

Read the result accurately

ResultWhat to check next
Flow or Draft App createdIs configuration complete, and has an executable App been prepared?
App builtHas it started and become ready?
App runningDid the requested capability actually execute?
Capability executedDoes the returned output satisfy the expected contract?

A running App alone is not proof that your request succeeded. Look for the invocation result, relevant output, and any reported failure or missing prerequisite.

Reuse work

Your request defines the task and its parameters. Once created, the capability can perform the same task with different parameter values, producing results based on each request. The task remains the same; reusing it does not require the same parameter values or produce a fixed result.

Refer to the existing capability or App by its returned name or ID when you want to use it again. Check the Environment and current readiness rather than asking to create a duplicate. Permissions to inspect, build, start, and execute can differ.

Learn to work with the Assistant