Data is pulled by hand whenever a report is due, and nobody can tell whether the result covers the whole period. In this case, the immediate task is to collect recurring store and platform data reliably. The workflow should produce an automation specification and sample report structure stating freshness and record-count checks.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me collect recurring store and platform data reliably.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [source definitions with granted access scopes, required fields and expected types, the extraction window for each run, and the merchant's stated validation expectations for freshness and record count]. Sequence extraction so each source is pulled for its stated window and validated on field completeness, record count and date coverage before it is stored, rejecting a run that falls short and keeping the previous complete collection rather than passing a partial result downstream as finished.
Return an automation specification and sample report structure with freshness and record-count checks stated for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect the source definitions with the granted access scopes, the required fields and their expected types, the extraction window for each run, and the validation expectations the merchant states, including freshness and record-count rules.
Sequence extraction so each source is pulled for its stated window and validated on field completeness, record count and date coverage before it is stored, rejecting a run that falls short and keeping the previous complete collection rather than passing a partial result downstream as finished.
Deliver the automation specification and sample report structure with freshness and record-count checks stated, then verify by running the sequence against the supplied records, confirming each stored collection carries its source, window, record count and outcome and that rejected runs are logged with the reason.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
An invalid row reaches every later report built on the collection, and repairing history costs far more than rejecting a run. Checking field completeness, record count and date coverage at extraction keeps one bad pull from becoming a quiet correction months later.
The run is rejected and the previous complete collection stays in place, with the gap flagged in the run log. A partial collection looks like a real decline in any report, so it must never be stored or marked complete.
The source, the window requested, start and end time, record count, validation outcome and the rejection reason where one applied. Those fields let a later gap be traced to a specific run without re-reading the whole pipeline.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.