Workflows
Visual processing pipelines
Chain CAD, GIS, point-cloud, mesh, PDF and image operations into one pipeline: trigger, input, operation, logic and output. Build once, then run on demand, on a schedule or from a webhook — with retries, human approval and a live timeline.
- 40+ server operations
- Retries with backoff
- Human approval gate
- Schedule & webhook triggers
- Live run timeline
My workflows
No workflows yet. Add nodes and click Save.
Templates
Run inputs (my files)
No files yet. Upload files first.
Building blocks
Five node families, with 50 server-executable operations across 10 PDF · 2 Image · 8 CAD 2D · 20 GIS / raster / terrain · 5 Point cloud · 4 3D mesh · 1 pcb-eda.
Triggers
- Manual run
- Webhook
- Schedule (cron)
Inputs
- Upload files
- Import a ZIP
- Previous cloud files
Operations
- PDF merge / split / compress / OCR
- DXF → SVG / PDF / PNG
- Raster reproject / terrain
- Point-cloud filter
- Mesh repair / simplify
Logic
- Filter
- Merge inputs
- Conditional branch
- Fan out per file
- Manual approval
- Sub-workflow
Outputs
- Download
- Package ZIP
- Rename by template
- Archive to R2
How it works
- 1
Start from a template or blank
Open a ready template — PDF archive cleanup, DXF → SVG in batch, image convert + rename, and more.
- 2
Wire the graph
Drop nodes on the canvas (trigger, input, operation, logic, output) and connect them; parameters are configured per node.
- 3
Validate and run
Validation reports missing inputs, unreachable nodes and type mismatches before you spend a run.
- 4
Watch the timeline
Follow each step live, approve human-in-the-loop gates, then download or archive the outputs.
Why build it here
Compared with generic automation platforms.
| Aspect | Vecaria | Generic automation |
|---|---|---|
| Native CAD/GIS operations | 40+ file operations built in | Generic app connectors |
| Human-in-the-loop | Approval node with timeout | Paid add-on / external tool |
| Durable execution | Step memoization, retries, long waits | Varies by platform |
| Pricing | Subscription, no per-task meter | Per task / per credit |
| Developer access | API, SDK, CLI and MCP | Often a paid tier |
Use cases
Supplier STEP → STL, packaged in batch
Explore →Drawing set merge → compress → archive
Explore →Shapefile → GeoJSON → PMTiles
Explore →SVG/DXF batch → G-code → ZIP
Explore →Gerber → PNG for pre-fab review
Explore →Contracts merge → paginate → R2 archive
Explore →Mesh repair → scale → package
Explore →Iteration batch with approval gate
Explore →Plan limits
Values follow the live configuration.
| Limit | Free | Pro |
|---|---|---|
| Saved workflows | 1 | 10 |
| Runs per month | 20 | 500 |
| Steps per run | 200 | 200 |
| Concurrent runs | 5 | 5 |
| Step timeout | 300s | 300s |
| Retries per step | 2 | 2 |
Frequently asked
What is a workflow here?
A visual pipeline of trigger, input, operation, logic and output nodes. Build it once, run it on demand, on a schedule or from a webhook.
Are my files uploaded?
Workflows run server-side, so input files are uploaded over TLS and deleted on expiry. Browser-only local tools are not workflow nodes — use the batch page for local-only processing.
Which operations can I chain?
40+ server operations: PDF merge/split/compress/OCR/redact/encrypt, image convert/compress, DXF conversions, raster reproject and terrain analysis, point-cloud filtering, mesh repair and simplify, plus file logic like filter, merge, branch and fan-out.
Can a run wait for a human?
Yes. The approval node pauses the run until someone approves or rejects it, then continues — useful before publishing or writing to storage.
How do retries work?
Each step is retried automatically with backoff, and the timeline shows every attempt so a failure is visible and resumable.
Automate the repetitive file work
Browsing is open to everyone; sign in to save and run. Pro raises workflows, runs and concurrency.