I/O & Files
These operators move bytes — files, objects, streams — and speak the wire protocols a flow needs to reach the outside world.
Files & storage
Section titled “Files & storage”| Operator | invoke: | What it does |
|---|---|---|
| Filesystem | filesystem.* | Read, write, move, list local files. |
| SFTP | sftp.* | List, get, put, move, delete over SFTP. Write actions carry compensating deletes. |
| SSH | ssh.* | Run remote commands over SSH. |
| S3 | s3.* | Object get/put/list/delete on AWS S3 or S3-compatible stores. |
| Dropbox | dropbox.* | File operations against Dropbox. |
| Archive | archive.* | Create/extract zip, tar.gz; bundle multiple inputs. |
| Binary Decoder | binary-decoder.* | Decode binary payloads into structured data. |
| Kinesis | kinesis.* | Put/get records on AWS Kinesis streams. |
using: - zenvara/sftp
steps: - $upload: create: sftp.file on: drop with: Path: "/incidents/${= str(_invocation-id)}.json" Input: "${rows.body}"Output field names are descriptive — path, content, files, etc. For a presigned-URL handoff, a flow can return: a redirect:.
Protocol layer — connect to anything
Section titled “Protocol layer — connect to anything”| Operator | invoke: | What it does |
|---|---|---|
| HTTP | http.* | get, post, put, delete, … Generic HTTP with multiple auth modes; auto-discovers OpenAPI specs. |
| REST | rest.* | Higher-level REST client over the HTTP core. |
| GraphQL | graphql.* | Typed GraphQL queries and mutations. |
| SOAP / WSDL SOAP | soap.* | SOAP requests; consumes a WSDL to type the operations. |
- $weather: invoke: http.get with: Url: "https://api.example.com/weather?city=${city}"Output: body (parsed where possible), statusCode, headers. Reference as ${weather.body.temp}.
The HTTP operator is the universal escape hatch: when no dedicated operator exists for a service, point http.* at its OpenAPI spec and you have a typed client. The SOAP operator does the same for legacy WSDL services. This is why the catalog stays focused rather than shipping hundreds of bespoke connectors.
Auth modes
Section titled “Auth modes”The HTTP/REST operators support multiple authentication modes — bearer token, basic, API key header, OAuth client-credentials — configured on the connection and backed by secrets, so the flow never carries a credential.