Template task input_data

Purpose

A Template task builds ordered product-description content from configured elements. Set job_type to template. The public type is template, not copy.

Valid JSON example

{
  "elements": [
    {
      "id": "headline-1",
      "type": "headline",
      "config": {
        "headlineType": "h2",
        "headlineStyle": "style2",
        "alignment": "left",
        "instructions": "Introduce the product's primary customer benefit.",
        "paddingTop": 0,
        "paddingBottom": 0,
        "bold": false
      }
    }
  ]
}

Top-level fields

Use the exact public element types headline, paragraph, image, benefits, custom-html, faq-section, specifications, and comparison-table. Do not use worker-normalized underscore aliases such as custom_html, faq_section, or comparison_table when authoring a task.

Shared generated-content fields

Every element except custom-html uses these fields. Include them when the assistant authors input_data; the defaults below are the run-time defaults when a field is omitted.

The editor starts new Headline, Paragraph, Image, and Benefits elements with alignment: "center"; the other generated-content elements start with alignment: "left". Use the explicit value the user wants instead of relying on that editor-only difference.

Headline

Set type to headline.

headlineStyle guides generated wording. It is not an HTML or CSS style value.

Paragraph

Set type to paragraph.

Image

Set type to image.

Sizing behavior:

• normal uses the original responsive size; keep width and height null.
• custom sets one dimension and keeps the other automatic. If both are set, width takes precedence.
• fixed uses both dimensions only when both are positive integers; otherwise rendering falls back to normal responsive sizing.

The image filtering controls apply to slideshow and productPage. An aiGenerated image requires a template selected through the editor. Never guess imageTemplateId.

Benefits

Set type to benefits.

highlight generates a short highlighted label plus a longer description for each benefit. minimal and bold generate one description per benefit. layout: "plain" omits list symbols, but symbol must still contain a valid value.

Custom HTML

Set type to custom-html. Its config contains only:

Do not add the shared fields to this element. Review the markup and never include scripts, credentials, or untrusted copied code.

FAQ section

Set type to faq-section.

boldQuestions and boldAnswers control the two generated parts separately. The shared bold field wraps the whole FAQ block, so normally leave it false.

Specifications

Set type to specifications.

bold-keyword bolds the generated specification name. plain does not. When includeEmpty is false, incomplete name/value pairs are omitted from the rendered output.

Comparison table

Set type to comparison-table.

The generated table always has three columns. Only the row count is configurable.

Defaults and omission behavior

• For assistant-authored JSON, use the complete public configuration described above. Do not depend on the editor to repair a partial payload.
• When the editor opens an older element with missing fields, it fills those fields from the new-element defaults. Invalid configuration can cause that element to reset to its complete default configuration in the editor.
• The run-time schema supplies the shared defaults and these type-specific defaults when omitted: Image sizing/filter fields; Benefits layout, customEmoji, and spacing; FAQ heading tags, bold controls, and spacing; Specifications layout and spacing.
• All other type-specific fields marked Yes are required for execution.
• Element order in the array is output order. Following workflow steps receive the resulting product state.

UI guides

Use Create a Template task and Use image templates in content blocks for the corresponding editor controls.