@hayden_redd as Brandon mentioned, we do have a Read Incident that can be used to lookup an incident by sys_id and return fields as defined in the comma separated list. Below is an example configuration I used in one of our environments to confirm:
In this case, I was only returning
short_description; however, if multiple fields are wanted then it would be a comma separated list such as
short_description, description, sys_id, assignment_group.
If you don’t already know the sys_id of the incident, you can also use the Search Incident action which will return a list of sys ids that match the filter. Filtering can get a little tricky but all that is documented here: https://docs.servicenow.com/bundle/paris-platform-user-interface/page/use/common-ui-elements/reference/r_OpAvailableFiltersQueries.html. I used something like
short_descriptionISNOTEMPTY to return all incidents that have a short description defined.
Output of those two actions together then looks like:
If you are already trying the Read Incident action, I would check to make sure the
description is actually defined for the incident you are retrieving. When a field is defined that isn’t populated for the incident, the response should show that field as empty like below: