Output

Outcome: After this step, buyers will see exactly what they receive and when, with formats and ETA communicated clearly.

The Output step defines what buyers receive after running your AI Tool and how long the processing takes. This includes the format of results, processing time estimates, and examples to set proper expectations.

Overview

Buyers need to know what they'll get and when they'll get it. This step helps you communicate the value and timeline of your AI Tool clearly.

Required fields

Full Description

• Purpose: Detailed explanation of what your AI Tool does and delivers
• Content: Expand on the short pitch from the Basics step
• Tips: Include specific outcomes, data points, or insights buyers will receive

Use Cases (up to 8)

• Format: Bullet points of specific scenarios
• Examples: "Audit your product listings for SEO issues (manual updates)", "Analyze competitor pricing strategies"
• Purpose: Help buyers understand when and why to use your AI Tool

Output types

Text and structured data

• text – Plain text reports, summaries, recommendations
• json – Structured data for further processing
• csv – Tabular data for analysis in spreadsheets
• url – Link to hosted content (recommended for HTML files)

Files and documents

• file – PDF, images (JPG/PNG/WebP), documents (DOCX), text (TXT), archives (ZIP), data (JSON), spreadsheets (CSV/XLSX)
• xlsx – Excel spreadsheets with formatted data
• url – Link to hosted results or external resources
• video – Video file output (MP4, MOV, WebM, AVI) for product demos, video ads, social media content, or tutorial videos

Processing mode

Async processing (required)

All AI Tools use asynchronous processing, meaning your automation runs in the background and sends results via callback when complete.

ETA buckets

Choose the timeframe that best matches your automation's typical processing time:

• Under ~2 minutes – Simple analysis, quick API calls
• Under 1 hour – Moderate to complex analysis, data collection, multiple data sources
• Within 24 hours – Comprehensive research, extensive processing, deep analysis

Optional configuration

JSON Schema

• When to use: For JSON output types when you want to validate structure
• Purpose: Ensures your output matches expected format
• Example: Schema for SEO audit results with specific fields

Output Examples (up to 2)

• Purpose: Show buyers exactly what they'll receive
• Format: Sample text, data snippets, or descriptions
• Tips: Use realistic examples that demonstrate value

Output format examples

Text report example

SEO Audit Results for example.com

CRITICAL ISSUES (3 found)
• Missing meta description on 5 pages
• Page speed score below 50 on mobile
• 12 broken internal links detected

RECOMMENDATIONS
1. Add unique meta descriptions to boost click-through rates
2. Optimize images - average size is 2.3MB per image
3. Fix internal links to improve user experience

TECHNICAL SCORE: 65/100
Overall SEO health is moderate with room for improvement.

JSON data example

{
  "audit_summary": {
    "overall_score": 65,
    "critical_issues": 3,
    "warnings": 8,
    "suggestions": 12
  },
  "issues": [
    {
      "type": "critical",
      "category": "meta_tags",
      "description": "Missing meta description",
      "pages_affected": 5,
      "impact": "high"
    }
  ],
  "recommendations": [
    {
      "priority": "high",
      "action": "Add meta descriptions",
      "estimated_impact": "10-15% increase in CTR"
    }
  ]
}

CSV data example

Page,Issue Type,Priority,Description,Fix Suggested
/home,Meta Tags,High,Missing description,Add 155-char description
/products,Performance,Medium,Slow load time,Compress images
/about,Links,Low,Broken external link,Update or remove link

Best practices

• Choose realistic ETAs – Better to under-promise and over-deliver
• Provide clear examples – Show actual output format and content structure
• Match output to use case – CSV for data analysis, URL for hosted reports (including HTML), JSON for developers
• Include actionable insights – Don't just provide data, provide recommendations
• Test your callback – Ensure you can deliver the promised output format

Common output patterns

Analysis agents

• Format: URL (for hosted reports) or text
• Content: Scores, issues found, recommendations
• ETA: Under ~2 minutes to under 1 hour for most analyses

Research agents

• Format: CSV or Excel files
• Content: Data tables, product lists, competitor info
• ETA: Under 1 hour to within 24 hours depending on data volume

Content generators

• Format: Text or URL (for formatted content)
• Content: Generated copy, headlines, descriptions
• ETA: Under ~2 minutes for AI-generated content

What's next?

After defining your output format, you'll move to the Connect step where you link your automation by configuring webhook settings and authentication.