Vision

00Overview

Read the contents of images and documents straight from a flow — pull classification labels and detected objects out of a photo, run OCR to recover printed text, and extract tables, key-value pairs and a document type from a scanned form or PDF. Manage the Vision projects that hold your custom models, creating, renaming, moving and listing them, and look up the trained models themselves by name, project or OCID. Everything runs against your own Oracle Cloud tenancy, in the region you connect.

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Vision

1. In each Vision node the Authentication dropdown offers two ways to sign in: Connect Oracle Cloud (recommended — a managed connection) and API signing key (advanced) (paste your own signing key). Set up whichever you prefer once, then reuse it on every action.
2. Connect Oracle Cloud (recommended): in Flomation, open your environment's Connections and add an Oracle Cloud (API key) connection — give it a name, your Tenancy OCID and a Region (e.g. uk-london-1), then choose Create. Flomation generates the signing key pair for you, so no private key is ever pasted by hand.
3. Still in the wizard, click Deploy to Oracle Cloud to open a stack in your OCI Console, pick the compartment to grant access to and apply it — this sets up the access Flomation needs. Copy the User OCID from the stack outputs back into the wizard, choose Connect, then Test until it confirms (a brand-new key can take a minute or two to activate).
4. API signing key (advanced): to supply your own key instead, in the OCI Console open your user's profile → API Keys → Add API Key, upload or download a key pair, and copy the Tenancy OCID, User OCID, Region and Key Fingerprint from the configuration preview OCI shows after the key is added.
5. Store the Private Key (PEM) as a Flomation environment secret (e.g. vision_secret) — the full PEM including the BEGIN/END lines — and pick it in the node's Private Key (PEM) field; fill Private Key Passphrase only if your key is encrypted.
6. Whichever method you use, set the Compartment OCID on each node to the compartment your Vision projects, models and analysis calls should run in — it is required on every action.

02Analyze

OCI Vision: Analyze Document

oracle/vision/analyze_document · Action

Run OCI Vision Document AI over a base64 document (image or PDF) to extract text, tables and key-value pairs, or classify the document type.

Returns: tool_result, result, success, error

OCI Vision: Analyze Image

oracle/vision/analyze_image · Action

Analyze a base64-encoded image with OCI Vision — request any mix of classification labels, object detection and text (OCR) detection, and get the labels, objects and recognised text back.

Returns: tool_result, result, success, error

03Model

OCI Vision: Get Model

oracle/vision/model_get · Action

Fetch a single OCI Vision custom model by its OCID — its type, version, project and lifecycle state.

Returns: tool_result, model, id, lifecycle_state, success, error

OCI Vision: List Models

oracle/vision/model_list · Action

List the custom Vision models in a compartment. Optionally filter by project, exact display name, or lifecycle state. Walks pagination up to a safe cap.

Returns: tool_result, models, count, truncated, success, error

04Project

OCI Vision: Change Project Compartment

oracle/vision/project_change_compartment · Action

Move a Vision project into a different compartment — the project keeps its OCID, only its compartment placement changes.

Returns: tool_result, id, destination_compartment_id, success, error

OCI Vision: Create Project

oracle/vision/project_create · Action

Create a Vision project — the container for your custom image/document models. Returns the project in a CREATING state plus a work-request id; poll Get Project until ACTIVE.

Returns: tool_result, project, id, lifecycle_state, work_request_id, success, error

OCI Vision: Delete Project

oracle/vision/project_delete · Action

Delete a custom Vision project by its OCID — returns a work-request to track the async delete.

Returns: tool_result, id, work_request_id, success, error

OCI Vision: Get Project

oracle/vision/project_get · Action

Fetch a single Vision project by its OCID — its display name, description, compartment and lifecycle state.

Returns: tool_result, project, id, lifecycle_state, success, error

OCI Vision: List Projects

oracle/vision/project_list · Action

List the custom Vision projects in a compartment. Optionally filter by exact display name or lifecycle state, and cap the number returned. Walks pagination up to a safe limit.

Returns: tool_result, projects, count, truncated, success, error

OCI Vision: Update Project

oracle/vision/project_update · Action

Partially update a Vision project — change only the display name or description you supply; blank fields are left unchanged. Asynchronous: returns a work-request id you can poll for completion.

Returns: tool_result, id, work_request_id, success, error

05Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

• Both the image and document analysis actions take their content inline as base64, so they suit single images and smaller documents better than very large multi-page files.
• Every action requires a Compartment OCID, because Oracle Cloud authorizes and bills each request against the compartment you name.
• You can look up and list custom Vision models here but not create or train them, so a custom model has to be built elsewhere in Oracle Cloud before it will show up in Get Model or List Models.
• OCI Vision is a regional service, so the region you connect in is where analysis runs and the only place its projects and models are visible — anything created in another region will not appear here.
• List Projects and List Models walk through results only up to a fixed number of pages, so in a very large compartment the returned list can be incomplete — watch the truncated flag when that matters.
• A newly connected Oracle Cloud account may need a minute or two before its first call succeeds, while the new signing key becomes active across Oracle Cloud.