Inputs

Outcome: After this step, your buyer input form is defined and validated against your webhook contract.

The Inputs step defines what information buyers need to provide to run your AI Short. You'll create a dynamic form that collects exactly the data your automation needs to process.

Overview

Every AI Short needs at least one input field. The inputs you define here become the form buyers fill out when purchasing your AI Short. The data they provide is sent to your webhook for processing.

Supported input types

Text fields

• text – Single-line text input (product names, keywords, etc.)
• textarea – Multi-line text input (descriptions, content, etc.)
• url – Website URL with validation
• tags – Comma-separated keywords or categories

Numbers and dates

• number – Numeric input with optional min/max limits
• date – Single date picker
• date_range – Start and end date selection

Choices

• select – Dropdown with predefined options
• multiselect – Multiple choice selection
• boolean – Yes/No or true/false checkbox

File uploads

• file_csv – CSV files for data analysis
• file_json – JSON files for structured data
• file_xlsx – Excel files for spreadsheet data
• file_pdf – PDF documents for analysis
• file_image – Images for visual analysis
• file_docx – Word documents for content extraction
• file_txt – Plain text files

Field configuration

Key (required)

• Format: Must match ^[a-z][a-zA-Z0-9_]{1,39}$
• Rules: Start with lowercase letter, only letters/numbers/underscores, max 40 characters
• Examples: website_url, product_name, start_date
• Purpose: This becomes the property name in your webhook payload

Label and description

• Label – What buyers see as the field name
• Helper text – Additional guidance shown below the field
• Placeholder – Example text shown inside empty fields
• Required – Whether buyers must fill out this field

Validation options

• Number fields: Set min/max values and validation patterns
• Date fields: Configure date ranges and constraints
• Text fields: Pattern matching for specific formats
• Select fields: Define available options and default values

Multi-file options

For file input types, you can enable multiple file uploads:

• Multiple files – Allow buyers to upload more than one file
• Max files – Limit the number of files (e.g., 5 files maximum)
• Max bytes each – Size limit per file (e.g., 10MB per file)
• Accept formats – Automatically set based on file type selected

Mapping to webhook data

Each input key becomes a property in the JSON payload sent to your webhook. For example:

{
  "short_id": "abc123",
  "order_id": "order-uuid",
  "website_url": "https://example.com",
  "product_name": "Sample Product",
  "analysis_depth": 3,
  "include_images": true,
  "callback_url": "https://api.example.com/callback",
  "ts": 1736032405
}

Validation rules

• At least one input required – Every AI Short needs input from buyers
• Unique keys – Each input key must be different
• Valid key format – Keys must follow the regex pattern above
• Select options required – Select and multiselect fields need predefined choices
• Number range validation – Min/max values must be logical
• Multi-file safeguards – File limits must be reasonable

Examples

SEO Analysis Agent

• website_url (url, required) – "Website to analyze"
• focus_keywords (tags, optional) – "Target keywords (comma-separated)"
• include_technical (boolean, default true) – "Include technical SEO analysis"

Product Research Agent

• search_term (text, required) – "Product or keyword to research"
• platform_context (text, optional) – e.g., "Amazon", "eBay", or "Walmart" (for output tailoring only; no login)
• date_range (date_range, optional) – "Historical data period"
• max_results (number, min: 10, max: 100) – "Maximum products to analyze"

Content Audit Agent

• content_files (file_pdf, multiple, max 5 files) – "Upload documents to audit"
• audit_type (multiselect, required) – Options: Grammar, SEO, Readability, Brand Voice
• target_audience (select, optional) – Options: General, Technical, Marketing

Tips for success

• Keep inputs minimal – Only ask for what you absolutely need
• Use clear labels – Avoid technical jargon buyers won't understand
• Provide examples – Use placeholder text to show expected formats
• Set smart defaults – Pre-select common options when possible
• Group related fields – Use logical ordering in your input list
• Test your keys – Make sure they match what your automation expects

What's next?

After defining inputs, you'll move to the Output step where you specify what results buyers will receive and how your automation will deliver them.

[SCREENSHOT HERE: Inputs builder with different field types]