Runtime Phase of the Embedded Task Automation (ETA)

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Runtime Phase of the Embedded Task Automation (ETA)

    The Runtime Phase of the Embedded Task Automation (ETA) facilitates the triggering of attended automations directly from ServiceNow forms. Users with the RPA Assisted User role initiate this process by accessing the relevant form in the ServiceNow instance.

    Show full answer Show less

    Key Features

    • Users select a form action to activate the attended automation.
    • Confirmation prompts ensure any unsaved changes to the form are addressed before automation is triggered.
    • Successful UI action attempts start the attended automation, provided the Attended Robot is installed.
    • Automation leverages OAuth for authentication, generating a URL with essential parameters for the Attended Robot.
    • The GetProcessFieldParameters component retrieves mapped form field values via a GraphQL API call.
    • The SetProcessFieldParameters component updates form fields post-automation execution using GraphQL API.

    Key Outcomes

    Upon successful execution of the automation, data is transferred to downstream applications, facilitating seamless integration and process efficiency. This functionality enables ServiceNow customers to enhance their workflows by automating repetitive tasks directly from their forms, resulting in improved productivity and reduced manual intervention.

    Learn more about the triggering of an attended automation from a ServiceNow form.

    Workflow of the Runtime Phase of an Embedded Task Automation

    Familiarize yourself with Embedded Task Automation concepts. For more information, see Embedded Task Automation (ETA) in RPA Hub.

    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.

    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.

    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.

    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.

    Figure 1. Workflow of the Runtime Phase of an Embedded Task Automation
    Workflow of the Runtime Phase of an Embedded Task Automation.

    Launch attended automations from ServiceNow forms

    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.