From 4f6553e3018155815c41fae79f39d91bd9ba0e94 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?=
 <felipe.garcia@datascope.io>
Date: Mon, 24 Aug 2026 15:39:55 -0400
Subject: [PATCH 1/7] docs: add the 5 Power Automate actions to the connector

Adds Assign Task, Change Form Status, Modify Form Answer, Send Data,
and Create Ticket as actions to the custom connector swagger, each
verified against the actual Rails controllers rather than assumed
from the equivalent Zapier definitions. Documents the actions in the
three guide languages and the Data Export overview.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 source/index.html.md                          |   2 +-
 .../power_automate/apiDefinition.swagger.json | 486 ++++++++++++++++++
 .../power_automate/connector_guide_en.html.md |  10 +
 .../power_automate/connector_guide_es.html.md |  10 +
 .../power_automate/connector_guide_pt.html.md |  10 +
 5 files changed, 517 insertions(+), 1 deletion(-)

diff --git a/source/index.html.md b/source/index.html.md
index ce4679528e7..1e9689a7152 100644
--- a/source/index.html.md
+++ b/source/index.html.md
@@ -73,7 +73,7 @@ Using both is normal. A webhook for the immediate reaction, a connector for the
 
 ## Microsoft Power Automate [Beta]
 
-DataScope publishes a custom connector for Microsoft Power Automate, so you can trigger flows from form answers, generated PDFs, task assignments, tickets and signature events, delivered as dynamic content instead of raw webhook JSON.
+DataScope publishes a custom connector for Microsoft Power Automate, so you can trigger flows from form answers, generated PDFs, task assignments, tickets and signature events, delivered as dynamic content instead of raw webhook JSON, and act back on DataScope with actions like assigning a task or creating a ticket.
 
 <aside class="notice">
 We have had ongoing trouble keeping the connector published in the official Power Automate connector gallery in sync with the latest version. Until that is resolved, the fastest way to connect is to build the custom connector yourself from the definition file below.
diff --git a/source/power_automate/apiDefinition.swagger.json b/source/power_automate/apiDefinition.swagger.json
index 9b172cfed08..325d7b58e5c 100644
--- a/source/power_automate/apiDefinition.swagger.json
+++ b/source/power_automate/apiDefinition.swagger.json
@@ -2046,6 +2046,492 @@
         ]
       }
     },
+    "/assign_task": {
+      "post": {
+        "summary": "Assign Task (Tasks)",
+        "description": "Assigns a task on a form to a user, optionally scheduling it and linking it to a location. If a task with the same code already exists, it is updated instead of creating a new one.",
+        "operationId": "AssignTaskV2",
+        "consumes": [
+          "application/x-www-form-urlencoded"
+        ],
+        "parameters": [
+          {
+            "name": "form_id",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Identifier of the form the task will be assigned on."
+          },
+          {
+            "name": "user_id",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Email or identifier of the user the task is assigned to. If it does not match an existing user, the task may fall back to another user of the account, so use a valid, existing identifier."
+          },
+          {
+            "name": "code",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Code that identifies the task assignment. If a task with this code already exists, it is updated instead of created."
+          },
+          {
+            "name": "task_instruction",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Instructions shown to the user for this task."
+          },
+          {
+            "name": "date",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Date and time the task is scheduled for. Defaults to the current date and time when omitted or invalid."
+          },
+          {
+            "name": "gap",
+            "in": "query",
+            "type": "integer",
+            "required": false,
+            "description": "Time window, in hours, around the scheduled date during which the task can be completed. Defaults to 4."
+          },
+          {
+            "name": "mandatory",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "enum": [
+              "for_everyone",
+              "for_one",
+              "for_nobody"
+            ],
+            "description": "Who the task is mandatory for. Defaults to for_everyone."
+          },
+          {
+            "name": "late_response_allowed",
+            "in": "query",
+            "type": "boolean",
+            "required": false,
+            "description": "Indicates whether the task can still be completed after its scheduled window."
+          },
+          {
+            "name": "location_name",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Name of the location linked to the task. A new location is created if it does not already exist."
+          },
+          {
+            "name": "location_address",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Address of the location linked to the task."
+          },
+          {
+            "name": "l_code",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Code used to find an existing location linked to the task."
+          },
+          {
+            "name": "l_phone",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Phone number of the location linked to the task."
+          },
+          {
+            "name": "l_email",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Email address of the location linked to the task."
+          },
+          {
+            "name": "c_name",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Name of the company linked to the location."
+          },
+          {
+            "name": "c_code",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Code of the company linked to the location."
+          },
+          {
+            "name": "latitude",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Latitude of the location linked to the task."
+          },
+          {
+            "name": "longitude",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Longitude of the location linked to the task."
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Task assigned successfully, or an error reported in the response body.",
+            "schema": {
+              "type": "object",
+              "properties": {
+                "result": {
+                  "type": "string",
+                  "description": "Outcome of the request, for example ok or an error message."
+                },
+                "task": {
+                  "type": "object",
+                  "description": "The created or updated task assignment. Its exact set of fields is not fully documented here."
+                }
+              }
+            }
+          },
+          "400": {
+            "description": "The task could not be assigned."
+          }
+        }
+      }
+    },
+    "/change_state": {
+      "post": {
+        "summary": "Change Form Status (Forms)",
+        "description": "Changes the status of an existing form answer.",
+        "operationId": "ChangeFormStatus",
+        "consumes": [
+          "application/x-www-form-urlencoded"
+        ],
+        "parameters": [
+          {
+            "name": "form_name",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Name of the form the answer belongs to."
+          },
+          {
+            "name": "form_code",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Code of the form answer to update."
+          },
+          {
+            "name": "form_state_id",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Identifier of the status to set on the form answer."
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Form answer status updated successfully.",
+            "schema": {
+              "type": "object",
+              "properties": {
+                "status": {
+                  "type": "string",
+                  "description": "Outcome of the request, for example ok."
+                },
+                "form_answer": {
+                  "type": "object",
+                  "description": "The updated form answer. Its exact set of fields is not fully documented here."
+                }
+              }
+            }
+          },
+          "400": {
+            "description": "The status could not be changed, for example because the form, form answer, or status was not found."
+          }
+        }
+      }
+    },
+    "/change_form": {
+      "post": {
+        "summary": "Modify Form Answer (Forms)",
+        "description": "Creates or updates a single question's answer on an existing form answer. The new answer is always stored as free text, regardless of the original question type.",
+        "operationId": "ModifyFormAnswer",
+        "consumes": [
+          "application/x-www-form-urlencoded"
+        ],
+        "parameters": [
+          {
+            "name": "form_name",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Name or identifier of the form the answer belongs to."
+          },
+          {
+            "name": "form_code",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Code of the form answer to update. The alias code is also accepted."
+          },
+          {
+            "name": "question_name",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Name of the question to create or update."
+          },
+          {
+            "name": "question_value",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "New value to set for the question."
+          },
+          {
+            "name": "subform_index",
+            "in": "query",
+            "type": "integer",
+            "required": false,
+            "description": "Row number of a subform table to update. When omitted, the answer at the root of the form is updated. Behavior for values other than a positive row number is not fully documented here."
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Form answer updated, or an error reported in the response body.",
+            "schema": {
+              "type": "object",
+              "properties": {
+                "status": {
+                  "type": "string",
+                  "description": "Outcome of the request: ok or error."
+                },
+                "form_answer": {
+                  "type": "object",
+                  "description": "The updated form answer. Its exact set of fields is not fully documented here."
+                }
+              }
+            }
+          },
+          "400": {
+            "description": "The request could not be processed, for example because the form or token was missing."
+          }
+        }
+      }
+    },
+    "/create_pdf": {
+      "post": {
+        "summary": "Forms: Send Data / New Answer [Beta]",
+        "description": "Generates a new form answer and its PDF from an existing form template. Any parameter besides form_id, emails, token, and action is treated as an answer to the matching question in the form, so this action supports as many additional fields as the selected form defines questions for. Not all question types are fully supported, which may result in unexpected behavior. This action does not trigger GSheet Sync, Automatic Signature, or other webhooks such as Power Automate triggers.",
+        "operationId": "SendData",
+        "consumes": [
+          "application/x-www-form-urlencoded"
+        ],
+        "parameters": [
+          {
+            "name": "form_id",
+            "in": "query",
+            "type": "string",
+            "required": true,
+            "description": "Identifier of the form template used to generate the new answer."
+          },
+          {
+            "name": "emails",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Email addresses that receive the generated PDF."
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Form answer and PDF generated successfully. If no question values are provided besides form_id, emails, and token, the response behavior is not fully documented here.",
+            "schema": {
+              "type": "object",
+              "properties": {
+                "ok": {
+                  "type": "boolean",
+                  "description": "Indicates whether the request succeeded."
+                },
+                "form_answer_id": {
+                  "type": "integer",
+                  "description": "Identifier of the generated form answer."
+                }
+              }
+            }
+          },
+          "400": {
+            "description": "The request could not be processed, for example because the account or form was not found."
+          }
+        }
+      }
+    },
+    "/findings/create": {
+      "post": {
+        "summary": "Tickets: Create Ticket",
+        "description": "Creates a new ticket. Tickets are not stored in the same database as forms and tasks, so some response fields below could not be fully verified against the underlying storage.",
+        "operationId": "CreateFinding",
+        "consumes": [
+          "application/x-www-form-urlencoded"
+        ],
+        "parameters": [
+          {
+            "name": "name",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Name of the ticket."
+          },
+          {
+            "name": "description",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Description of the ticket."
+          },
+          {
+            "name": "type",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Ticket type. When set, it can fill in defaults such as priority, expiration, location, and assignees, which may override other values sent in the same request."
+          },
+          {
+            "name": "author_email",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Email of the user registered as the author of the ticket. If it does not match an existing user, the ticket is created under the account associated with the token."
+          },
+          {
+            "name": "creation_date",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Date and time the ticket was created."
+          },
+          {
+            "name": "expiration_date",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Date and time the ticket expires."
+          },
+          {
+            "name": "status",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "enum": [
+              "open",
+              "in_progress",
+              "paused",
+              "closed"
+            ],
+            "description": "Status of the ticket."
+          },
+          {
+            "name": "priority",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "enum": [
+              "low",
+              "medium",
+              "high",
+              "critical"
+            ],
+            "description": "Priority of the ticket."
+          },
+          {
+            "name": "location_id",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Identifier of the location linked to the ticket."
+          },
+          {
+            "name": "location_name",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Name of the location linked to the ticket."
+          },
+          {
+            "name": "location_type",
+            "in": "query",
+            "type": "string",
+            "required": false,
+            "description": "Type of the location linked to the ticket."
+          },
+          {
+            "name": "assignees",
+            "in": "query",
+            "type": "array",
+            "items": {
+              "type": "string"
+            },
+            "collectionFormat": "multi",
+            "required": false,
+            "description": "Users assigned to the ticket."
+          },
+          {
+            "name": "invitees",
+            "in": "query",
+            "type": "array",
+            "items": {
+              "type": "string"
+            },
+            "collectionFormat": "multi",
+            "required": false,
+            "description": "Users invited to the ticket."
+          }
+        ],
+        "responses": {
+          "201": {
+            "description": "Ticket created successfully.",
+            "schema": {
+              "type": "object",
+              "properties": {
+                "id": {
+                  "type": "string",
+                  "description": "Identifier of the created ticket."
+                },
+                "finding": {
+                  "type": "object",
+                  "description": "The created ticket. Its exact set of fields could not be fully verified against the underlying storage."
+                }
+              }
+            }
+          },
+          "403": {
+            "description": "Ticket access is not available for this account, for example because the trial has not started or access has been closed."
+          },
+          "422": {
+            "description": "The ticket could not be created.",
+            "schema": {
+              "type": "object",
+              "properties": {
+                "error": {
+                  "type": "string",
+                  "description": "Description of the reason the ticket could not be created."
+                },
+                "finding": {
+                  "type": "object",
+                  "description": "Empty object."
+                }
+              }
+            }
+          }
+        }
+      }
+    },
     "/delete_hooks/{account_id}/{webhook_id}/{uuid}": {
       "delete": {
         "summary": "Delete webhook subscription",
diff --git a/source/power_automate/connector_guide_en.html.md b/source/power_automate/connector_guide_en.html.md
index 7ef2aee1554..ff1145b57ab 100644
--- a/source/power_automate/connector_guide_en.html.md
+++ b/source/power_automate/connector_guide_en.html.md
@@ -102,6 +102,16 @@ The connector provides the following triggers:
 Each trigger delivers the event data as dynamic content, ready to use in the
 following steps of the flow without having to parse the JSON manually.
 
+The connector also provides the following actions, so a flow can act back on DataScope instead of only reacting to it:
+
+| Action | What it does |
+|---|---|
+| Assign Task | Assigns a task on a form to a user, optionally scheduling it and linking it to a location |
+| Change Form Status | Changes the status of a form answer |
+| Modify Form Answer | Creates or updates an answer within a form response |
+| Send Data | Generates a new form answer and its PDF from an existing template |
+| Create Ticket | Creates a new ticket |
+
 ## Important considerations
 
 - **One active connection per form.** Triggers associated with a form support
diff --git a/source/power_automate/connector_guide_es.html.md b/source/power_automate/connector_guide_es.html.md
index 8f4cb741328..8f34c3c7bd8 100644
--- a/source/power_automate/connector_guide_es.html.md
+++ b/source/power_automate/connector_guide_es.html.md
@@ -102,6 +102,16 @@ Cada disparador entrega los datos del evento como contenido dinámico, listos
 para usar en los pasos siguientes del flujo sin necesidad de procesar el JSON
 manualmente.
 
+El conector también entrega las siguientes actions, para que un flujo pueda actuar sobre DataScope y no solo reaccionar a sus eventos:
+
+| Action | Qué hace |
+|---|---|
+| Assign Task | Asigna una tarea de un formulario a un usuario, opcionalmente agendándola y vinculándola a una ubicación |
+| Change Form Status | Cambia el estado de una respuesta de formulario |
+| Modify Form Answer | Crea o modifica una respuesta dentro de un formulario |
+| Send Data | Genera una nueva respuesta de formulario y su PDF a partir de una plantilla existente |
+| Create Ticket | Crea un nuevo ticket |
+
 ## Consideraciones importantes
 
 - **Una conexión activa por formulario.** Los disparadores asociados a un
diff --git a/source/power_automate/connector_guide_pt.html.md b/source/power_automate/connector_guide_pt.html.md
index 7489217537d..4c8a7933329 100644
--- a/source/power_automate/connector_guide_pt.html.md
+++ b/source/power_automate/connector_guide_pt.html.md
@@ -103,6 +103,16 @@ Cada disparador entrega os dados do evento como conteúdo dinâmico, prontos
 para usar nas próximas etapas do fluxo sem precisar processar o JSON
 manualmente.
 
+O conector também oferece as seguintes actions, para que um fluxo possa agir sobre o DataScope, e não só reagir aos seus eventos:
+
+| Action | O que faz |
+|---|---|
+| Assign Task | Atribui uma tarefa de um formulário a um usuário, opcionalmente agendando-a e vinculando-a a um local |
+| Change Form Status | Muda o status de uma resposta de formulário |
+| Modify Form Answer | Cria ou modifica uma resposta dentro de um formulário |
+| Send Data | Gera uma nova resposta de formulário e seu PDF a partir de um modelo existente |
+| Create Ticket | Cria um novo ticket |
+
 ## Considerações importantes
 
 - **Uma conexão ativa por formulário.** Os disparadores associados a um

From 35f33565c15026f92fde0a0169b5f1858d710891 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?=
 <felipe.garcia@datascope.io>
Date: Mon, 24 Aug 2026 16:08:09 -0400
Subject: [PATCH 2/7] fix: use a supported collectionFormat for the
 assignees/invitees params

Power Automate's OpenAPI validator rejects collectionFormat: multi
(WorkflowTriggerNotFound-style ResponseSwaggerSchemaValidationFailure
at import time, not at runtime). csv is one of the values it accepts.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 source/power_automate/apiDefinition.swagger.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/power_automate/apiDefinition.swagger.json b/source/power_automate/apiDefinition.swagger.json
index 325d7b58e5c..9933beefdd1 100644
--- a/source/power_automate/apiDefinition.swagger.json
+++ b/source/power_automate/apiDefinition.swagger.json
@@ -2477,7 +2477,7 @@
             "items": {
               "type": "string"
             },
-            "collectionFormat": "multi",
+            "collectionFormat": "csv",
             "required": false,
             "description": "Users assigned to the ticket."
           },
@@ -2488,7 +2488,7 @@
             "items": {
               "type": "string"
             },
-            "collectionFormat": "multi",
+            "collectionFormat": "csv",
             "required": false,
             "description": "Users invited to the ticket."
           }

From f1a61fbeeae80128b22ba397ef778a1f33a09ea3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?=
 <felipe.garcia@datascope.io>
Date: Thu, 3 Sep 2026 12:54:06 -0400
Subject: [PATCH 3/7] fix: add a dynamic values dropdown for Change Form Status

form_state_id had no x-ms-dynamic-values, so Power Automate couldn't
offer a picker for it -- only trigger outputs and raw expression
input were available, forcing users to paste a raw state id copied
from elsewhere (e.g. Zapier's equivalent field). Adds a hidden
/list_states operation (mirrors Rails' GET /api/external/list_states,
already used by Zapier's own "form_state" hidden trigger) and wires
it as the dropdown source, matching the pattern already used for
form_id fields via Form-list.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 .../power_automate/apiDefinition.swagger.json | 42 ++++++++++++++++++-
 1 file changed, 41 insertions(+), 1 deletion(-)

diff --git a/source/power_automate/apiDefinition.swagger.json b/source/power_automate/apiDefinition.swagger.json
index 9933beefdd1..ca06a99faf3 100644
--- a/source/power_automate/apiDefinition.swagger.json
+++ b/source/power_automate/apiDefinition.swagger.json
@@ -166,6 +166,40 @@
         "x-ms-visibility": "internal"
       }
     },
+    "/list_states": {
+      "get": {
+        "responses": {
+          "200": {
+            "description": "List form statuses",
+            "schema": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "type": {
+                    "type": "string",
+                    "description": "type"
+                  },
+                  "key": {
+                    "type": "string",
+                    "description": "key"
+                  },
+                  "identifier": {
+                    "type": "string",
+                    "description": "identifier"
+                  }
+                }
+              }
+            }
+          }
+        },
+        "summary": "Get list of form statuses",
+        "description": "Retrieves the list of form statuses available in the account.",
+        "operationId": "Form-state-list",
+        "parameters": [],
+        "x-ms-visibility": "internal"
+      }
+    },
     "/hooks/power_automate/finding_created": {
       "x-ms-notification-content": {
         "description": "Details of the created ticket.",
@@ -2231,7 +2265,13 @@
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Identifier of the status to set on the form answer."
+            "description": "Identifier of the status to set on the form answer.",
+            "x-ms-summary": "Form Status",
+            "x-ms-dynamic-values": {
+              "operationId": "Form-state-list",
+              "value-path": "key",
+              "value-title": "identifier"
+            }
           }
         ],
         "responses": {

From b22aeb9f4249ae4412b5e2dd20bd8ef441c48536 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?=
 <felipe.garcia@datascope.io>
Date: Thu, 3 Sep 2026 12:59:07 -0400
Subject: [PATCH 4/7] fix: wire dynamic value dropdowns for the remaining
 action fields

form_id (Assign Task, Send Data), and type/author_email/assignees/
invitees (Create Ticket) had no x-ms-dynamic-values, same issue
already fixed for Change Form Status's form_state_id. Adds the two
missing hidden list operations (/list_users, /findings/types,
mirroring Rails' GET /api/external/list_users and
GET /api/external/findings/types, both already used by Zapier's own
hidden dynamic-field triggers) and wires all 6 remaining fields to
their respective dropdown sources.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 .../power_automate/apiDefinition.swagger.json | 112 +++++++++++++++++-
 1 file changed, 106 insertions(+), 6 deletions(-)

diff --git a/source/power_automate/apiDefinition.swagger.json b/source/power_automate/apiDefinition.swagger.json
index ca06a99faf3..e66750c5de4 100644
--- a/source/power_automate/apiDefinition.swagger.json
+++ b/source/power_automate/apiDefinition.swagger.json
@@ -200,6 +200,70 @@
         "x-ms-visibility": "internal"
       }
     },
+    "/list_users": {
+      "get": {
+        "responses": {
+          "200": {
+            "description": "List users",
+            "schema": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "type": {
+                    "type": "string",
+                    "description": "type"
+                  },
+                  "user_key": {
+                    "type": "integer",
+                    "description": "user_key"
+                  },
+                  "identifier": {
+                    "type": "string",
+                    "description": "identifier"
+                  }
+                }
+              }
+            }
+          }
+        },
+        "summary": "Get list of users",
+        "description": "Retrieves the list of users available in the account.",
+        "operationId": "User-list",
+        "parameters": [],
+        "x-ms-visibility": "internal"
+      }
+    },
+    "/findings/types": {
+      "get": {
+        "responses": {
+          "200": {
+            "description": "List ticket types",
+            "schema": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "id": {
+                    "type": "string",
+                    "description": "id"
+                  },
+                  "name": {
+                    "type": "string",
+                    "description": "name"
+                  }
+                }
+              }
+            }
+          }
+        },
+        "summary": "Get list of ticket types",
+        "description": "Retrieves the list of ticket types available in the account.",
+        "operationId": "Finding-type-list",
+        "parameters": [],
+        "x-ms-visibility": "internal"
+      }
+    },
     "/hooks/power_automate/finding_created": {
       "x-ms-notification-content": {
         "description": "Details of the created ticket.",
@@ -2094,7 +2158,13 @@
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Identifier of the form the task will be assigned on."
+            "description": "Identifier of the form the task will be assigned on.",
+            "x-ms-summary": "Form",
+            "x-ms-dynamic-values": {
+              "operationId": "Form-list",
+              "value-path": "key",
+              "value-title": "label"
+            }
           },
           {
             "name": "user_id",
@@ -2379,7 +2449,13 @@
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Identifier of the form template used to generate the new answer."
+            "description": "Identifier of the form template used to generate the new answer.",
+            "x-ms-summary": "Form",
+            "x-ms-dynamic-values": {
+              "operationId": "Form-list",
+              "value-path": "key",
+              "value-title": "label"
+            }
           },
           {
             "name": "emails",
@@ -2440,14 +2516,26 @@
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Ticket type. When set, it can fill in defaults such as priority, expiration, location, and assignees, which may override other values sent in the same request."
+            "description": "Ticket type. When set, it can fill in defaults such as priority, expiration, location, and assignees, which may override other values sent in the same request.",
+            "x-ms-summary": "Ticket Type",
+            "x-ms-dynamic-values": {
+              "operationId": "Finding-type-list",
+              "value-path": "id",
+              "value-title": "name"
+            }
           },
           {
             "name": "author_email",
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Email of the user registered as the author of the ticket. If it does not match an existing user, the ticket is created under the account associated with the token."
+            "description": "Email of the user registered as the author of the ticket. If it does not match an existing user, the ticket is created under the account associated with the token.",
+            "x-ms-summary": "Author",
+            "x-ms-dynamic-values": {
+              "operationId": "User-list",
+              "value-path": "identifier",
+              "value-title": "identifier"
+            }
           },
           {
             "name": "creation_date",
@@ -2519,7 +2607,13 @@
             },
             "collectionFormat": "csv",
             "required": false,
-            "description": "Users assigned to the ticket."
+            "description": "Users assigned to the ticket.",
+            "x-ms-summary": "Assignees",
+            "x-ms-dynamic-values": {
+              "operationId": "User-list",
+              "value-path": "user_key",
+              "value-title": "identifier"
+            }
           },
           {
             "name": "invitees",
@@ -2530,7 +2624,13 @@
             },
             "collectionFormat": "csv",
             "required": false,
-            "description": "Users invited to the ticket."
+            "description": "Users invited to the ticket.",
+            "x-ms-summary": "Invitees",
+            "x-ms-dynamic-values": {
+              "operationId": "User-list",
+              "value-path": "user_key",
+              "value-title": "identifier"
+            }
           }
         ],
         "responses": {

From e60b4ed26702518334788f0de5b96845abcfa08a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?=
 <felipe.garcia@datascope.io>
Date: Fri, 4 Sep 2026 03:02:08 -0400
Subject: [PATCH 5/7] fix: more dynamic values, drop location fields, native
 date picker on Assign Task

- Change Form Status: form_name now offers a form dropdown (Form-list,
  keyed by label since this endpoint takes a name, not an id -- unlike
  the other actions/triggers).
- Assign Task: user_id now offers a user dropdown (User-list); date
  gets format: date-time so Power Automate renders its native
  date/time picker instead of a plain text box.
- Assign Task: removed location_name, location_address, l_code,
  l_phone, l_email, c_name, c_code, latitude, longitude. These only
  existed to create a new Location on the fly, and Locations are
  being deprecated in favor of NestableLocations -- no longer worth
  exposing a path that creates new Location rows.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 .../power_automate/apiDefinition.swagger.json | 82 ++++---------------
 .../power_automate/connector_guide_en.html.md |  2 +-
 .../power_automate/connector_guide_es.html.md |  2 +-
 .../power_automate/connector_guide_pt.html.md |  2 +-
 4 files changed, 19 insertions(+), 69 deletions(-)

diff --git a/source/power_automate/apiDefinition.swagger.json b/source/power_automate/apiDefinition.swagger.json
index e66750c5de4..43edd66ea30 100644
--- a/source/power_automate/apiDefinition.swagger.json
+++ b/source/power_automate/apiDefinition.swagger.json
@@ -2147,7 +2147,7 @@
     "/assign_task": {
       "post": {
         "summary": "Assign Task (Tasks)",
-        "description": "Assigns a task on a form to a user, optionally scheduling it and linking it to a location. If a task with the same code already exists, it is updated instead of creating a new one.",
+        "description": "Assigns a task on a form to a user. If a task with the same code already exists, it is updated instead of creating a new one.",
         "operationId": "AssignTaskV2",
         "consumes": [
           "application/x-www-form-urlencoded"
@@ -2171,7 +2171,13 @@
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Email or identifier of the user the task is assigned to. If it does not match an existing user, the task may fall back to another user of the account, so use a valid, existing identifier."
+            "description": "Email or identifier of the user the task is assigned to. If it does not match an existing user, the task may fall back to another user of the account, so use a valid, existing identifier.",
+            "x-ms-summary": "User",
+            "x-ms-dynamic-values": {
+              "operationId": "User-list",
+              "value-path": "identifier",
+              "value-title": "identifier"
+            }
           },
           {
             "name": "code",
@@ -2191,6 +2197,7 @@
             "name": "date",
             "in": "query",
             "type": "string",
+            "format": "date-time",
             "required": false,
             "description": "Date and time the task is scheduled for. Defaults to the current date and time when omitted or invalid."
           },
@@ -2219,69 +2226,6 @@
             "type": "boolean",
             "required": false,
             "description": "Indicates whether the task can still be completed after its scheduled window."
-          },
-          {
-            "name": "location_name",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Name of the location linked to the task. A new location is created if it does not already exist."
-          },
-          {
-            "name": "location_address",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Address of the location linked to the task."
-          },
-          {
-            "name": "l_code",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Code used to find an existing location linked to the task."
-          },
-          {
-            "name": "l_phone",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Phone number of the location linked to the task."
-          },
-          {
-            "name": "l_email",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Email address of the location linked to the task."
-          },
-          {
-            "name": "c_name",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Name of the company linked to the location."
-          },
-          {
-            "name": "c_code",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Code of the company linked to the location."
-          },
-          {
-            "name": "latitude",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Latitude of the location linked to the task."
-          },
-          {
-            "name": "longitude",
-            "in": "query",
-            "type": "string",
-            "required": false,
-            "description": "Longitude of the location linked to the task."
           }
         ],
         "responses": {
@@ -2321,7 +2265,13 @@
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Name of the form the answer belongs to."
+            "description": "Name of the form the answer belongs to.",
+            "x-ms-summary": "Form",
+            "x-ms-dynamic-values": {
+              "operationId": "Form-list",
+              "value-path": "label",
+              "value-title": "label"
+            }
           },
           {
             "name": "form_code",
diff --git a/source/power_automate/connector_guide_en.html.md b/source/power_automate/connector_guide_en.html.md
index ff1145b57ab..24298ed511c 100644
--- a/source/power_automate/connector_guide_en.html.md
+++ b/source/power_automate/connector_guide_en.html.md
@@ -106,7 +106,7 @@ The connector also provides the following actions, so a flow can act back on Dat
 
 | Action | What it does |
 |---|---|
-| Assign Task | Assigns a task on a form to a user, optionally scheduling it and linking it to a location |
+| Assign Task | Assigns a task on a form to a user, optionally scheduling it |
 | Change Form Status | Changes the status of a form answer |
 | Modify Form Answer | Creates or updates an answer within a form response |
 | Send Data | Generates a new form answer and its PDF from an existing template |
diff --git a/source/power_automate/connector_guide_es.html.md b/source/power_automate/connector_guide_es.html.md
index 8f34c3c7bd8..dd01491b95a 100644
--- a/source/power_automate/connector_guide_es.html.md
+++ b/source/power_automate/connector_guide_es.html.md
@@ -106,7 +106,7 @@ El conector también entrega las siguientes actions, para que un flujo pueda act
 
 | Action | Qué hace |
 |---|---|
-| Assign Task | Asigna una tarea de un formulario a un usuario, opcionalmente agendándola y vinculándola a una ubicación |
+| Assign Task | Asigna una tarea de un formulario a un usuario, opcionalmente agendándola |
 | Change Form Status | Cambia el estado de una respuesta de formulario |
 | Modify Form Answer | Crea o modifica una respuesta dentro de un formulario |
 | Send Data | Genera una nueva respuesta de formulario y su PDF a partir de una plantilla existente |
diff --git a/source/power_automate/connector_guide_pt.html.md b/source/power_automate/connector_guide_pt.html.md
index 4c8a7933329..148976d2d76 100644
--- a/source/power_automate/connector_guide_pt.html.md
+++ b/source/power_automate/connector_guide_pt.html.md
@@ -107,7 +107,7 @@ O conector também oferece as seguintes actions, para que um fluxo possa agir so
 
 | Action | O que faz |
 |---|---|
-| Assign Task | Atribui uma tarefa de um formulário a um usuário, opcionalmente agendando-a e vinculando-a a um local |
+| Assign Task | Atribui uma tarefa de um formulário a um usuário, opcionalmente agendando-a |
 | Change Form Status | Muda o status de uma resposta de formulário |
 | Modify Form Answer | Cria ou modifica uma resposta dentro de um formulário |
 | Send Data | Gera uma nova resposta de formulário e seu PDF a partir de um modelo existente |

From ce679d04df83a7073bd042a431ef57edec676828 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?=
 <felipe.garcia@datascope.io>
Date: Fri, 4 Sep 2026 03:49:41 -0400
Subject: [PATCH 6/7] docs: improve field and action descriptions across the
 Power Automate connector

---
 .../power_automate/apiDefinition.swagger.json | 72 ++++++++++++-------
 1 file changed, 47 insertions(+), 25 deletions(-)

diff --git a/source/power_automate/apiDefinition.swagger.json b/source/power_automate/apiDefinition.swagger.json
index 43edd66ea30..4f87a06e07d 100644
--- a/source/power_automate/apiDefinition.swagger.json
+++ b/source/power_automate/apiDefinition.swagger.json
@@ -2184,14 +2184,16 @@
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Code that identifies the task assignment. If a task with this code already exists, it is updated instead of created."
+            "description": "Code that identifies the task assignment. If a task with this code already exists, it is updated instead of created. If omitted, a new code is generated automatically.",
+            "x-ms-summary": "Task Code"
           },
           {
             "name": "task_instruction",
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Instructions shown to the user for this task."
+            "description": "Instructions shown to the user for this task.",
+            "x-ms-summary": "Instructions"
           },
           {
             "name": "date",
@@ -2199,14 +2201,16 @@
             "type": "string",
             "format": "date-time",
             "required": false,
-            "description": "Date and time the task is scheduled for. Defaults to the current date and time when omitted or invalid."
+            "description": "Date and time the task is scheduled for. Defaults to the current date and time when omitted or invalid.",
+            "x-ms-summary": "Scheduled Date"
           },
           {
             "name": "gap",
             "in": "query",
             "type": "integer",
             "required": false,
-            "description": "Time window, in hours, around the scheduled date during which the task can be completed. Defaults to 4."
+            "description": "Time window, in hours, around the scheduled date during which the task can be completed. Defaults to 4.",
+            "x-ms-summary": "Time Window (Hours)"
           },
           {
             "name": "mandatory",
@@ -2218,14 +2222,16 @@
               "for_one",
               "for_nobody"
             ],
-            "description": "Who the task is mandatory for. Defaults to for_everyone."
+            "description": "Who the task is mandatory for. for_everyone requires every assigned user to complete it, for_nobody makes it optional for everyone, and for_one currently behaves like assigning the task to a single named user, with no additional group-completion behavior. Defaults to for_everyone.",
+            "x-ms-summary": "Mandatory"
           },
           {
             "name": "late_response_allowed",
             "in": "query",
             "type": "boolean",
             "required": false,
-            "description": "Indicates whether the task can still be completed after its scheduled window."
+            "description": "Indicates whether the task can still be completed after its scheduled window.",
+            "x-ms-summary": "Allow Late Response"
           }
         ],
         "responses": {
@@ -2278,7 +2284,8 @@
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Code of the form answer to update."
+            "description": "Code of the form answer to update.",
+            "x-ms-summary": "Form Code"
           },
           {
             "name": "form_state_id",
@@ -2331,35 +2338,40 @@
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Name or identifier of the form the answer belongs to."
+            "description": "Name or identifier of the form the answer belongs to.",
+            "x-ms-summary": "Form"
           },
           {
             "name": "form_code",
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Code of the form answer to update. The alias code is also accepted."
+            "description": "Code of the form answer to update. The alias code is also accepted.",
+            "x-ms-summary": "Form Code"
           },
           {
             "name": "question_name",
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "Name of the question to create or update."
+            "description": "Name of the question to create or update.",
+            "x-ms-summary": "Question Name"
           },
           {
             "name": "question_value",
             "in": "query",
             "type": "string",
             "required": true,
-            "description": "New value to set for the question."
+            "description": "New value to set for the question.",
+            "x-ms-summary": "Question Value"
           },
           {
             "name": "subform_index",
             "in": "query",
             "type": "integer",
             "required": false,
-            "description": "Row number of a subform table to update. When omitted, the answer at the root of the form is updated. Behavior for values other than a positive row number is not fully documented here."
+            "description": "Row number of a subform table to update, starting at 1. When omitted, the answer at the root of the form is updated. Behavior for values other than a positive row number is not fully documented here.",
+            "x-ms-summary": "Subform Row"
           }
         ],
         "responses": {
@@ -2387,7 +2399,7 @@
     },
     "/create_pdf": {
       "post": {
-        "summary": "Forms: Send Data / New Answer [Beta]",
+        "summary": "Send Data / New Answer (Forms) [Beta]",
         "description": "Generates a new form answer and its PDF from an existing form template. Any parameter besides form_id, emails, token, and action is treated as an answer to the matching question in the form, so this action supports as many additional fields as the selected form defines questions for. Not all question types are fully supported, which may result in unexpected behavior. This action does not trigger GSheet Sync, Automatic Signature, or other webhooks such as Power Automate triggers.",
         "operationId": "SendData",
         "consumes": [
@@ -2412,7 +2424,8 @@
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Email addresses that receive the generated PDF."
+            "description": "Email addresses that receive the generated PDF.",
+            "x-ms-summary": "Recipient Emails"
           }
         ],
         "responses": {
@@ -2440,8 +2453,8 @@
     },
     "/findings/create": {
       "post": {
-        "summary": "Tickets: Create Ticket",
-        "description": "Creates a new ticket. Tickets are not stored in the same database as forms and tasks, so some response fields below could not be fully verified against the underlying storage.",
+        "summary": "Create Ticket (Tickets)",
+        "description": "Creates a new ticket.",
         "operationId": "CreateFinding",
         "consumes": [
           "application/x-www-form-urlencoded"
@@ -2452,14 +2465,16 @@
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Name of the ticket."
+            "description": "Name of the ticket.",
+            "x-ms-summary": "Name"
           },
           {
             "name": "description",
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Description of the ticket."
+            "description": "Description of the ticket.",
+            "x-ms-summary": "Description"
           },
           {
             "name": "type",
@@ -2492,14 +2507,16 @@
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Date and time the ticket was created."
+            "description": "Date and time the ticket was created. Defaults to the current date and time when omitted.",
+            "x-ms-summary": "Creation Date"
           },
           {
             "name": "expiration_date",
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Date and time the ticket expires."
+            "description": "Date and time the ticket expires.",
+            "x-ms-summary": "Expiration Date"
           },
           {
             "name": "status",
@@ -2512,7 +2529,8 @@
               "paused",
               "closed"
             ],
-            "description": "Status of the ticket."
+            "description": "Status of the ticket.",
+            "x-ms-summary": "Status"
           },
           {
             "name": "priority",
@@ -2525,28 +2543,32 @@
               "high",
               "critical"
             ],
-            "description": "Priority of the ticket."
+            "description": "Priority of the ticket.",
+            "x-ms-summary": "Priority"
           },
           {
             "name": "location_id",
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Identifier of the location linked to the ticket."
+            "description": "Identifier of the location linked to the ticket.",
+            "x-ms-summary": "Location ID"
           },
           {
             "name": "location_name",
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Name of the location linked to the ticket."
+            "description": "Name of the location linked to the ticket.",
+            "x-ms-summary": "Location Name"
           },
           {
             "name": "location_type",
             "in": "query",
             "type": "string",
             "required": false,
-            "description": "Type of the location linked to the ticket."
+            "description": "Type of the location linked to the ticket.",
+            "x-ms-summary": "Location Type"
           },
           {
             "name": "assignees",

From 9b04eb9d39164910f43a0f53f546ee30c44d32f6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?=
 <felipe.garcia@datascope.io>
Date: Fri, 4 Sep 2026 03:50:41 -0400
Subject: [PATCH 7/7] docs: replace stale issue terminology with ticket in
 EN/PT connector guides

---
 source/power_automate/connector_guide_en.html.md | 10 +++++-----
 source/power_automate/connector_guide_pt.html.md | 10 +++++-----
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/source/power_automate/connector_guide_en.html.md b/source/power_automate/connector_guide_en.html.md
index 24298ed511c..29781b21cf6 100644
--- a/source/power_automate/connector_guide_en.html.md
+++ b/source/power_automate/connector_guide_en.html.md
@@ -8,7 +8,7 @@ title: Connect DataScope with Power Automate
 
 This guide explains how to enable the DataScope integration in Power Automate
 to automate your field operation: trigger flows when a form is completed,
-when a document is generated, when a task is assigned, or when an issue is
+when a document is generated, when a task is assigned, or when a ticket is
 registered.
 
 <aside class="notice">
@@ -93,8 +93,8 @@ The connector provides the following triggers:
 | New PDF | A PDF document is generated |
 | Status changed | A form answer changes status |
 | New assigned task | A task is assigned |
-| New issue | An issue is registered |
-| Issue status changed | An issue changes status |
+| New ticket | A ticket is registered |
+| Ticket status changed | A ticket changes status |
 | Completed signature | A document signature is completed |
 | Rejected signature | A signature request is rejected |
 | Updated signature | The signatures on a document are updated |
@@ -117,7 +117,7 @@ The connector also provides the following actions, so a flow can act back on Dat
 - **One active connection per form.** Triggers associated with a form support
   only one active connection at a time. If you need several flows on the
   same form, chain them from a single trigger.
-- **Issue triggers operate at the account level.** They support only one
+- **Ticket triggers operate at the account level.** They support only one
   active connection per account.
 - **Available fields vary by configuration.** Some data, such as planning
   fields or extended task fields, only appears when those features are
@@ -130,7 +130,7 @@ The connector also provides the following actions, so a flow can act back on Dat
   stop it, you also need to go to
   <a href="https://app.mydatascope.com/integrations" target="_blank" rel="noopener noreferrer">app.mydatascope.com/integrations</a>
   and delete the connection there. Every other trigger (forms, PDFs, tasks,
-  issues, signatures) does clean up automatically when the flow is turned
+  tickets, signatures) does clean up automatically when the flow is turned
   off in Power Automate.
 
 ## If something doesn't work
diff --git a/source/power_automate/connector_guide_pt.html.md b/source/power_automate/connector_guide_pt.html.md
index 148976d2d76..c1b37c89c2f 100644
--- a/source/power_automate/connector_guide_pt.html.md
+++ b/source/power_automate/connector_guide_pt.html.md
@@ -9,7 +9,7 @@ title: Conectar o DataScope com o Power Automate
 Este guia explica como habilitar a integração do DataScope no Power Automate
 para automatizar sua operação em campo: disparar fluxos quando um formulário
 é preenchido, quando um documento é gerado, quando uma tarefa é atribuída ou
-quando uma não conformidade é registrada.
+quando um ticket é registrado.
 
 <aside class="notice">
 Você pode encontrar o DataScope listado na galeria oficial de conectores do Power Automate (<a href="https://preview.flow.microsoft.com/en-us/connectors/shared_datascopeforms/datascope-forms/" target="_blank" rel="noopener noreferrer">preview.flow.microsoft.com</a>, documentado em <a href="https://learn.microsoft.com/en-us/connectors/datascopeforms/" target="_blank" rel="noopener noreferrer">learn.microsoft.com</a>). Essa versão está desatualizada, por isso este guia mostra como construir o custom connector você mesmo.
@@ -93,8 +93,8 @@ O conector oferece os seguintes disparadores:
 | Novo PDF | Um documento PDF é gerado |
 | Mudança de status | Uma resposta de formulário muda de status |
 | Nova tarefa atribuída | Uma tarefa é atribuída |
-| Nova não conformidade | Uma não conformidade é registrada |
-| Mudança de status de não conformidade | Uma não conformidade muda de status |
+| Novo ticket | Um ticket é registrado |
+| Mudança de status de ticket | Um ticket muda de status |
 | Assinatura concluída | A assinatura de um documento é concluída |
 | Assinatura rejeitada | Uma solicitação de assinatura é rejeitada |
 | Assinatura atualizada | As assinaturas de um documento são atualizadas |
@@ -119,7 +119,7 @@ O conector também oferece as seguintes actions, para que um fluxo possa agir so
   formulário admitem apenas uma conexão ativa por vez. Se precisar de vários
   fluxos sobre o mesmo formulário, encadeie-os a partir de um único
   disparador.
-- **Os disparadores de não conformidades operam no nível da conta.** Admitem
+- **Os disparadores de tickets operam no nível da conta.** Admitem
   apenas uma conexão ativa por conta.
 - **Os campos disponíveis variam conforme sua configuração.** Alguns dados,
   como os de planejamento ou os campos estendidos de tarefas, aparecem
@@ -132,7 +132,7 @@ O conector também oferece as seguintes actions, para que um fluxo possa agir so
   interrompê-lo por completo, também é necessário acessar
   <a href="https://app.mydatascope.com/integrations" target="_blank" rel="noopener noreferrer">app.mydatascope.com/integrations</a>
   e excluir a conexão correspondente ali. Os demais disparadores
-  (formulários, PDFs, tarefas, não conformidades, assinaturas) se limpam
+  (formulários, PDFs, tarefas, tickets, assinaturas) se limpam
   automaticamente ao desativar o flow no Power Automate.
 
 ## Se algo não funcionar