> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langdock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Field Modes

> Configure node fields with Auto, Manual, and AI Prompt modes.

<img src="https://mintcdn.com/langdock-34/cWyoB3RsITQmAUnM/images/workflows/modes.jpg?fit=max&auto=format&n=cWyoB3RsITQmAUnM&q=85&s=9d367c3b96e7a842c984451186cd8f32" alt="Field Modes" width="1920" height="903" data-path="images/workflows/modes.jpg" />

## Overview

Every node field can be configured in one of three modes. Choose based on whether you need AI intelligence, exact control, or quick setup.

## The Three Modes

### Manual Mode

You specify the exact value—static text, variables, or a combination.

<img src="https://mintcdn.com/langdock-34/cWyoB3RsITQmAUnM/images/workflows/screenshots/FieldConfigManual.png?fit=max&auto=format&n=cWyoB3RsITQmAUnM&q=85&s=3a74f334e56b0743544255c75c97e6c0" alt="Manual Mode" width="3840" height="2160" data-path="images/workflows/screenshots/FieldConfigManual.png" />

**Use when:** You know exactly what value you need.

```handlebars theme={null}
Field: "Recipient Email"
Mode: Manual
Value: "{{trigger.output.email}}"
→ Directly uses the email from your form
```

<Note>
  No AI credits. Fastest and most predictable. Use this whenever possible.
</Note>

***

### AI Prompt Mode

Give natural language instructions for AI to generate content.

<img src="https://mintcdn.com/langdock-34/cWyoB3RsITQmAUnM/images/workflows/screenshots/FieldConfigPrompt.png?fit=max&auto=format&n=cWyoB3RsITQmAUnM&q=85&s=ce1ba6a2cba18a3893fd45ad8db5f75e" alt="AI Prompt Mode" width="3840" height="2160" data-path="images/workflows/screenshots/FieldConfigPrompt.png" />

**Use when:** You need AI to write, summarize, or transform content.

```text theme={null}
Field: "Email Body"
Mode: AI Prompt
Instructions: "Write a friendly response to {{trigger.output.message}},
addressing their concern about {{agent.output.structured.issue_category}}."
→ Personalized email generated each time
```

<Note>
  Uses AI credits. Output varies between executions based on context.
</Note>

***

### Auto Mode

AI analyzes context from previous nodes and determines the value automatically.

<img src="https://mintcdn.com/langdock-34/cWyoB3RsITQmAUnM/images/workflows/screenshots/FieldConfigManual.png?fit=max&auto=format&n=cWyoB3RsITQmAUnM&q=85&s=3a74f334e56b0743544255c75c97e6c0" alt="Auto Mode" width="3840" height="2160" data-path="images/workflows/screenshots/FieldConfigManual.png" />

**Use when:** You're prototyping or the data structure varies between runs.

```text theme={null}
Field: "Ticket Priority"
Mode: Auto
→ AI looks at message content and sets priority based on urgency signals
```

<Note>
  Uses AI credits. Convenient for quick setup, but less predictable than Manual.
</Note>

***

## Quick Comparison

| Mode      | AI Credits | Control | Best For                           |
| --------- | ---------- | ------- | ---------------------------------- |
| Manual    | No         | High    | Direct values, templates (default) |
| AI Prompt | Yes        | Medium  | Content generation, summarization  |
| Auto      | Yes        | Low     | Prototyping, variable structures   |

<Note>
  Recipient fields such as To, Cc, and Bcc are never filled by AI by default, to protect against prompt injection. If you switch them to Auto or AI Prompt, the editor shows a security warning. See the [Action node](/en/using-langdock/workflows/nodes/action-node) page for details.
</Note>

## Variable Syntax

Both Manual and AI Prompt modes support variables:

```handlebars theme={null}
{{node_name.output.field_name}}
{{node_name.output.nested.field}}
{{node_name.output.array[0].property}}
```

**Examples:**

```handlebars theme={null}
{{trigger.output.email}}              // Form field
{{agent.output.summary}}              // Agent output
{{http_request.output.data.userId}}   // API response
{{my_loop.output.currentItem.name}}   // Current loop item
```

<Tip>
  Type `{{` in any field to see available variables from previous nodes.
</Tip>

## Real-World Examples

### Customer Support

```text theme={null}
Trigger: Form submission

Action: Send email
├─ To: Manual → "{{trigger.output.email}}"
├─ From: Manual → "support@company.com"
├─ Subject: Manual → "Re: {{trigger.output.subject}}"
└─ Body: AI Prompt → "Write a helpful response to: {{trigger.output.message}}"
```

### Data Processing

```text theme={null}
Trigger: New spreadsheet row

Action: Create CRM record
├─ Name: Manual → "{{trigger.output.customer_name}}"
├─ Email: Manual → "{{trigger.output.email}}"
├─ Notes: AI Prompt → "Summarize this feedback: {{trigger.output.feedback}}"
└─ Status: Manual → "New Lead"
```

## Next Steps

<CardGroup cols={2}>
  <Card title="Variable Usage" icon="code" href="/en/using-langdock/workflows/fundamentals/variable-usage">
    Deep dive into workflow variables
  </Card>

  <Card title="Agent Node" icon="brain" href="/en/using-langdock/workflows/nodes/agent-node">
    AI-powered content processing
  </Card>
</CardGroup>