--- title: "Seliom Integration" description: "Seliom is no-code business process automation from Spain: design a process template once, then run cases through it. Agents start cases, read and advance them, and pull case data so a process that lives in Seliom can be driven from anywhere." url: https://flowrunner.ai/integrations/seliom date_modified: 2026-09-04T14:52:04-07:00 --- # Seliom [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Seliom is no-code business process automation from Spain: design a process template once, then run cases through it. Agents start cases, read and advance them, and pull case data so a process that lives in Seliom can be driven from anywhere. 17 actions · API key · available [Seliom website](https://seliom.com/) · [Platform Documentation](https://docs.seliom.com/api/introduction) · Capability data verified 2026-08-18 1. A signed supplier agreement arrives in the shared mailbox 2. List Launchable Templates confirms the supplier onboarding template can actually be started through the API 3. Get Start Definition returns the submission elements the template's start node requires 4. Create Case opens one run of the process with the label and required elements filled in 5. Upload File puts the signed agreement into the case's document repository 6. The process owner is told a case is open and which elements the agent supplied 7. The owner reviews the opened case and decides whether it proceeds or pauses for a missing approval ## What This Integration Enables Seliom is built for teams that treat a business process as a design rather than a habit. A process template is authored once, and every run of it is a case. That separation is what makes the process automatable from outside: a case is a named object with a state, a document repository and a defined set of submission elements, so a FlowRunner agent can open one, advance it, read it and close it without anybody opening the Seliom interface. The connector follows Seliom's own model rather than flattening it. Agents discover which templates are genuinely startable through the API with List Launchable Templates, read the start node's requirements with Get Start Definition before writing anything, then open the case with Create Case. Pause, stop and resume arrive as one Set Case State operation with a three-way choice, because that is what they are in Seliom. Where a process needs a person, the human step stays a step in the process, and FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline covers the calls the agent makes about the case itself. ### Without FlowRunner **Process lives in two places**: The design sits in Seliom and the starting conditions sit in an inbox nobody audits **Cases opened by hand**: Someone retypes the same submission elements into the same start form for every run **Idle looks like abandoned**: A paused case and a forgotten case are indistinguishable in a listing ### With FlowRunner **Cases start from the event**: The system that produced the trigger opens the case, with its required elements already resolved **Documents land with the run**: The source file is attached to the case it belongs to, not filed separately **Idle cases get a verdict**: A sweep gathers the evidence for each stalled case and a person says which are genuinely finished ## Use Case Scenarios ### The case opens itself, correctly, the first time A contract comes back signed from [DocuSign](https://flowrunner.ai/integrations/docusign) or a purchase order is approved in the ERP. The agent calls List Launchable Templates so it never tries to start a template the API will refuse, then Get Start Definition to learn exactly which submission elements the start node wants. Where an element expects team members, List Definition Element Members supplies the valid identifiers rather than a guessed name. Create Case opens the run, Upload File attaches the signed document, and a summary posts to [Slack](https://flowrunner.ai/integrations/slack) naming the case and the elements the agent filled in. Nobody retyped a start form, and no case failed validation because a required element was missing. ### A running process reports on itself On a schedule, the agent calls List Cases filtered to the states that matter, then Get Case for each one to read where it stands. The results append to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and a digest lands with the operations lead: how many cases are running, which templates they came from, and how long each has been in its current state. Because List Process Templates, List Launchable Templates and List Automated Templates answer three genuinely different questions, the digest can separate "designed" from "startable" from "automated" instead of blurring them into one count. ### The stalled case review Seliom lets a case be paused or stopped, and both leave it sitting still. A monthly sweep pulls every case that has not moved, gathers the evidence for each one with Get Case and List Case Documents, and assembles a comparison: which template it came from, what state it is in, which documents it holds, and when it last moved. The process owner reads that list and marks each case as resume, leave, or close. Only then does the agent call Set Case State or Delete Case. The gathering is the agent's work. The verdict is not. ## Human-in-Loop Highlight Delete Case is permanent, and a Seliom case is not just a status row: it carries the whole record of one run of a process, including the documents uploaded into it. The dangerous part is that a stalled case and a deliberately paused case look identical in a listing, so a cleanup sweep built on age alone will destroy work somebody is still waiting on. So the sweep never decides. It posts to the process owner: "Case FR-2291, template Supplier Onboarding, stopped 41 days ago, holds 3 documents, last state change by A. Ruiz. Resume, leave, or close it for good?" The owner answers, and only a close answer reaches Delete Case. The agent found every stalled case in the account in one pass. What it did not do was mistake silence for completion. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 17 actions ### Connection 1 - **Who Am I** Returns the account the API token and organization identifier resolve to. The cheapest way for a flow to confirm a connection works before it starts writing. ### Cases 6 - **List Cases** Lists cases with cursor paging, filtered by status, template or creation date. This is the read behind every reporting sweep and the polling read for flows that need to notice new runs. - **Get Case** Returns one case with its current state and details. Used to gather full context before a decision or an advance. - **Create Case** Opens one run of a process template. Read Get Start Definition first, because the start node decides which submission elements the new case must carry. - **Set Case State** Pauses, stops or resumes a case. Seliom exposes these as three separate routes; the connector gathers them into one operation with a three-way choice. Resume brings back a case that was either paused or stopped. - **Delete Case** Permanently deletes a case. The operation this page's human gate exists for. - **List Case Documents** Lists the documents held in a case's repository. Used to show a reviewer what a case actually contains before anybody decides its fate. ### Process Templates 8 - **List Process Templates** Lists every template the account can see. The inventory read, not the startable read. - **List Launchable Templates** Lists only the templates that can be started through the API, which is exactly what Create Case will accept. A flow that picks from this list cannot choose a template the next call refuses. - **List Automated Templates** Lists the templates that have been automated. Requires the edit-processes permission in Seliom. - **Get Process Template** Returns one template's definition. Used to check what a process is designed to do before launching cases against it. - **Rename Process Template** Renames a template. The label change everyone in the account sees. - **Delete Process Template** Permanently deletes a template. Seliom routes the delete through a different path family than the read, and the connector sends the one that actually removes it. - **Get Start Definition** Returns the submission elements a template's start node requires. There is no other way to learn them, which makes this the mandatory read before Create Case. - **List Definition Element Members** Returns the valid identifiers for a team members element on a start definition. Used so a case is opened naming real people rather than free text. ### Files 2 - **Upload File** Uploads a document into a case. Seliom takes uploads as a JSON body rather than a multipart form, and the connector builds that shape from either a URL or inline content. - **Download Case Document** Retrieves a document held in a case. Used to hand a file to the next system in a flow, or to a reviewer who needs to see it before deciding. ## Frequently Asked Questions ### What can FlowRunner do with Seliom? FlowRunner agents can run Who Am I, List Cases, and Get Case in Seliom, plus 14 more actions. ### Does connecting Seliom to FlowRunner require OAuth? No. Seliom connects to FlowRunner with an API key, no OAuth flow required. ### Can Seliom trigger a FlowRunner workflow automatically? Seliom doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Seliom?** This integration exposes Seliom to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/seliom. Site index: https://flowrunner.ai/llms.txt