System-managed workflow steps
Distinguish system-managed scrape, shopify_upsert, and shopify_publish input_data from public Tasks configuration.
Some job names appear in workflow history because CopyHero uses them to load, synchronize, or publish products. They are execution details, not reusable task types that you can create on Tasks.
Do not author these as Tasks
job_type | User-visible role | How it is configured |
|---|---|---|
scrape | Loads product information from a supported source during import. | Use the product import flow. CopyHero combines the selected import options with the source and destination context. |
shopify_upsert | Creates or updates the product in the selected Shopify destination. | Use the destination and publishing controls. CopyHero supplies the required product, store, and sync context at run time. |
shopify_publish | Publishes an existing Shopify product to selected sales channels. | Use the product publishing action and select channels exposed by the connected store. |
These system-managed steps do not have a stable public blueprint input_data
format. Do not create them through a generic task or blueprint operation, copy a
job payload from history, or manually supply product identifiers, store
identifiers, access tokens, publication identifiers, callback URLs, or other
run-time values.
Configure the supported action instead
- For source links, CSV files, collections, tags, inventory choices, and product status, use Import products.
- For store-specific product state, use Publishing and sync.
- For reusable content and price transformations, create one of the documented task input data formats.
- For an error in one of these steps, inspect the run and follow Workflow failures.
Security boundary
Never place Shopify credentials, webhook secrets, signed URLs, or copied job
payloads in a task's input_data. CopyHero obtains authorized destination
context from the connected store and validates access when the action runs.