Hello ​@sarahhhh20.  One way you might be able to go about this is using the HTTP V2 integration  in your playbook.  Assuming you have a list of change identifiers (change requests), you can then pass them to an instance of the HTTP V2 integration where you would target the appropriate API on the Service-Now side.

For instance, the parameters for the integration action might be that you’re sending a “GET” request to the Service-Now endpoint https://[Instance].service-now.com/api/now/table/change_request

https://cloud.google.com/chronicle/docs/soar/marketplace-integrations/http-v2

Most customers use SNOW integration in a similar way, so for this some of our content is hard coded to very specific actions to enable a drag drop experience.  But we also include some content that is a bit more flexible,

Looking at the ServiceNow Connector it has a ‘table’ field
 

This allows you to ingest from any table, incident or other.  Obviously you will need to ensure permissions are correct etc.

Consider the rest of the workflow, if you then wish to: push comments back, change fields, sync status etc, check each workflow has Content from the marketplace that works against user defined table name (i.e. is not hard locked to ‘Incidents’ table)

Andy