When building automated workflows, structure matters.
Any response you generate, especially from AI models, needs to follow a predictable format so it can be:
- Referenced by later steps
- Used in conditions or classifications
- Pushed reliably to CRMs, grids, or integrations
- Change response formats
- Add extra text
- Reorder information
- Hallucinate structure even with strict prompts
Why Output Formatting Is Important
Without structured outputs:- Workflows break unpredictably
- Downstream enrichments fail
- CRM pushes become unreliable
- Automation becomes fragile
- Every run produces the same schema
- Columns are always consistent
- AI results can safely drive logic and actions
Where Output Formatting Is Available
Output formatting is available on:- Bit Agent
- GPT / Claude / AI enrichments
- Any text-based AI step
Fields vs Lists
Bitscale supports two output types:Fields
- Used for single values or comma-separated values
- Best for:
- Industry
- ICP classification
- Boolean flags
- Short summaries
Lists
- Used for multiple structured entries
- Each item is treated as a separate entity
- Best for:
- Event attendees
- Customers
- Technologies
- People lists
- Anything you may want to explode into rows later
Manually Defining Output Formats
You can manually define:- Field name
- Data type (text, boolean, number, etc.)
- Output structure
Using “Generate with AI” (Recommended)
For most users, the easiest and safest approach is Use AI.How it works
- Bitscale reads your prompt
- Understands the intent
- Automatically generates the correct output schema
Example
Prompt:Go through @company_website and find their target demography and customersClick Use AI, and Bitscale generates:
- Target Demography
- Industry
- Customers
Running and Storing Structured Outputs
Once the enrichment runs:- The AI response is forced into the defined structure
- Each output field becomes a reusable column
- These columns can now be:
- Referenced in later prompts
- Used in run conditions
- Exported to CRMs
- Passed to other grids or integrations
Best Practices
- Always use output formatting for AI-driven workflows
- Use Fields unless you explicitly need row-level expansion
- Prefer Use AI unless you have very strict schema requirements
- Treat structured outputs as foundational workflow primitives