---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Runtime Phase of ETA

# Runtime Phase of the Embedded Task Automation (ETA) {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Learn more about the triggering of an attended automation from a ServiceNow form.

## Workflow of the Runtime Phase of an Embedded Task Automation {#runtime-trigger-automation-forms__section_vq2_sxq_b1c}

Familiarize yourself with Embedded Task Automation concepts. For more information, see [Embedded Task Automation (ETA) in RPA Hub](https://www.servicenow.com/docs/I0zUXsz4veyo~U40rWPMkA "With the embedded task automation feature, trigger attended bot processes (attended automations) from the ServiceNow forms, apart from initiating them from the Attended Robot application.").

A user with RPA Assisted User role logs into the ServiceNow instance.

Navigates to the corresponding ServiceNow form from where the automation must be triggered.  
The user selects the form action, that is created when you activate the attended configuration.

* If any changes are made on the ServiceNow form, a confirmation message is displayed to save before triggering the UI Action. If the user selects Proceed or OK, the form is saved. The automation is triggered. If the user selects Cancel, the automation is not triggered and the ServiceNow form is not saved.
* When the user selects the UI action, if it is successful, an attempt is made to start attended automation. Make sure that the Attended Robot is installed on the machine. If it is not successful, a connection to initiate the Attended Robot is not established. An information message is displayed to try again or contact system administrator.
{#runtime-trigger-automation-forms__ul_sht_rwq_b1c}

A URL is generated that initiates the Attended Robot with details such as OAuth Entity ID, code challenge, ServiceNow form record SysID (from where the automation is triggered), Bot Process Sys ID, and Package SysID (Automation SysID).

Using these details, the Attended Robot makes a call to the OAuth to get the access and refresh token. Learn about the authentication journey in the Attended Robot application and the automation execution. For more information, see [Attended Robot authentication journey and automation execution in Embedded Task Automation](https://www.servicenow.com/docs/pielsPkFs4VKZVSRQSCTdQ "Learn about the authentication process in the Attended Robot application and the automation execution, when the automation is triggered from ServiceNow forms.").

With these token details, the Attended Robot shares the session details with the ServiceNow form and starts executing the automation.

The GetProcessFieldParameters component makes a GraphQL API to the ServiceNow instance to read the form field values that are mapped to the dynamic process field parameters. For more information about the GetProcessFieldParameters component, see [Use the GetProcessFieldParameters component](https://www.servicenow.com/docs/I4on7M88fB0l5Gbddn9ivQ "Gets the values of the associated Table fields mapped to the process field parameter, that you had configured in an attended configuration record of a bot process. The component returns both the individual values of the parameters and all values as an object. This component reads the value of the associated Table field in the ServiceNow form record.").

After the automation is executed, the data is passed to the downstream applications.

The SetProcessFieldParameters component makes a GraphQL API to the ServiceNow instance to set the form field values that are mapped to the dynamic process field parameters. For more information about the SetProcessFieldParameters component,
see [Use the SetProcessFieldParameters component](https://www.servicenow.com/docs/CjzXuQyZuU3GKGC03USqOQ "Sets the values of the associated Table fields mapped to the process field parameter, that you had configured in an attended configuration record of a bot process. This component updates the values of the configured field parameters associated to the Table field in the ServiceNow form record.").
Figure 1. Workflow of the Runtime Phase of an Embedded Task Automation

## Launch attended automations from ServiceNow forms {#runtime-trigger-automation-forms__section_l2m_2qp_b1c}

Learn about the restrictions to launch an attended automation from ServiceNow forms and launching the attended automations. For more information, see [Attended Robot authentication journey and automation execution in Embedded Task Automation](https://www.servicenow.com/docs/pielsPkFs4VKZVSRQSCTdQ "Learn about the authentication process in the Attended Robot application and the automation execution, when the automation is triggered from ServiceNow forms.").
**Related reference**   

* [List of steps for configuring embedded task automation](https://www.servicenow.com/docs/GHOvQEOt70C1tFfPPzamrQ "Use this list of steps to guide you through all the tasks for configuring an embedded task automation.")