List Appmixer flows of the authenticated user, sorted by last modification. Returns flow IDs, names, stages and modification times. Use pattern to filter by name.

Get a single Appmixer flow by ID: metadata and, optionally, the full flow descriptor (the JSON definition of components and their wiring). Set include_descriptor=true when you need component IDs, e.g. for trigger_component.

Get the current stage of an Appmixer flow: "running" or "stopped".

Get execution logs of an Appmixer flow. Optionally filter with an Apache Lucene query over fields such as "msg", "@timestamp", "portType", "port", "correlationId", "senderType", "senderId" and "inputMessages".

List messages that failed processing and were parked instead of being dropped. This is where a component sends its failures under the default error handling ("Stop execution" / onError: storeUnprocessed) — the flow keeps running and the failed message waits here. Use it to find out what broke and, after the flow is fixed, replay it with retry_unprocessed_message.

Read one parked message in full: err (message, code, name, stack) and messages, the input the component received keyed by inPort — together they usually explain why it failed.

Replay a parked message through its component. Fix the flow first — a replay repeats the original input, so an unfixed cause fails again.

Discard a parked message without replaying it. This cannot be undone.

Start an Appmixer flow by ID. The flow must be valid and complete to start.

Stop a running Appmixer flow by ID.

Permanently delete an Appmixer flow by ID. This cannot be undone.

Send a webhook request that submits data to a trigger component of a running flow, using POST (default), PUT, PATCH or DELETE — match the method the flow's webhook trigger expects. Find the component ID with get_flow (include_descriptor=false lists components with their IDs). For triggers that expect GET, use read_component_trigger.

Send a GET request to a trigger component of a running flow, for webhook triggers that listen on GET, and return the component's response.

Send a named App Event to Appmixer. All running flows of this user that contain an OnAppEvent trigger for this event name will receive it.

Get the complete guide to writing Appmixer flow descriptor JSON: structure, wiring (source), input mapping (config.transform, modifiers, variables), error handling and common validation failures. Read this before calling create_flow or update_flow.

List apps (connectors) available on this Appmixer tenant, e.g. "appmixer.utils", "appmixer.slack". Use get_components to inspect an app's components.

Inspect components of an Appmixer app. Without component, returns a compact summary of all the app's components (type, description, port names). With component (the full type, e.g. "appmixer.utils.email.SendEmail"), returns the full manifest including input fields, required fields and output variables — needed to build config.transform correctly. Never guess component types, port names or fields.

List third-party accounts (Slack, Google, …) connected by the authenticated Appmixer user. Components of connected apps need an account; accounts are connected by the user in the Appmixer UI, not through this server.

Create a new Appmixer flow from a flow descriptor JSON and validate it. Read get_flow_authoring_guide first and discover exact component types, ports and fields with get_components. Component keys may be readable placeholders ("trigger", "send_email") — real UUIDs are minted for them and every reference is rewritten, so you never need to generate IDs yourself; the mapping comes back as componentIds. The flow is created stopped; fix any validation errors with update_flow, then use start_flow.

Update an existing Appmixer flow (descriptor and/or name) and re-validate it. Send the COMPLETE flow descriptor — it replaces the stored one, so start from the current descriptor (get_flow with include_descriptor=true), keep the existing component IDs and the configuration of everything you were not asked to change. A running flow is rejected unless force is set.

Get the output variables available to each component of a flow — the exact "$..." paths (with schemas) usable in config.transform modifiers. Call this after create_flow/update_flow to fix or build variable references instead of guessing paths.

Test-run a single component (and its downstream graph) of a flow without starting the flow. Provide the input data the component should receive; returns the outputs each component produced. The flow does not need to be running. Use this to verify a flow works before start_flow.

Resolve a field's dynamic options at runtime — the values behind inspector fields and output ports whose manifest declares a source URL (Slack channel pickers, spreadsheet lists, generated output variables). Take component_type and out_port from that source URL (it often points at a different, auxiliary component), and pass the component that owns the field as component_id — it must already exist in a flow and, for connected services, have an account assigned, because the lookup runs with that component's credentials. Results are the auxiliary component's raw output: sources that declare a transform are not converted here, so pick the identifier the target field expects (Slack channels: id). Pointer strings in source.data such as "properties/event" mean "send that property's value".

Get the public webhook URL of a trigger component (e.g. WebhookTrigger) in one of your flows. Use it to chain flows: another flow POSTs to this URL via appmixer.utils.http.Post — no credentials needed, the endpoint is public. The flow must be running for the webhook to actually accept requests.

List which components of a flow require a connected third-party account and which account (if any) is assigned to them.

Assign a connected third-party account (see list_accounts) to a component of a flow, so the component can authenticate against its service. The account must belong to the authenticated user and match the component's service.

Validate an Appmixer flow server-side. Returns per-component errors (wrong port names, missing required fields, invalid variables). A flow must be valid to start.

List the user's Appmixer data stores. Flows read and write these through the appmixer.utils.storage components, which need the store's ID — look it up here rather than guessing it.

Create a data store the flows of this user can read and write.

Read records of a data store: their keys, values and timestamps. Use it to see what a flow has stored, or to check the data a flow is about to read.

Create or overwrite one record of a data store. value is stored as it is, so wrap a scalar in an object, e.g. {"value": "text"}. Useful for seeding data a flow will read, or correcting a record a flow wrote.

Delete one record from a data store. This cannot be undone.

List saved versions of a flow, newest first. Versions are snapshots the flow can be rolled back to.

Snapshot the current state of a flow so it can be restored later. Take one before rewriting a flow you did not build — update_flow replaces the descriptor and there is no undo otherwise.

Roll a flow back to a saved version. The flow's current descriptor is replaced by the snapshot, so take a version of the current state first if you may want it back.

Copy a flow, including its components and wiring. The copy is created stopped and its components have no accounts assigned unless connect_accounts is set. Cloning then editing the copy is the safe way to change a flow that is in use.

List the modifier functions available on this tenant — the g_* functions usable in a transform's functions array (g_length, g_jsonPath, g_formatDate …). Check here instead of assuming a function exists.