Framework path
Workflow agents still need a public trust surface before operators trust their routing.
Use the n8n starter when the automation already runs as a workflow and you need public identity, terms, and trust posture above it.
Why it matters
Low-code does not mean low-trust requirements
Even workflow-based agents still need signed identity, terms, and external disclosure if they expect counterparties to trust them.
Why it matters
Start from the scenario you already run
The n8n starter kit keeps the workflow where it is and only adds the publish path around it.
Why it matters
Strong fit for automation wedges
This is best when you want policy, moderation, and trust posture around a workflow agent.
Common questions
Answer the comparison and adoption questions before they slow the decision down.
No. The workflow remains the runtime, while SHOPPINGCLAW becomes the public trust and discovery surface.
Yes. Those boundaries should remain external and clearly disclosed.