files.com 1.1.682 → 1.1.683

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2c86cae5b00c3655207ca8a4425401eac36bcd0a92db0200cd34d546f490d2df
-  data.tar.gz: 9ba89c4e3380e60f347d418849583781c727212f3902b467ee04c05b9979f0f8
+  metadata.gz: 5ed47796e505dddf19405cf5eafb106a333029fbfce94d3b8303cb7ef375240a
+  data.tar.gz: e078917468a41070b39145b1fd483aa9bcb150686c82b92e8d0ee8ad8cb5094f
 SHA512:
-  metadata.gz: 54f1251d77ee97cc00f53e0d43df23e2801aa6807a160456967cfcf3df397f2b61faf72888c2b6cdab58852de95bcbc70e51cbd7a7542bc665ef5c2b7480a50f
-  data.tar.gz: 6dc7aba8222b3e55812567b362282e3ce3b93bf37ae4077bcef14f1911490288dceb0502df924f4118727ec490a1e2c0cc28cfa00fe5203ea68587243d63dc30
+  metadata.gz: 51ffcb02734ebd77e4fc43645e9283cd3281b66929d1c4d3b6533df0bd69b15c6e96ef27799223fb891503ee08dd3ff26c4f77e07cda330f2324a8431e465630
+  data.tar.gz: 0f655e22b02716d6971ceae493b562bc939f04660b9d347cf9337db7b240fdf2326284174c2bb273b4aaf12726373840a89999af34ae3b3ece2970b8c29cb452

data/_VERSION

@@ -1 +1 @@
-1.1.682
+1.1.683

data/docs/automation.md

@@ -32,6 +32,7 @@
       }
     }
   ],
+  "inbound_email_address": "example-automation-abc123@inbox.files.com",
   "flatten_destination_structure": true,
   "group_ids": [
     1,
@@ -112,6 +113,7 @@
 * `disabled` (boolean): If true, this automation will not run.
 * `exclude_pattern` (string): If set, this glob pattern will exclude files from the automation. Supports globs, except on remote mounts.
 * `import_urls` (array(object)): List of URLs to be imported and names to be used.
+* `inbound_email_address` (string): If trigger is `email`, this is the address that triggers the Automation.
 * `flatten_destination_structure` (boolean): Normally copy and move automations that use globs will implicitly preserve the source folder structure in the destination.  If this flag is `true`, the source folder structure will be flattened in the destination.  This is useful for copying or moving files from multiple folders into a single destination folder.
 * `group_ids` (array(int64)): IDs of Groups for the Automation (i.e. who to Request File from)
 * `ignore_locked_folders` (boolean): If true, the Lock Folders behavior will be disregarded for automated actions.
@@ -268,15 +270,18 @@ Files::Automation.create(
 
 ---
 
-## Manually Run Automation
+## Manually Run Automation. v2 Automations require Site or Workspace Admin permission
 
 ```
-Files::Automation.manual_run(id)
+Files::Automation.manual_run(id, 
+  items: [{"file":"incoming/report.csv"},{"data":{"customer":"Acme"}}]
+)
 ```
 
 ### Parameters
 
 * `id` (int64): Required - Automation ID.
+* `items` (array(object)): Initial items for a v2 manual trigger. Each item contains exactly one `file` path or `data` object.
 
 
 ---
@@ -374,17 +379,20 @@ Files::Automation.delete(id)
 
 ---
 
-## Manually Run Automation
+## Manually Run Automation. v2 Automations require Site or Workspace Admin permission
 
 ```
 automation = Files::Automation.find(id)
 
-automation.manual_run
+automation.manual_run(
+  items: [{"file":"incoming/report.csv"},{"data":{"customer":"Acme"}}]
+)
 ```
 
 ### Parameters
 
 * `id` (int64): Required - Automation ID.
+* `items` (array(object)): Initial items for a v2 manual trigger. Each item contains exactly one `file` path or `data` object.
 
 
 ---

data/docs/automation_authoring_schema.md

@@ -10,10 +10,12 @@
   ],
   "nodes": [
     "example"
-  ]
+  ],
+  "schema_url": "example"
 }
 ```
 
 * `definition_schema` (object): JSON Schema for active Automation v2 graph definitions.
 * `error_families` (array(object)): Typed error families accepted by Automation v2 on_error rules.
 * `nodes` (array(object)): Active Automation v2 node authoring metadata.
+* `schema_url` (string): Stable public URL for the Automation v2 graph definition JSON Schema.

data/docs/automation_execution_node.md

@@ -0,0 +1,39 @@
+# AutomationExecutionNode
+
+## Example AutomationExecutionNode Object
+
+```
+{
+  "node_id": "example",
+  "node_type": "example",
+  "status": "example",
+  "run_stage": "example",
+  "reused": true,
+  "successful_operations": 1,
+  "failed_operations": 1,
+  "started_at": "2000-01-01T01:00:00Z",
+  "completed_at": "2000-01-01T01:00:00Z",
+  "duration_ms": 1,
+  "inputs": [
+    "example"
+  ],
+  "outputs": "example",
+  "input_items": "example",
+  "output_items": "example"
+}
+```
+
+* `node_id` (string): Node ID from the pinned Automation definition.
+* `node_type` (string): Node type.
+* `status` (string): Node status.
+* `run_stage` (string): Current node execution stage.
+* `reused` (boolean): Whether this node reused persisted output from an earlier run.
+* `successful_operations` (int64): Count of successful operations in this node.
+* `failed_operations` (int64): Count of failed operations in this node.
+* `started_at` (date-time): When this node started.
+* `completed_at` (date-time): When this node completed.
+* `duration_ms` (int64): Node runtime in milliseconds.
+* `inputs` (array(object)): Ordered inbound edge references.
+* `outputs` (object): Output counts, item kinds, and typed-error summaries by outlet.
+* `input_items` (object): Materialized input items currently available, grouped by inlet.
+* `output_items` (object): Materialized output items grouped by outlet.