Step 1
Collect the campaign process as it runs today, the approved content and audience rules, the timing between sends, and the tools each step already connects to.
Campaign work moves between content, audience and sending steps by hand, losing context at every handoff. In this case, the immediate task is to connect marketing tasks into a coordinated workflow. The workflow should produce the step dependencies with triggers, completion checks and failure handling, verified against the campaign records.
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 connect marketing tasks into a coordinated workflow.
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: [the current campaign process, approved content and audience rules, send timing, and the tools each step already connects to]. Map the dependencies between steps so every handoff carries a trigger, a completion check that can be tested and a defined failure path, marking as manual any step whose output the merchant still has to approve before it reaches a customer.
Return a marketing workflow with handoff and failure rules 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 campaign process as it runs today, the approved content and audience rules, the timing between sends, and the tools each step already connects to.
Map the dependencies between steps so every handoff carries a trigger, a completion check that can be tested and a defined failure path, marking as manual any step whose output the merchant still has to approve before it reaches a customer.
Deliver the workflow as an ordered step list with its handoff and failure rules, then run one campaign through it end to end and confirm against the supplied records that each trigger fires and each completion check passes.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
The recurring ones with a clear trigger and a testable output, such as audience refresh, content assembly and reporting. Starting with a step whose output nobody can verify gives you automation that fails silently.
Define the fallback in advance, whether it retries, blocks the later steps or routes the failure to a named owner. A workflow without a failure path leaves a campaign half sent with no record of where it stopped.
Not for anything customer-facing. Keep a review point wherever the workflow publishes or sends on the merchant's behalf, and log who approved each send so the record shows a person was accountable.
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.