--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Test model inputs and outputs # Use ERP Data action details for flows {#ariaid-title1} Release version: Australia Updated August 6, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Use ERP Data action details for flows TheUse ERP Dataaction in Workflow Studio allows ServiceNow customers to test and incorporate ERP data into their flows after creating and managing models in the Zero Copy Connector for ERP. This enables integration of ERP system read or update operations directly into ServiceNow AI Platform workflows, facilitating seamless data interaction between ERP systems and ServiceNow applications. Show full answer Show less ## Roles and Availability This action is available as part of the Zero Copy Connector for ERP. Users must have appropriate roles granted by delegated development or assigned directly to access and use this action within Workflow Studio. Proper role assignment ensures secure and authorized use of ERP data operations. ## Inputs To configure the **Use ERP Data** action, customers provide: * **ModelName**: Select the ERP model containing the defined read or update operation, previously created in Zero Copy Connector for ERP. * **ModelOperation**: Choose whether to perform a Read or Update operation on the ERP system, with entities defined in the ERP model. * **Required Fields**: Input parameters marked as required for the operation, defined in the ERP model management. * **Optional Fields**: Input parameters marked as optional for the operation, also managed within the ERP model. * **System**: Reference the connected ERP system to target for the operation. Dynamic values can be assigned using the pill picker for flexible input mapping in flows. ## Outputs The action provides several outputs that can be utilized in subsequent flow steps: * **Action status**: Contains runtime details with a status code and message indicating the outcome of the action. * **Don't Treat As Error**: A true/false flag to specify if the action status should be reported as an error or success within the flow. * **Error Message**: Contains any error message generated by the action or system operation. * **Response**: Returns the requested ERP data as a dynamic object, based on the selected output parameters from the ERP model. ## Practical Use for ServiceNow Customers By leveraging the **Use ERP Data** action, customers can efficiently integrate ERP data retrieval and updates into their ServiceNow workflows. This capability streamlines business processes by enabling real-time ERP data access within ServiceNow's AI Platform, ensuring data consistency and improving automation across enterprise systems. After you're done creating and managing your model in Zero Copy Connector for ERP, go to Workflow Studio and use the Use ERP Data action to test your model's inputs and outputs. You can then build a flow with the action to incorporate ERP data into the ServiceNow AI Platform. For information on using the Use ERP Data action to retrieve ERP data, see [Building flows with the Zero Copy Connector for ERP Use ERP Data action](https://www.servicenow.com/docs/AU_j28QqSnC~eb2MiJ01Sg "Use the Use ERP Data action in Workflow Studio to build flows that read or update ERP data through a Zero Copy Connector for ERP model. Filter each request with input parameters such as an order ID."). ## Roles and availability {#erp-canvas-flow-reference-2__section-subscription-roles} Available as part of Zero Copy Connector for ERP. Role requirements{#erp-canvas-flow-reference-2__action-fd-roles} : This action requires roles granted by delegated development or assigned to the user. For more information, see [User access to Workflow Studio flows](https://www.servicenow.com/docs/access?context=user-access-flow-designer&version=australia&pubname=australia-build-workflows&ft:locale=en-US). ## Inputs {#erp-canvas-flow-reference-2__section-inputs} Provide a value for each input that your action requires. To add dynamic values, you can also select data pills using the pill picker.{#erp-canvas-flow-reference-2__inputs-description} ModelName : Data type: Dynamic Choice Name of the ERP model that contains the read or update operation. The model must already be created and have the read or update operation defined in Zero Copy Connector for ERP. For more information, see [Exploring Zero Copy Connector for ERP models](https://www.servicenow.com/docs/NU6zdbRB2GhdDzp4xca4FA "Build ERP (Enterprise Resource Planning) models in Zero Copy Connector for ERP to create read, update, and create operations and organize mirrored ERP data."). ModelOperation : Data type: Dynamic Choice Whether to Read or Update the ERP system. The read or update entity must already be defined in Zero Copy Connector for ERP. For more information, see [Adding an entity to a Zero Copy Connector for ERP model](https://www.servicenow.com/docs/K5R6O9qTuWaixyfpMQc1Tw "Add an entity to a model operation to specify the ERP data that Zero Copy Connector for ERP reads, creates, or updates when the model runs."). Required Fields : Data type: Dynamic Template Fields that are required for the operation. Fields must already be defined as required input parameters when you manage the model in Zero Copy Connector for ERP. For more information, see [Manage input parameters for a model operation](https://www.servicenow.com/docs/TWk~G71cedaW02LGqN5Sxw "Specify how fields on the ERP (Enterprise Resource Planning) system map to input parameters and their values. Mapping defines the inputs for an operation that reads, creates, or updates the ERP system from Zero Copy Connector for ERP."). Optional Fields : Data type: Dynamic Template Fields that are optional for the operation. Fields must already be defined as optional input parameters when you manage the model. For more information, see [Manage input parameters for a model operation](https://www.servicenow.com/docs/TWk~G71cedaW02LGqN5Sxw "Specify how fields on the ERP (Enterprise Resource Planning) system map to input parameters and their values. Mapping defines the inputs for an operation that reads, creates, or updates the ERP system from Zero Copy Connector for ERP."). System : Data type: Reference Name of the connected ERP system. For more information, see [Working with ERP systems in Zero Copy Connector for ERP](https://www.servicenow.com/docs/k76DJtiZsS5RENtOS3_03g "A Zero Copy Connector for ERP (Enterprise Resource Planning) system represents a connection to a section of your ERP system, such as sales orders or vendor invoices."). ## Outputs {#erp-canvas-flow-reference-2__section-outputs} You can use these outputs as inputs for other items.{#erp-canvas-flow-reference-2__outputs-description} Action status : Data type: Object Data pill that contains the current runtime details about the action. The Action Status object consists of a code and a message. Don't Treat As Error : Data type: True/False Option to report the Action Status as an error or a success when returned to a flow. Error Message : Data type: String String data pill containing the error message produced by the action, step, or system operation. Response : Data type: Dynamic Object Requested data that's returned from the ERP system. For more information, see [Choose output parameters for a model](https://www.servicenow.com/docs/q9nzhgMSleqKmiqeQ7zH2w "Specify output parameters for a model operation in Zero Copy Connector for ERP to define which ERP fields map to the ServiceNow AI Platform and how the returned data is stored.").