AI Nodes

Text Generation

Category
AI Node
Node Type
Action Node

Overview

The Text Generation Node enables users to automatically generate text or structured data using advanced AI models. This node can be used for a wide range of purposes — such as creating summaries, generating responses, writing articles, or producing structured JSON data — without requiring any coding knowledge.

It forms a key component in workflows where natural language generation or intelligent content creation is required.

Description

Generate text or structured data using AI models.

This node uses AI models to process user instructions and produce text or JSON output. It is fully compatible with no-code workflows, meaning users can simply configure key parameters through an intuitive interface without writing scripts or API calls.

The platform provides free, in-house AI models for general and creative tasks:

  • aicon-v4-nano-160824 – for simple or lightweight tasks. Does not support file attachments.
  • aicon-v4-large-160824 – for complex text generation and file-based processing (supports file attachments).
  • aicon-v4-search-160824 – for online-based search tasks that search, analyze, and summarize in one step.

For users requiring more precision, reasoning depth, or specialized capabilities, there is an option to connect premium external models from providers like OpenAI, Anthropic, or Google. These models can be enabled from the billing page and are billed at cost. Available external models include:

Anthropic Models

  • Opus 4.1
  • Sonnet 4.5
  • Haiku-3.5

OpenAI Models

  • GPT 5
  • GPT 5 mini
  • GPT 5 nano

Google Models

  • Gemini 2.5 Pro
  • Gemini Flash Latest
  • Gemini 3 Pro

Input Parameters

The node accepts a flat list of key-value inputs. Each parameter controls specific aspects of how the AI generates content.

generationTypestringOptional
Defines which AI model to use. Choose from: aicon-v4-nano-160824 (simple tasks, no file support), aicon-v4-large-160824 (complex tasks with file attachments), aicon-v4-search-160824 (online search and analysis), or external models (Anthropic, OpenAI, Google) enabled from billing page.
Example
"aicon-v4-nano-160824"
promptstringOptional
The main instruction or query you want the AI to respond to. Also referred to as 'question'.
Example
"Write a 100-word summary about renewable energy."
trainingDatastringOptional
Helps define the AI's behavior, tone, and role, ensuring its responses are structured and aligned with the intended purpose. Also referred to as the 'system prompt'.
Example
"You are a helpful assistant that provides concise answers."
attachmentsstringOptional
Comma-separated list of file IDs that the AI can analyze or reference. Works only with aicon-v4-large-160824. Not supported by aicon-v4-nano-160824.
Example
"file-id-1,file-id-2"
randomnessnumberOptional
Controls creativity on a scale from 0 to 1. Lower values generate predictable, factual responses. Higher values produce more creative and diverse outputs.
Example
0.5
outputTypestringOptional
Defines how the output is formatted: 'text' for plain written responses, 'json' for structured, machine-readable data.
Example
"text" or "json"
thinkingstringOptional
When set to 'true', the AI performs deeper reasoning before generating results.
Example
"true"
conversationIdstringOptional
Maintains context across multiple runs, allowing the AI to remember previous interactions and produce consistent responses.
Example
"71e9512ea89b9e9f0d1d174369678b85"
jsonContentobjectOptional
Required only when outputType is 'json'. Defines the structure of the expected JSON output. Must be flat, without nested objects or arrays. Use numbered keys instead of arrays (e.g., 'item1', 'item2').
Example
{"title": "string", "summary": "string", "point1": "string"}
Instructions

Model Capabilities:

  • aicon-v4-nano-160824: Simple tasks only. Does not support file attachments.
  • aicon-v4-large-160824: Complex text generation and file-based processing. Supports file attachments via the attachments parameter.
  • aicon-v4-search-160824: Online-based search tasks. Searches the internet, analyzes results, and summarizes in one step.

External Models: Premium external models from Anthropic, OpenAI, and Google can be enabled from the billing page and are billed at cost. Once enabled, they appear in the generationType dropdown.

JSON Schema Requirements: When creating JSON schemas, always use flat structures. Avoid nested objects and arrays. Use numbered keys instead of arrays (e.g., "item1", "item2").

Access values from this node using:

{{nodeId.input.<key>}}

Example:

{{textGeneration.input.prompt}}
{{textGeneration.input.generationType}}

Output Parameters

After execution, the node returns several outputs that represent both the AI's result and processing information.

processingCountnumberOptional
Indicates the total number of tokens or data units processed by the AI model during execution.
Example
439
processingTimenumberOptional
Total time taken to generate the response, returned as a number (milliseconds).
Example
5178
processingIdstringOptional
A unique identifier automatically assigned to each generation request. Useful for debugging or tracking specific executions.
Example
"google-520649282babb51d"
conversationIdstringOptional
Identifier used to maintain continuity between multiple AI generations. When reused, it allows the AI to remember previous context and respond consistently.
Example
"71e9512ea89b9e9f0d1d174369678b85"
contentstringOptional
The main output generated by the AI. Only present when outputType is 'text'. Contains the generated text content.
Example
"AI ethics are a crucial framework..."
key1, key2, ...stringOptional
When outputType is 'json', the keys defined in jsonContent are flattened and appear directly in the output alongside processing metadata. Each key from jsonContent becomes a separate output parameter.
Example
For jsonContent {"title": "string", "summary": "string"}, outputs will be: title, summary, processingCount, processingTime, etc.
Accessing Data

For Text Output (outputType: "text"):

{{textGeneration.output.content}}
{{textGeneration.output.processingId}}
{{textGeneration.output.processingTime}}
{{textGeneration.output.processingCount}}
{{textGeneration.output.conversationId}}

For JSON Output (outputType: "json"): The JSON keys are flattened and appear directly in the output:

{{textGeneration.output.title}}
{{textGeneration.output.summary}}
{{textGeneration.output.point1}}
{{textGeneration.output.processingId}}
{{textGeneration.output.processingTime}}
{{textGeneration.output.processingCount}}
{{textGeneration.output.conversationId}}

Output Type

Output Type: text | json

The node's outputType input parameter determines how the output is structured:

  • "text" → Returns content field containing the generated text, along with processing metadata.
  • "json" → Returns flattened keys from jsonContent directly in the output (not nested under content), along with processing metadata.

For Text Output:

{{nodeId.output.content}}
{{nodeId.output.processingId}}
{{nodeId.output.processingTime}}
{{nodeId.output.processingCount}}
{{nodeId.output.conversationId}}

For JSON Output:

{{nodeId.output.<key1>}}
{{nodeId.output.<key2>}}
{{nodeId.output.processingId}}
{{nodeId.output.processingTime}}
{{nodeId.output.processingCount}}
{{nodeId.output.conversationId}}

Where <key1>, <key2>, etc. are the keys defined in your jsonContent schema.

Example Usage

Example 1: Generate Text

Goal: Write a paragraph about AI ethics.

Input Configuration:

{  "generationType": "aicon-v4-nano-160824",  "prompt": "Write a paragraph explaining the importance of AI ethics.",  "outputType": "text"}

Output Example:

{  "output": {    "content": "AI ethics are a crucial framework for navigating the complex landscape of artificial intelligence development and deployment. The six key principles outlined in this image – Transparency, Accountability, Mitigating Bias, Fairness, Security, and Privacy – collectively highlight why ethical considerations are paramount. Without transparency, it's difficult to understand how AI systems make decisions, hindering trust and accountability. Unchecked bias can lead to discriminatory and harmful outcomes, emphasizing the need for robust mitigation strategies. Fairness, while challenging to define, is essential to ensure equitable treatment for all. Robust security measures are vital to protect AI systems from malicious attacks and preserve public trust, while privacy safeguards individual autonomy regarding personal data. Adhering to these principles ensures that AI systems are developed responsibly, beneficially, and without causing undue harm, fostering public confidence and promoting a positive societal impact from this transformative technology.",    "processingTime": 5178,    "processingId": "google-520649282babb51d",    "processingCount": 439,    "conversationId": "71e9512ea89b9e9f0d1d174369678b85"  }}

Accessing Values Inside the Workflow:

{{textGeneration.output.content}}        → Generated text
{{textGeneration.output.processingTime}} → 5178
{{textGeneration.output.processingId}}   → "google-520649282babb51d"

Example 2: Generate Structured JSON

Goal: Extract key points from an article.

Input Configuration:

{  "generationType": "aicon-v4-large-160824",  "prompt": "Provide a paragraph about Healthcare 4.0.",  "outputType": "json",  "jsonContent": {    "title": "string",    "content": "string",    "summary": "string",    "point1": "string",    "point2": "string",    "point3": "string"  }}

Output Example:

{  "output": {    "title": "Healthcare 4.0: The Future of Medicine",    "content": "Healthcare 4.0 represents the transformative integration of advanced digital technologies into the healthcare ecosystem, marking a significant evolution from traditional medical practices. This paradigm leverages technologies such as Artificial Intelligence (AI), Machine Learning (ML), the Internet of Medical Things (IoMT), big data analytics, blockchain, and robotics to create a more personalized, predictive, preventive, and participatory healthcare experience. It aims to enhance operational efficiency, improve patient outcomes, reduce costs, and make healthcare more accessible and equitable globally. From precision medicine tailored to individual genetic profiles to AI-powered diagnostics and robotic surgery, Healthcare 4.0 is redefining how medical services are delivered, managed, and consumed, fostering an era of smart, connected, and data-driven healthcare solutions.",    "summary": "Healthcare 4.0 integrates advanced digital technologies like AI, IoMT, and big data into healthcare for a more personalized, predictive, and efficient system, improving patient outcomes and accessibility.",    "point1": "Utilizes AI, Machine Learning, and IoMT for enhanced diagnostics and personalized treatment plans.",    "point2": "Focuses on predictive and preventive care through data analytics, shifting from reactive to proactive healthcare.",    "point3": "Improves operational efficiency, reduces costs, and increases healthcare accessibility through digital transformation.",    "processingTime": 2414,    "processingId": "google-b3437be5929daeaa",    "processingCount": 371,    "conversationId": "b0a5d25e4b46980ed8c8d3c04e7f6bf3"  }}

Accessing Values Inside the Workflow:

{{textGeneration.output.title}}        → "Healthcare 4.0: The Future of Medicine"
{{textGeneration.output.content}}      → Full content paragraph
{{textGeneration.output.summary}}      → Summary text
{{textGeneration.output.point1}}       → First key point
{{textGeneration.output.point2}}      → Second key point
{{textGeneration.output.point3}}      → Third key point
{{textGeneration.output.processingTime}} → 2414
{{textGeneration.output.processingCount}} → 371

Note: When outputType is "json", the keys from jsonContent are flattened and appear directly in the output alongside the processing metadata. There is no content field for JSON output type.

Example 3: File-Based Processing with aicon-v4-large

Goal: Analyze a document and extract key information.

Input Configuration:

{  "generationType": "aicon-v4-large-160824",  "prompt": "Summarize the main points from the attached document.",  "attachments": "file-id-123,file-id-456",  "outputType": "text"}

Note: File attachments are only supported by aicon-v4-large-160824. The aicon-v4-nano-160824 model does not support file attachments.

Goal: Search the internet and get a summarized analysis.

Input Configuration:

{  "generationType": "aicon-v4-search-160824",  "prompt": "What are the latest developments in quantum computing? Search online and provide a summary.",  "outputType": "text"}

Note: The aicon-v4-search-160824 model performs online-based search, analysis, and summarization in one step.

How to Use in a No-Code Workflow

1

Add the Text Generation Node

Drag the Text Generation Node into your workflow builder. It can be placed anywhere after a trigger node.

2

Connect a Trigger

Link a trigger node (e.g., Email Trigger, REST API Trigger, WhatsApp Trigger) to provide input data for the AI generation.

3

Configure Inputs

Enter your prompt, choose the AI model (generationType), and select the output type (text or json).

Model Selection Guide:

  • Use aicon-v4-nano-160824 for simple text generation (no file support).
  • Use aicon-v4-large-160824 for complex tasks or when you need file attachments.
  • Use aicon-v4-search-160824 for online search and analysis tasks.
  • Select external models (if enabled) for premium capabilities.
4

Configure File Attachments (if needed)

If using aicon-v4-large-160824, you can add file IDs in the attachments field (comma-separated). Remember: aicon-v4-nano-160824 does not support file attachments.

5

Set JSON Schema (if outputType is json)

When outputType is "json", define a flat JSON structure in jsonContent. Use numbered keys instead of arrays (e.g., "item1", "item2").

6

Link Outputs

Connect this node's content output to the next step — e.g., a Text-to-Speech Node, Send Message Node, or Return State Node.

7

Run the Workflow

The node will automatically generate text or structured data as defined when the workflow is triggered.

Best Practices

  • Keep prompts specific and concise for more accurate AI results.
  • Use flat JSON structures to simplify integration with downstream nodes.
  • For complex file-based tasks, select aicon-v4-large-160824.
  • For online search and analysis, use aicon-v4-search-160824.
  • To maintain conversational context (like a chatbot), pass a consistent conversationId.
  • Use randomness between 0.2 and 0.5 for balanced creativity and coherence.
  • Enable external models from the billing page if you need premium capabilities.

Do / Don't

Do
  • ✔️ Use aicon-v4-nano-160824 for simple text generation tasks.
  • ✔️ Use aicon-v4-large-160824 when you need file attachments or complex processing.
  • ✔️ Use aicon-v4-search-160824 for online search and analysis tasks.
  • ✔️ Keep JSON schemas flat with numbered keys instead of arrays.
  • ✔️ Use consistent conversationId for maintaining context across multiple generations.
  • ✔️ Set randomness between 0.2 and 0.5 for balanced outputs.
  • ✔️ Enable external models from billing page if you need premium capabilities.
Don't
  • ❌ Don't use file attachments with aicon-v4-nano-160824 — it doesn't support them.
  • ❌ Don't use nested objects or arrays in JSON schemas — keep them flat.
  • ❌ Don't forget to set jsonContent when outputType is "json".
  • ❌ Don't use aicon-v4-search-160824 for simple text generation — use nano or large instead.
  • ❌ Don't set randomness too high (above 0.8) for factual or structured outputs.
  • ❌ Don't assume external models are available — enable them from the billing page first.

Example Workflow Integration

Use Case: Generate and send AI-generated report automatically.

  1. Trigger Node – REST API Trigger (receives input data such as topic or user query.)
  2. AI Node – Text Generation Node (creates the report based on the input.)
  3. Process Node – Return State Node (displays the generated output.)

Additional Use Cases

1. Customer Support Chatbot

A customer sends a message via WhatsApp asking about product features:

Workflow:

  1. WhatsApp Trigger – Receives customer message.
  2. Text Generation Node – Generates a helpful response using aicon-v4-nano-160824 with conversationId for context.
  3. Send Message Node – Sends the AI-generated response back to the customer.

2. Document Analysis and Summarization

A user uploads a document that needs to be analyzed:

Workflow:

  1. File Upload Trigger – Receives the document file.
  2. Text Generation Node – Uses aicon-v4-large-160824 with attachments parameter to analyze the document.
  3. Database Node – Stores the summary in a database.
  4. Return State Node – Returns the analysis results.

3. Online Research Assistant

A user requests information about a current topic:

Workflow:

  1. REST API Trigger – Receives research query.
  2. Text Generation Node – Uses aicon-v4-search-160824 to search online and provide a summary.
  3. Email Node – Sends the research results via email.

4. Structured Data Extraction

Extract structured information from unstructured text:

Workflow:

  1. Email Trigger – Receives an email with unstructured data.
  2. Text Generation Node – Uses outputType: "json" with a flat schema to extract structured data.
  3. Database Node – Stores the extracted structured data.

5. Multi-Turn Conversation Handler

Maintain context across multiple interactions:

Workflow:

  1. REST API Trigger – Receives user message and conversation ID.
  2. Text Generation Node – Uses conversationId to maintain context and generate contextual responses.
  3. Return State Node – Returns the response with the same conversationId for next interaction.

Common Errors

Missing required parameterErrorOptional
Either prompt or generationType was not provided in the input. Make sure both prompt and generationType are included before running the node.
UnauthorizedErrorOptional
Invalid or missing API credentials, or external model not enabled. Check your API key or authentication settings. For external models, ensure they are enabled from the billing page.
Invalid JSON structureErrorOptional
The provided JSON schema contains nested objects or arrays. Use a flat JSON structure with simple key-value pairs (no nesting or arrays). Use numbered keys like 'item1', 'item2' instead of arrays.
File attachments not supportedErrorOptional
File attachments were provided but the selected model (aicon-v4-nano-160824) does not support them. Use aicon-v4-large-160824 for file-based processing.
Missing jsonContentErrorOptional
outputType is set to 'json' but jsonContent parameter is missing. Provide a flat JSON schema in jsonContent when using JSON output type.
Rate limit exceededErrorOptional
Too many requests were sent in a short time period. Add a short delay between requests or retry after some time to comply with rate limits.
External model not enabledErrorOptional
An external model was selected but not enabled. Enable the model from the billing page before using it in workflows.