Verify a weekly intake count
Prepare a reviewed count of incoming records for a team report.
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.
Take the complete set of records returned by an earlier stage and calculate how many it contains. Keep the result alongside the source context so a person can confirm that the expected records were included before the count informs a report or downstream decision.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Count all records in the selected result set and return the count with enough context for a person to verify its scope.”
Clear tasks, with review where it matters.
Helps a team check the size of a returned result set without counting each record by hand.
A count does not confirm that the right records were selected or that the source data is complete. Check the upstream filters, time period, and expected total; verify the count before relying on external data or including it in a public report.
Select an illustrative task to explore its proposed role. No workflow runs here.
Choose the records from the intended processing step and confirm the run or source they belong to.
Calculate the number of returned records once, including a clear zero when the selected set is empty.
Retain the source, selection criteria, and run reference so a reviewer can tell exactly what was counted.
Compare the count with the selected filters, expected volume, and any known omissions or duplicate records.
Have a person verify the scope and count before it is used in a public report, shared externally, or used to trigger a consequential action.
Choose the records from the intended processing step and confirm the run or source they belong to.
These are planning notes for the concept, not instructions for a currently available template.
Specify which returned records are counted and which run, filter, or time period defines the set.
Decide how an empty result is shown and whether duplicates are counted as returned or removed beforehand.
Choose where the count appears, include its source context, and name who verifies it before use.
Compare the count with a known set in each case and confirm the result does not lose its source context.
Published templates and verified customer availability remain pending.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation