procesio

Create, edit, and run PROCESIO processes, forms, documents, credentials, and webhooks via its REST API.

4|2|Updated Sep 1, 2026
One-click install
npx skills add https://github.com/Procesio-Externals/procesio-cli --skill procesio-procesio-externals
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: procesio
Source: https://github.com/Procesio-Externals/procesio-cli/tree/main/tools/procesio
Command: npx skills add https://github.com/Procesio-Externals/procesio-cli --skill procesio-procesio-externals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Building PROCESIO automation resources by hand through the designer is slow and error-prone, and the platform's REST API has undocumented DTO shapes, validation rules, and behavioral quirks that make naive API scripting fail silently. This Skill provides curated actions and deterministic DTO builders that construct valid processes, data models, forms, documents, credentials, and webhooks from minimal JSON configs, validated against PROCESIO's own endpoints before anything is committed. ## Core Features & Use Cases - Deterministic DTO builders: Each component (datatype, process, credential, document, webhook, form) has a JSON Schema, a golden DTO template, and a pure builder function, exposed as <component>-create / <component>-edit actions with --dry-run preview against PROCESIO's validate endpoints. - Full process lifecycle: Run processes (including file-input uploads), poll instance status, download generated files, duplicate/validate/delete flows, auto-layout canvases, and manage schedules and custom action packages. - Documented API corrections: A maintained register of places where the official API reference is wrong (e.g., instance variables returned under defaultValue, the form launch route's instance segment, canonical export fingerprinting), so builds don't repeat known failures. - Use Case: Ask the agent to build a webhook-triggered process that calls an external API, generates a branded PDF from a document template, and emails it via a SendGrid SMTP credential — all resources created, validated, and run live in a workspace from a single declarative config. ## Quick Start Ask the agent to list the available PROCESIO actions and then create a simple process in your workspace using a JSON config with dry-run enabled.

Frequently Asked Questions about procesio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PROCESIO process programmatically?▼

Use the process-create action with a minimal JSON config naming actions, variables, and edges. The builder merges the config onto a golden DTO template, validates it against PROCESIO's /api/Projects/validate endpoint, and supports --dry-run to preview the DTO before sending.

How do I run a PROCESIO process with a file input via the API?▼

Use the three-step sequence: publish an instance with file metadata, upload the bytes to /api/File/upload/flow with ids in headers, then launch the instance. Poll /api/Projects/instances/{id}/status with the flowTemplateId query parameter until status 50.

Why does my PROCESIO process show empty parameters in the designer but run fine?▼

PROCESIO stores parameter values in two places: runtime Parameters[] and the designer's CustomData.configuration tree. The builder mirrors values into both, including bespoke shapes for document-mapper and decisional-case properties, so the designer validates what the runtime executes.

Can a Javascript action output a typed list in PROCESIO?▼

No. The Javascript action wraps output as {result: v} and PROCESIO does not map a plain JS object onto a typed model's attributes. Use a Call API action bound to a model-typed Response Body, or build HTML in a script and render it through a shell document template.

Why does reading flow instance variables return None for every output?▼

The variables endpoint returns definitions, not values: the runtime value is in the defaultValue field, and there is no value key. Flatten results to {name: defaultValue} at the boundary to avoid misreading successful runs as empty.

What are the limitations of PROCESIO form automation with headless browsers?▼

Headless Playwright fill/press events do not update the Angular-bound form model, so field values stay empty in automation. Verify form value-flow in a real browser, and use RUN_PROCESS triggers with server-side inputMap/outputMap rather than in-form JavaScript to move field values.