---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Non-Interactive activities

# Non-Interactive activities {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
A non-interactive activity runs entirely behind-the-scenes on the ServiceNow AI Platform® and doesn't require any user input.

A non-interactive activity is an entirely automated operation on the ServiceNow AI Platform which doesn't require any user input to proceed to completion. Non-interactive activities still render in a playbook, but only display information to agents. Configure the activity inputs for an
interactive activity so that the activity is a fully automated operation on the ServiceNow AI Platform.

When non-interactive activities run, they automatically proceed to completion or are skipped. For example, if your activity automatically updates the Assigned To user for a record, the Playbook card can display the newly updated
Assigned To user's name to the playbook agent, but the card's status is automatically set to Complete.  
Figure 1. Non-interactive activities

Non-interactive activities turn into activity cards that are collapsed and marked complete in a playbook. The playbook continues running without any input from the playbook agent.

To learn how to design a playbook with non-interactive activities, see [design an automated process](https://servicenow-prod.fluidtopics.net/OynyzdxYrLI2quKA_FNsJg "Create a sample playbook to standardize and automate how Service Desk agents handle chat interactions with VIP users.").
* **[Automated Create Record activity](https://servicenow-prod.fluidtopics.net/TX2x8ZDvLEuWIQfS4TmRZw)**   
  Create a record without pausing the playbook to ask for user input. When the activity runs, it immediately creates the record and continues to the next activity in the playbook. The record must meet server-side validation rules such as data policies, business rules and dictionary-defined mandatory fields but ignores UI policies.
* **[Automated Send Email activity](https://servicenow-prod.fluidtopics.net/Z~FhKdRkyfKH97LutQeuaA)**   
  Create an email from previously gathered or generated data without pausing the playbook to ask for user input. When the activity runs, it immediately sends the email and continues to the next activity in the playbook.
* **[Automated Update Record activity](https://servicenow-prod.fluidtopics.net/pu7EA7iSYBA9mpihGtkfMg)**   
  Update a record without pausing the playbook to ask for user input. When the activity runs, it immediately updates the record and continues to the next activity in the playbook. The record must meet server-side validation rules such as data policies, business rules and dictionary-defined mandatory fields but ignores UI policies.
* **[Autocompleting User Form](https://servicenow-prod.fluidtopics.net/BVD6ju0mb214LyrdD7uwxw)**   
  Display a form during runtime to collect input values for your playbook.
* **[Look Up Records activity](https://servicenow-prod.fluidtopics.net/_2N4jDRINcrUkoFvnWOf3A)**   
  Find system records that match a set of conditions.
* **[Make a Decision-First Match activity](https://servicenow-prod.fluidtopics.net/LoabMEq_EKIJx3JBqHL9QQ)**   
  Execute rules in a decision table. When this activity runs, it will immediately finish and continue the process execution. The activity returns the result of the first matching decision rule, based on the rank of the rules. To return results from all matching rules, add the decision table to a subflow.