Skip to content
Explore the preview
Browse workflow ideas

See what changed when two versions of a list do not match.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

Bring two lists of records together and compare the details for each shared item. See which entries appear only on one side, which match, and which have different values so a person can focus on the meaningful differences.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
Two lists ready to compareA pair of structured record lists with a field they have in common
“Compare the two lists using their shared identifier and group records that appear in one list only, match in both, or differ in their details.”
Work through the request.

Clear tasks, with review where it matters.

  1. Choose the two lists to compare
  2. Identify the shared record field
  3. Find records unique to either list
See all 5 tasks
A set of comparison groups that makes one-sided records, matching entries, and differing values easy to inspect.

What this workflow could do

Helps a person understand how two versions of structured information relate without reading every row in both lists side by side.

Review points proposed in this idea

The comparison depends on a reliable shared identifier and consistent field meanings. Review the match criteria and check records with missing or repeated identifiers before deciding what the differences mean.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Select the current and reference lists and make sure each represents information that can fairly be compared.

Step 1 of 5

Choose the two lists to compare

Select the current and reference lists and make sure each represents information that can fairly be compared.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    Select the lists and fields in scope

    Choose which two sets of records to compare and which details matter for this review.

  2. 02

    Choose a dependable matching field

    Use a shared identifier that distinguishes one record from another in both lists.

  3. 03

    Decide how to handle incomplete records

    Agree what should happen when an identifier or comparison value is blank, repeated, or formatted differently.

  4. 04

    Try matching and changed examples

    Check a matching pair, a value that changed, and a record appearing on only one side to confirm the groups are useful.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation