Add a REST entity to a model operation

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read
  • Specify the REST entity that a Zero Copy Connector for ERP (Enterprise Resource Planning) model uses for a read, update, or create operation.

    Before you begin

    Role required: sn_erp_integration.erp_admin

    You must have already added the read, write, or create operation before you can add an entity to it. For more information, see Add an operation to a model in Zero Copy Connector for ERP.

    The REST endpoint table must be populated with any services you want to add using the AI search method.

    For an overview of the REST API connector, see Rest API for Zero Copy Connector for ERP.

    For information about the REST API connector tables added for Zero Copy Connector for ERP, see REST API connector for Zero Copy Connector for ERP tables.

    Note:
    Many REST APIs return deeply nested JSON objects. The connector supports up to three levels of nesting in response mapping. You can define nested levels for both input parameters and output fields in the Model Manager UI.

    Procedure

    1. Navigate to All > Zero Copy Connector for ERP > Zero Copy Connector for ERP Home.
    2. Open the ERP model page by selecting the models icon in the side panel.
    3. Select the model that you want to add an operation entity to.
    4. Select the Manage model button.
    5. Select an operation.
    6. Select Select entity on the Manage entities tab.
    7. In Select type, select REST.
    8. In Select service, specify the REST service to use.

      If you don't see the service you need, add the service by selecting + Add service manually. For more information, see Add a REST service manually in Zero Copy Connector for ERP.

    9. After the REST Endpoints field loads, in Select the endpoints, specify an endpoint discovered from the URL or uploaded file.
    10. After you complete the configuration, select Add entity.

      The entity card shows the date and time information was last retrieved.

    What to do next

    • Map top-level and nested JSON fields (up to three levels deep) to model fields.
    • Configure pagination parameters to control how data is retrieved in batches.
    • Define input parameters and output fields.