The Scenario
An insurance dispute arrived Monday morning. The claims adjuster is asking for documentation of every touchpoint your company had with 15 specific job contacts over the past six months. That history is in JobNimbus. You need it in an Excel workbook, timestamped, by end of day.
The bad version:
- Open the first contact in JobNimbus. Scroll through the activity feed. Copy each event — the date, the type, the note — and paste it into the workbook.
- Move to the second contact. Scroll. Copy. Paste.
- After the third contact you realize the activity feed doesn't show a created date for every event type. Some activities only show relative time. You start estimating.
This is compliance documentation for a legal dispute. Estimated dates are not documentation.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Excel workbook. It connects to the JobNimbus activity log, filters to the contacts you need, and writes the timestamped history into your workbook.
Pull the complete JobNimbus activity log and write it into my Excel sheet with columns: activity date, related contact ID, action type, and note text.
What You Get
- Every activity record for the contacts in your list, pulled from the JobNimbus activity log.
- Activity date, related contact ID, action type, and note text across four columns.
- Timestamped data from the source system — not reconstructed from memory or relative time labels.
- One row per activity event. Multiple events per contact each get their own row.
What If the Data Is Not Quite Ready
You need activities filtered to a specific date range
The dispute covers the period from December 1, 2025 through March 31, 2026. Activities outside that window aren't relevant.
Pull the JobNimbus activity log for the contact IDs listed in column A of my Excel workbook. Filter to activities where the activity date is between 2025-12-01 and 2026-03-31. Write activity date, contact ID, action type, and note text into columns A through D.
Activity type codes come back as internal identifiers, not readable labels
The API returns type codes like NOTE, CALL, STATUS_CHANGE instead of human-readable labels. The adjuster needs readable text.
Pull JobNimbus activities for the contact IDs in column A of my workbook. When writing the activity type, convert the type code to a readable label: NOTE to Note Added, CALL to Phone Call, STATUS_CHANGE to Status Changed, and any unrecognized code to Other. Write date, readable type, and note text across columns B through D.
Some contacts have no activity in the relevant period
A contact on your list may have had zero activity during the dispute window. You need to flag that explicitly rather than leaving a gap that looks like a data error.
Pull JobNimbus activities for the contact IDs in column A of my workbook, filtered to between 2025-12-01 and 2026-03-31. For any contact ID that has no activity in that range, write a row with the contact ID and No activity in period in the note column. For all others, write the date, contact ID, type, and note.
You need a contact-by-contact summary above the full detail log
The adjuster wants a one-line summary per contact before the raw event log.
Pull JobNimbus activities for the contact IDs in column A of my workbook. Above the detail log starting at row 2, write a summary with one row per contact showing the contact ID, total activity count, date of first activity, and date of last activity. Then write the full detail log below the summary.
Summary and detail delivered together.
Try It
Get the 7-day free trial of SheetXAI and open the Excel workbook where you've listed the contact IDs in question, then ask it to pull the full JobNimbus activity log for those contacts — timestamped and ready for the adjuster. See also how to export payments for revenue reconciliation or the JobNimbus overview for Excel.