@uipath/skills 1.195.0

package/skills/uipath-maestro-bpmn/.maintenance/check-validation-fixtures.sh

@@ -0,0 +1,8 @@
+#!/bin/bash
+# Validate the synthetic BPMN/package fixture corpus for this skill.
+# Usage: bash .maintenance/check-validation-fixtures.sh
+
+ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+cd "$ROOT" || exit 1
+
+python3 .maintenance/check-validation-fixtures.py

package/skills/uipath-maestro-bpmn/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: uipath-maestro-bpmn
+description: "Always invoke for `.bpmn`, `project.uiproj`, `entry-points.json`, `operate.json`, `bindings_v2.json`, or `package-descriptor.json` files. UiPath Maestro BPMN / Process Orchestration — author, inspect, validate, package, operate, diagnose. Model writes BPMN skeleton + non-IS UiPath XML; CLI owns Integration Service nodes/templates and generated package files. For .flow JSON→uipath-maestro-flow. For XAML/coded workflows→uipath-rpa. For Python agents→uipath-agents. For Case plans→uipath-maestro-case."
+allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion
+---
+
+# UiPath Maestro BPMN Skill
+
+Guide for authoring, inspecting, validating, packaging, operating, and diagnosing UiPath Maestro BPMN Process Orchestration projects. BPMN XML is the source of record. Generated JSON package files and Integration Service details are owned by CLI tooling.
+
+## When to use this skill
+
+**Author** - creating or editing local BPMN project source. Read [references/author/CAPABILITY.md](references/author/CAPABILITY.md).
+
+- Create a Maestro BPMN project skeleton
+- Edit `.bpmn` XML for process structure, variables, mappings, timers, messages, gateways, subprocesses, script tasks, and documented non-Integration-Service UiPath extensions
+- Plan where Integration Service activities/triggers require CLI enrichment instead of model-authored XML
+- Validate XML, diagrams, entry points, bindings, and generated package metadata locally
+
+**Operate** - packaging, uploading, publishing, running, or managing cloud lifecycle. Read [references/operate/CAPABILITY.md](references/operate/CAPABILITY.md).
+
+- Package a BPMN Process Orchestration project
+- Upload to Studio Web or publish/deploy when explicitly requested
+- Run/debug a process instance only after explicit user consent
+- Manage jobs, instances, incidents, variables, and lifecycle actions
+
+**Diagnose** - investigating failed or misbehaving runs. Read [references/diagnose/CAPABILITY.md](references/diagnose/CAPABILITY.md).
+
+- Fetch incidents, variables, element executions, and deployed BPMN assets
+- Correlate runtime failures back to BPMN element IDs and local XML
+- Identify authoring, packaging, binding, and Integration Service enrichment failures
+
+## Capability router
+
+| I want to... | Read |
+| --- | --- |
+| Create or edit BPMN source | [references/author/CAPABILITY.md](references/author/CAPABILITY.md) |
+| Package, upload, publish, run, or manage lifecycle | [references/operate/CAPABILITY.md](references/operate/CAPABILITY.md) |
+| Diagnose a failed or misbehaving run | [references/diagnose/CAPABILITY.md](references/diagnose/CAPABILITY.md) |
+| Understand project layout and package files | [references/shared/project-layout.md](references/shared/project-layout.md) |
+| Regenerate or verify local package metadata | [references/shared/local-metadata-regeneration-guide.md](references/shared/local-metadata-regeneration-guide.md) |
+| Understand BPMN XML authoring boundaries | [references/shared/bpmn-xml-contract.md](references/shared/bpmn-xml-contract.md) |
+| Copy minimal XML shells per supported wrapper | [references/shared/wrapper-shells.md](references/shared/wrapper-shells.md) |
+| Understand variables, bindings, entry points, and expressions | [references/shared/variables-bindings-expressions.md](references/shared/variables-bindings-expressions.md) |
+| Author lint-compatible runtime expressions | [references/shared/expression-authoring.md](references/shared/expression-authoring.md) |
+| Author Maestro retry and error handling | [references/shared/error-handling.md](references/shared/error-handling.md) |
+| Understand CLI conventions and side-effect boundaries | [references/shared/cli-conventions.md](references/shared/cli-conventions.md) |
+| Keep examples and commits public-safe | [references/shared/public-safety.md](references/shared/public-safety.md) |
+
+## Critical rules (universal)
+
+1. **BPMN XML is the source of record** - edit `.bpmn` for process structure; treat generated package JSON as derived unless a CLI contract explicitly says otherwise.
+2. **Model owns skeleton and documented non-IS XML only** - generate BPMN control flow, diagram coordinates, root variables, mappings, entry point IDs, script tasks, retry/error metadata, and documented non-Integration-Service UiPath extensions. Do not invent undocumented UiPath extension payloads.
+3. **Use two-pass authoring for substantial changes** - write the standard BPMN skeleton first, get operator confirmation of the process shape, then fill model-owned UiPath extension XML.
+4. **CLI owns Integration Service enrichment** - Integration Service activities/triggers, connection bindings, connector metadata, dynamic schemas, trigger properties, and generated output templates must come from registry-backed CLI enrichment or validation.
+5. **Never use private source material in skill content** - no exported customer BPMN, tenant URLs, folder keys, connection IDs, user names, process names, local paths, screenshots, or temporary mission notes. Examples must be synthetic.
+6. **Use JSON output for parsed CLI calls** - whenever CLI output is parsed programmatically, request JSON output from the CLI and preserve the raw command result in the local transcript or a sanitized report.
+7. **Do not run debug or deployed process execution without explicit user consent** - debug/run can trigger real side effects in external systems.
+8. **Ask before cloud-side mutations** - upload, publish, deploy, run, pause, resume, cancel, retry, migrate, and move-cursor operations require a clear user decision.
+9. **Do not automatically invoke sibling skills** - when BPMN references an RPA process, agent, app, API workflow, or case asset that is missing, identify the dependency and provide handoff instructions.
+10. **Validate before operate** - run local XML/project/package validation before upload, publish, or debug. Treat validation warnings about CLI-owned enrichment as blockers for real runs when the target element can execute.
+11. **Preserve unknown extension payloads unless normalizing explicitly** - do not delete or rewrite user-authored or imported UiPath extension XML just because the skill cannot fully interpret it.
+
+## Anti-patterns (universal)
+
+- **Do not hand-author Integration Service connection details** - connection IDs, resource keys, connector labels, trigger property bindings, and generated schemas are CLI-owned.
+- **Do not rely on BPMN without diagrams for Studio Web import** - a valid diagram and plane are required, and visible elements need shapes or waypoints.
+- **Do not edit derived package files as the primary fix** - fix the BPMN source or rerun the CLI generator/enricher unless the package file itself is the documented source for that field.
+- **Do not include real exported XML snippets in docs or examples** - summarize patterns using public-safe synthetic IDs and placeholder values.
+- **Do not use validation fixtures as greenfield templates** - fixtures are
+  coverage examples, not the authoring source of truth. Use capability docs,
+  shared contracts, wrapper shells, and the specific plugin or task recipe
+  instead.
+
+> Trouble? Send public-safe product feedback through the repository's normal feedback path.

package/skills/uipath-maestro-bpmn/fixtures/validation/README.md

@@ -0,0 +1,94 @@
+# Maestro BPMN Validation Fixtures
+
+Public-safe fixture corpus for the `uipath-maestro-bpmn` skill maintenance checks. These files are synthetic and intentionally cover Maestro BPMN XML wrappers, preservation boundaries, and generated package-output families.
+
+## Fixture Set
+
+| Fixture | Coverage |
+| --- | --- |
+| `linear-process/` | Minimal executable process, root variables, entry point ID, BPMN DI, and generated package metadata. |
+| `imported-brownfield-preservation/` | Imported brownfield preservation case with numeric `uipath:migrationVersion`, legacy `uipath:scriptVersion value="v2"`, and matching generated package metadata. |
+| `gateway-boundary-error/` | Exclusive gateway conditions/defaults, service task retry/error mapping, boundary error event, terminate end, tags, and package manifest checks. |
+| `integration-service-enriched/` | Integration Service trigger and activity extensions, root connection/property bindings, generated `bindings_v2.json` resources, entry point schema, and package metadata. |
+| `subprocess-multi-instance/` | Subprocess scoped variables, multi-instance loop metadata, script task metadata, mappings, message event, and diagram/waypoint coverage. |
+| `contract-variants/` | Representative public-safe Orchestrator agent, A2A, API workflow, business rule, queue, agentic/case call activity, message send event, case-management draft/preserve shells, `Intsvc.WaitForEvent`, numeric migration, legacy script, and preserve-only extension variants. |
+| `registry-coverage-matrix/` | Synthetic static wrapper coverage for current registry rows not otherwise covered by the corpus, including HITL, plain RPA, timer, HTTP, unified HTTP, and remaining Integration Service execution variants. |
+| `wrapper-family-contract/` | Maestro BPMN wrapper coverage for `Orchestrator.StartAgentJob` (folder-deployed coded or low-code agent with the required `name`+`folderPath` binding pair), API workflow, business rule, queue wait, case-management call activity, and `Intsvc.WaitForEvent` enrichment paths. `A2A.AgentExecution` (external A2A) coverage stays in `contract-variants/`. |
+| `agent-invocation/` | End-to-end runnable example for invoking a folder-deployed coded (Python) or low-code agent: start-scoped `uipath:inputOutput` entry input, `Orchestrator.StartAgentJob` with the `name`+`folderPath` binding pair, and direct `JobArguments` / `Process response` payloads on `uipath:activity`. Matches the shape enforced by the Maestro BPMN packager validator. |
+
+## Contract Coverage Scope
+
+The `contract-variants/` fixture is representative coverage for public-safe XML shells and preservation boundaries; it is not a claim that every row in `references/author/references/supported-elements.md` has a static fixture. Coverage is split as follows:
+
+| Bucket | Static fixture coverage |
+| --- | --- |
+| Model-owned or model-draft non-Integration-Service shells | Covered by `contract-variants/` for Orchestrator agent/API workflow/queue/business-rule wrappers, agentic and case-management sync/async call activities, and `Maestro.SendMessageEvent`. |
+| Preserve-only or dedicated-contract case-management XML | Covered by `contract-variants/` for `uipath:caseManagement`, generic `uipath:Activity`, `Maestro.CasePlanScheduler`, `Maestro.CaseManagerGuardrails`, and `Maestro.CaseRulesEvaluator` preservation/draft shells. |
+| CLI-owned `Intsvc.*` enrichment | Covered as synthetic wrapper shells only. `contract-variants/` keeps one representative `Intsvc.WaitForEvent` shell; `integration-service-enriched/` covers enriched trigger/activity sidecars; `registry-coverage-matrix/` covers the remaining current registry wrapper names without claiming connector-specific schemas are model-owned. |
+| Standard BPMN structures | Covered across the fixture corpus by targeted structural checks, not by a row-for-row supported-elements matrix. |
+
+The Integration Service fixture is intentionally shape-only. It verifies where enriched XML, bindings, and generated package metadata appear, but it is not evidence that those connector values are valid for a live tenant. Real projects still require current registry-backed enrichment before Operate.
+
+## Pilot Scenarios
+
+The corpus was piloted against these public-safe authoring and debugging requests:
+
+| Request | Fixtures used | Result |
+| --- | --- | --- |
+| Create a service-desk intake process with a connector trigger, ticket creation, and generated package metadata. | `integration-service-enriched/` | Kept the model/CLI boundary explicit: connector metadata, connection bindings, and generated resources must come from enrichment before Operate. |
+| Validate that imported XML survives local checks without normalizing legacy script metadata. | `imported-brownfield-preservation/` | Covers the XML analyst baseline by preserving numeric `uipath:migrationVersion` values and imported `uipath:scriptVersion value="v2"` alongside package metadata. |
+| Debug an approval workflow where the run takes the wrong branch and then faults on error handling. | `gateway-boundary-error/` | Tightened checks around gateway conditions/defaults, boundary error references, and package metadata drift. |
+| Author a batch item processor with a scoped subprocess, sequential multi-instance loop, script normalization, and a message wait. | `subprocess-multi-instance/` | Added checks for message references and multi-instance collection/item metadata so stuck-loop and stuck-wait issues are caught locally. |
+| Review imported XML that mixes public Orchestrator wrappers, Integration Service waits, message events, case-management draft/preserve shells, numeric migrations, legacy script metadata, and unsupported UiPath extension payloads. | `contract-variants/` | Added structural checks that wrappers stay on the documented BPMN element classes and preserve-only payloads are retained without private identifiers. |
+| Compare the static fixture corpus against the registry surface exposed by `uip maestro bpmn registry list`. | `registry-coverage-matrix/` plus existing fixtures | Filled the missing wrapper rows with synthetic placeholders while keeping cloud resource resolution as a later authenticated test. |
+| Verify that Maestro BPMN XML keeps the documented wrapper family for agent execution, API workflow, business rules, queue wait, case management, and connector wait nodes. | `wrapper-family-contract/` | Added contract checks for wrapper-to-service-type alignment so coverage fails if supported behavior drifts to the wrong BPMN element family. |
+| Invoke a folder-deployed coded Python agent end-to-end from BPMN with the binding-pair shape (`name`+`folderPath`, `resource="process"`, `resourceSubType="Agent"`) and a downstream-readable entry input. | `agent-invocation/` | Demonstrates the shape that survives both `uip maestro bpmn pack` and `uip solution pack` validation. |
+
+## Validation Output
+
+Latest local fixture validation from this pilot:
+
+```text
+validation_fixture_projects=9 bpmn_files=9 errors=0
+```
+
+The local checker also runs a narrow negative regression for a misnamed
+single-file BPMN project, seeded from the `gateway-boundary-error/` fixture. The
+regression passes only when basename validation rejects copied project metadata
+whose single BPMN file no longer matches the project directory name.
+
+## Open Questions for Maestro Owners
+
+- Should `uipath:loopCharacteristics` remain the stable public contract for multi-instance collection and item binding, or should fixture validation prefer registry/CLI-generated loop metadata when available?
+- Which `Intsvc.*` context fields are mandatory across all connector families versus connector-specific fields that should stay outside this static checker?
+
+## Maintenance Commands
+
+Contributor check from the repository root:
+
+```bash
+bash skills/uipath-maestro-bpmn/.maintenance/check-validation-fixtures.sh
+```
+
+Full skill maintenance suite from the repository root:
+
+```bash
+bash skills/uipath-maestro-bpmn/.maintenance/check-all.sh
+```
+
+`check-all.sh` includes real `uip maestro bpmn pack` coverage for every fixture.
+When `uip login status` reports a logged-in tenant, it also runs
+`uip solution pack` for the `agent-invocation/` runnable contract fixture.
+
+CI should run the same commands before skill evals. The smoke eval task for this corpus is:
+
+```bash
+cd tests
+make tags TAGS="uipath-maestro-bpmn smoke" EXPERIMENT=experiments/smoke.yaml
+```
+
+## Public-Safety Rules
+
+- Do not copy raw exported BPMN, screenshots, tenant metadata, connection IDs, folder keys, URLs, user names, private process names, or temporary mission notes into these fixtures.
+- Keep IDs readable and synthetic, for example `Task_CreateTicket` and `Binding_ServiceDeskConnection`.
+- Keep package metadata deterministic and local to the fixture folder.

package/skills/uipath-maestro-bpmn/fixtures/validation/agent-invocation/agent-invocation.bpmn

@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:uipath="http://uipath.org/schema/bpmn" id="Definitions_AgentInvocation" targetNamespace="http://uipath.com/synthetic/maestro-bpmn/agent-invocation">
+  <bpmn:process id="Process_AgentInvocation" name="Agent Invocation" isExecutable="true">
+    <bpmn:extensionElements>
+      <uipath:variables version="v1">
+        <uipath:inputOutput id="Var_Request" name="request" type="json" elementId="Start_Manual"><![CDATA[{"type":"object","properties":{"prompt":{"type":"string"}}}]]></uipath:inputOutput>
+        <uipath:inputOutput id="Var_AgentResult" name="agentResult" type="json" />
+      </uipath:variables>
+      <uipath:bindings version="v1">
+        <uipath:binding id="Binding_AgentName" name="Synthetic Agent" type="process" elementId="Task_StartAgentJob" resource="process" resourceSubType="Agent" resourceKey="synthetic-agent" propertyAttribute="name" />
+        <uipath:binding id="Binding_AgentFolderPath" name="Synthetic Agent" type="process" elementId="Task_StartAgentJob" resource="process" resourceSubType="Agent" resourceKey="synthetic-agent" propertyAttribute="folderPath" />
+      </uipath:bindings>
+    </bpmn:extensionElements>
+    <bpmn:startEvent id="Start_Manual" name="Start">
+      <bpmn:extensionElements>
+        <uipath:entryPointId value="Entry_AgentInvocation" />
+      </bpmn:extensionElements>
+      <bpmn:outgoing>Flow_Start_To_Agent</bpmn:outgoing>
+    </bpmn:startEvent>
+    <bpmn:serviceTask id="Task_StartAgentJob" name="Start Agent Job">
+      <bpmn:extensionElements>
+        <uipath:activity version="v1">
+          <uipath:type value="Orchestrator.StartAgentJob" version="v1" />
+          <uipath:context>
+            <uipath:input name="name" type="string" value="=bindings.Binding_AgentName" />
+            <uipath:input name="folderPath" type="string" value="=bindings.Binding_AgentFolderPath" />
+          </uipath:context>
+          <uipath:input name="JobArguments" type="json" target="bodyField"><![CDATA[{"prompt":"=vars.Var_Request"}]]></uipath:input>
+          <uipath:output name="Process response" type="Orchestrator.RunJob" var="Var_AgentResult" />
+        </uipath:activity>
+      </bpmn:extensionElements>
+      <bpmn:incoming>Flow_Start_To_Agent</bpmn:incoming>
+      <bpmn:outgoing>Flow_Agent_To_End</bpmn:outgoing>
+    </bpmn:serviceTask>
+    <bpmn:endEvent id="End_Done" name="Done">
+      <bpmn:incoming>Flow_Agent_To_End</bpmn:incoming>
+    </bpmn:endEvent>
+    <bpmn:sequenceFlow id="Flow_Start_To_Agent" sourceRef="Start_Manual" targetRef="Task_StartAgentJob" />
+    <bpmn:sequenceFlow id="Flow_Agent_To_End" sourceRef="Task_StartAgentJob" targetRef="End_Done" />
+  </bpmn:process>
+  <bpmndi:BPMNDiagram id="Diagram_AgentInvocation">
+    <bpmndi:BPMNPlane id="Plane_AgentInvocation" bpmnElement="Process_AgentInvocation">
+      <bpmndi:BPMNShape id="Shape_Start_Manual" bpmnElement="Start_Manual">
+        <dc:Bounds x="120" y="120" width="36" height="36" />
+      </bpmndi:BPMNShape>
+      <bpmndi:BPMNShape id="Shape_Task_StartAgentJob" bpmnElement="Task_StartAgentJob">
+        <dc:Bounds x="220" y="98" width="160" height="80" />
+      </bpmndi:BPMNShape>
+      <bpmndi:BPMNShape id="Shape_End_Done" bpmnElement="End_Done">
+        <dc:Bounds x="450" y="120" width="36" height="36" />
+      </bpmndi:BPMNShape>
+      <bpmndi:BPMNEdge id="Edge_Flow_Start_To_Agent" bpmnElement="Flow_Start_To_Agent">
+        <di:waypoint x="156" y="138" />
+        <di:waypoint x="220" y="138" />
+      </bpmndi:BPMNEdge>
+      <bpmndi:BPMNEdge id="Edge_Flow_Agent_To_End" bpmnElement="Flow_Agent_To_End">
+        <di:waypoint x="380" y="138" />
+        <di:waypoint x="450" y="138" />
+      </bpmndi:BPMNEdge>
+    </bpmndi:BPMNPlane>
+  </bpmndi:BPMNDiagram>
+</bpmn:definitions>

package/skills/uipath-maestro-bpmn/fixtures/validation/agent-invocation/bindings_v2.json

@@ -0,0 +1,37 @@
+{
+  "version": "2.0",
+  "resources": [
+    {
+      "id": "Binding_AgentName",
+      "kind": "process",
+      "resource": "process",
+      "resourceSubType": "Agent",
+      "propertyAttribute": "name",
+      "name": "Synthetic Agent",
+      "resourceKey": "synthetic-agent",
+      "metadata": {
+        "BindingsVersion": "v1",
+        "DisplayLabel": "Synthetic Agent",
+        "SolutionsSupport": "Required",
+        "SubType": "Agent",
+        "PropertyAttribute": "name"
+      }
+    },
+    {
+      "id": "Binding_AgentFolderPath",
+      "kind": "process",
+      "resource": "process",
+      "resourceSubType": "Agent",
+      "propertyAttribute": "folderPath",
+      "name": "Synthetic Agent",
+      "resourceKey": "synthetic-agent",
+      "metadata": {
+        "BindingsVersion": "v1",
+        "DisplayLabel": "Synthetic Agent",
+        "SolutionsSupport": "Required",
+        "SubType": "Agent",
+        "PropertyAttribute": "folderPath"
+      }
+    }
+  ]
+}

package/skills/uipath-maestro-bpmn/fixtures/validation/agent-invocation/entry-points.json

@@ -0,0 +1,21 @@
+{
+  "entryPoints": [
+    {
+      "id": "Entry_AgentInvocation",
+      "name": "Start",
+      "filePath": "/content/agent-invocation.bpmn#Start_Manual",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "request": {
+            "type": "object"
+          }
+        }
+      },
+      "outputSchema": {
+        "type": "object",
+        "properties": {}
+      }
+    }
+  ]
+}

package/skills/uipath-maestro-bpmn/fixtures/validation/agent-invocation/operate.json

@@ -0,0 +1,9 @@
+{
+  "projectId": "Fixture.AgentInvocation",
+  "main": "agent-invocation.bpmn",
+  "contentType": "ProcessOrchestration",
+  "targetFramework": "Portable",
+  "runtimeOptions": {
+    "requiresUserInteraction": false
+  }
+}

package/skills/uipath-maestro-bpmn/fixtures/validation/agent-invocation/package-descriptor.json

@@ -0,0 +1,10 @@
+{
+  "id": "Fixture.AgentInvocation",
+  "version": "1.0.0",
+  "content": [
+    "content/agent-invocation.bpmn",
+    "content/bindings_v2.json",
+    "content/entry-points.json",
+    "content/operate.json"
+  ]
+}

package/skills/uipath-maestro-bpmn/fixtures/validation/agent-invocation/project.uiproj

@@ -0,0 +1,7 @@
+{
+  "projectVersion": "1.0.0",
+  "ProjectType": "ProcessOrchestration",
+  "Name": "AgentInvocation",
+  "description": "End-to-end fixture: start-scoped entry input plus Orchestrator.StartAgentJob with the name+folderPath binding pair.",
+  "main": "agent-invocation.bpmn"
+}

package/skills/uipath-maestro-bpmn/fixtures/validation/contract-variants/bindings_v2.json

@@ -0,0 +1,68 @@
+{
+  "version": "2.0",
+  "resources": [
+    {
+      "id": "Binding_AgentName",
+      "kind": "process",
+      "name": "Synthetic Agent",
+      "resourceKey": "synthetic-agent",
+      "metadata": {
+        "BindingsVersion": "v1",
+        "DisplayLabel": "Synthetic Agent",
+        "SolutionsSupport": "Required",
+        "SubType": "Agent",
+        "PropertyAttribute": "name"
+      },
+      "resource": "process",
+      "resourceSubType": "Agent",
+      "propertyAttribute": "name"
+    },
+    {
+      "id": "Binding_AgentFolderPath",
+      "kind": "process",
+      "name": "Synthetic Agent",
+      "resourceKey": "synthetic-agent",
+      "metadata": {
+        "BindingsVersion": "v1",
+        "DisplayLabel": "Synthetic Agent",
+        "SolutionsSupport": "Required",
+        "SubType": "Agent",
+        "PropertyAttribute": "folderPath"
+      },
+      "resource": "process",
+      "resourceSubType": "Agent",
+      "propertyAttribute": "folderPath"
+    },
+    {
+      "id": "Binding_EventConnection",
+      "kind": "connection",
+      "name": "Synthetic Event Connection",
+      "resourceKey": "synthetic-event-connection",
+      "metadata": {
+        "BindingsVersion": "v1",
+        "DisplayLabel": "Synthetic Event Connection",
+        "SolutionsSupport": "Required",
+        "SubType": "connection",
+        "Connector": "synthetic-events"
+      },
+      "resource": "SyntheticEvents",
+      "resourceSubType": "connection"
+    },
+    {
+      "id": "Binding_EventTrigger",
+      "kind": "eventTrigger",
+      "name": "Synthetic Event Trigger",
+      "resourceKey": "synthetic-event-trigger",
+      "metadata": {
+        "BindingsVersion": "v1",
+        "DisplayLabel": "Synthetic Event Trigger",
+        "SolutionsSupport": "Required",
+        "SubType": "eventTrigger",
+        "Connector": "synthetic-events",
+        "EventName": "external-signal"
+      },
+      "resource": "SyntheticEvents.ExternalSignal",
+      "resourceSubType": "eventTrigger"
+    }
+  ]
+}