Task input_data formats

Every reusable task has a job_type and an input_data JSON object. At an API boundary, input_data may be carried as a serialized JSON string; the examples in this reference show the decoded object so its fields are readable.

Use the CopyHero editor for normal configuration. Use these contracts when you need to inspect or produce a supported format programmatically, and include only documented fields and values.

Public configuration types

template is the current Template task job_type. Do not substitute copy. Agent configuration has a separate Agents surface even though an agent can be used as a workflow step.

Shared rules

• input_data must decode to a JSON object, not an array or plain string.
• JSON field names and enum values are case-sensitive.
• Do not add undocumented fields based on a job payload seen in workflow history. Run-time payloads also contain system-managed context.
• Store-dependent values are resolved when the task runs and can fail when the required destination setting is unavailable.
• A configuration accepted for a future run does not change completed history.

The scrape, shopify_upsert, and shopify_publish names are system-managed workflow steps, not public task-authoring formats.

Related guides

• Understand tasks
• Build a workflow
• Manage tasks