The Scenario
The change manager is staring at a Google Sheet left by the person who left the company last Friday. Column A has 40 change request sys_ids. Column B has implementation task descriptions. Column C has the assigned group for each task. The change tasks need to exist in ServiceNow under their respective change requests before the CAB review tomorrow morning — one implementation task per row.
The bad version:
- Open ServiceNow, search for the first change request by sys_id, navigate to the Tasks tab, click New, select Implementation, fill in the description and assigned group, save.
- Repeat 39 more times with a sheet open in the other tab so you can keep track of which change you are on.
- Come back the next morning to discover that three of the change sys_ids in the sheet were for changes that were already closed, and those tasks need to be created against a different change.
Creating 40 tasks by hand is not change management. It is data entry. The person who left did not finish the job, and now the timeline is yours to solve.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the change sys_ids, task descriptions, and assigned groups, and creates one implementation task per row under the correct change request in ServiceNow.
For each row in this sheet, create a change task in ServiceNow under the change request sys_id in column A, using the description in column B and the assigned group in column C, then write the task number into column D
What You Get
- One ServiceNow change task created per row, attached to the correct change request
- The returned task number written into column D for each row
- Rows where the change sys_id is invalid or the change is closed flagged in column D with the error reason
- The full batch submitted in one operation
What If the Data Is Not Quite Ready
Some change sys_ids in column A point to changes that are already closed or cancelled
Creating tasks against closed changes will fail. You need to identify those before submitting.
For each change sys_id in column A, check if the change is still active in ServiceNow — if it is, create an implementation task using the description in column B and assigned group in column C and write the task number into column D; if the change is closed or cancelled, write "CHANGE CLOSED — SKIP" into column D
The task type needs to be set from column B — some are test tasks, some are implementation tasks
The brief has mixed task types, not just implementation.
For each row, create a change task in ServiceNow under the sys_id in column A, setting the task type from column B (implementation or test), the description from column C, and the assigned group from column D, then write the task number into column E
The assigned group names in column C are display names, not sys_ids
ServiceNow's change task API requires sys_ids for the assignment group.
For each row, look up the group sys_id in ServiceNow by the name in column C, then create a change task under the change request in column A using the description in column B and the resolved group sys_id, writing the task number into column D and the group sys_id used into column E
Full kill chain: validate changes, resolve groups, create tasks, and flag exceptions
For each row, verify the change request sys_id in column A is active in ServiceNow, look up the assignment group sys_id from the name in column C, create an implementation task with the description from column B and resolved group sys_id, write the task number into column D, and write any errors — closed change, invalid group, API failure — into column E
One prompt validates, resolves, creates, and audits the full batch.
Try It
Get the 7-day free trial of SheetXAI and open the Google Sheet with the change sys_id list, then ask it to create all 40 tasks in ServiceNow before the CAB review. For pulling change request data, see the export-change-requests spoke or return to the ServiceNow hub.