---
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


---

# Create a ServiceNow metadata collector

# Create a ServiceNow metadata collector {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Create a collector to import metadata from ServiceNow.

## Before you begin

Verify the following:

* All prerequisite tasks are completed. For more information, see [Prepare to run the ServiceNow collector](https://www.servicenow.com/docs/ju7v4GQo88s0dSYyhzK40g "Create a ServiceNow user and configure permissions before running the collector.").
* If you plan to run the collector on-premise, a MID Server is setup for the collector. For more information, see [MID Server for metadata collectors](https://www.servicenow.com/docs/2l_oawHD8jDgqUJN6Gaorw "When your source is behind a firewall or requires on-premises handling, deploy metadata collectors on a MID Server you host to harvest metadata from on-premises and privately networked data sources.").
* Role required: connection-admin
{#create-servicenow-metadata-collector__ul_pvj_mz5_bjc}

## Procedure

1. Navigate to AllWorkflow Data FabricWorkflow Data Fabric Home.
2. Select the Connect Hub ![Connect Hub icon]() icon in the left sidebar.
3. Select CreateMetadata collector.
4. From the System list, select ServiceNow.
5. From the Connection type list, select one of the following:
   1. Select New connection to configure a new connection.
   2. Select Existing connection to reuse an existing connection and select an existing connection from the Connections list.  
      The configuration form is filled with details from the existing connection. The name is appended with the word Copy and sensitive details like password aren't copied.
   {#create-servicenow-metadata-collector__substeps_lgh_q4y_jjc}
6. Complete the form.  
   {#create-servicenow-metadata-collector__table_axw_2j2_h3c__entry__2}

   | Field | Description |
   |-|-|
   | Connection name | Unique identifier for the connection. This field can't be modified once the connection is established. |
   | Short description | Purpose and details of the connection. |
   [Table 1. ServiceNow metadata collector form]

   {#create-servicenow-metadata-collector__table_axw_2j2_h3c}
7. Configure the connection options.  
   {#create-servicenow-metadata-collector__table_dqp_tkd_j3c__entry__2}

   | Field | Description |
   |-|-|
   | ServiceNow Instance URL | Base URL of your ServiceNow instance, such as https://your-instance.service-now.com. Do not include a trailing slash. |
   | Use MID server | Option to connect to the source system through a MID Server. When selected, the MID selection options appear. |
   | MID selection | MID Server routing option for the collector job. This field appears only when Use MID server is selected. * Auto-Select MID Server --- The system selects an available MID Server at job execution time. Default selection. * Specific MID Server --- The collector job runs on the selected MID Server. If the MID Server is offline at job execution time, the job fails with an error identifying the MID Server by name. * Specific MID Cluster --- The collector job runs on any available MID Server within the selected cluster. |
   | MID Server | MID Server to use for the collector job. This field appears only when Specific MID Server is selected. The selected MID Server is saved on the collector record and used for all subsequent collection runs until changed. |
   | MID Cluster | MID cluster to use for the collector job. This field appears only when Specific MID Cluster is selected. The selected cluster is saved on the collector record; any available MID Server within the cluster may serve the job. |
   | Capabilities | One or more capability labels that restrict auto-selection to MID Servers advertising those capabilities. This field appears only when Auto-Select MID Server is selected. |
   | MID application | MID Server application to use for the collector job. This field appears only when Auto-Select MID Server is selected. |
   [Table 2. Connection options]

   {#create-servicenow-metadata-collector__table_dqp_tkd_j3c}
8. Configure the authentication options.  
   {#create-servicenow-metadata-collector__table_epy_zqy_l3c__entry__2}

   | Field | Description |
   |-|-|
   | Username | ServiceNow username to use for authentication. |
   | Password | Password for the specified username. |
   [Table 3. Authentication options]

   {#create-servicenow-metadata-collector__table_epy_zqy_l3c}
9. Configure the advanced options.  
   {#create-servicenow-metadata-collector__entry__30}

   | Field | Description |
   |-|-|
   | ServiceNow API Page Size | Number of records to request per page from the ServiceNow Table API. Default is 1000. |
   | Skip Glide Tables, Fields, and Views | Select to skip harvesting of Glide tables, fields, and views. |
   [Table 4. Advanced options]

10. Select Save.

## Result

The metadata collector is created and appears on the Connectors page with a Configured status. It is now ready to connect to the source system and harvest metadata.

## What to do next

You can perform any of the following tasks:

* Run the collector manually to harvest metadata immediately. See [Run metadata collectors manually](https://www.servicenow.com/docs/aQKuJd5j3lCXk75ya17e~A "Execute a metadata collector on-demand to import metadata immediately.").
* Automate metadata collection by scheduling regular collector runs. See [Schedule metadata collector runs](https://www.servicenow.com/docs/asZ0rH6fgXYHaoh9wK~UWw "Schedule a metadata collector to run automatically at a specified frequency.").
* Monitor execution status and troubleshoot issues by viewing the runtime logs. See [View runtime logs for collector runs](https://www.servicenow.com/docs/k1TsyTx6kPU1XTWQB9VJdA "Access execution logs and download detailed log files for metadata collector runs.").
* Discover and evaluate the harvested data assets in the Data Catalog. See [Governing the Data Catalog](https://www.servicenow.com/docs/0K_ULy_QruQwo4Xz2_VT8w "Data stewards add business context to catalog assets, making them more discoverable for catalog consumers. Governance tools include glossary terms, tags, domains, and direct asset updates.").
* After the first collector run, serviceNow Vault data classifications can be generated automatically for ServiceNow assets using the [Classifying ServiceNow assets with Vault agents agentic workflow](https://www.servicenow.com/docs/access?context=now-assist-vault-classify-servicenow-assets&version=brazil&pubname=brazil-platform-security&ft:locale=en-US). Classifications produced by the agent are written to Vault's classification tables and are picked up by the metadata collector on its next run. Avoid running the agent and the collector at the same time to prevent a mismatch between source data and the catalog.

*[\>]: and then