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

# Start Node

> Run your workflow manually with a click

The Start node is the simplest way to run a workflow - you click a button and it starts. You can also type in some starting information if needed.

This is great for testing, one-off tasks, or workflows you want to run whenever you need them.

## When to Use

* **Run it yourself** - When you want to click a button to make it go
* **Testing** - Try out your workflow with test data
* **One-off tasks** - When you want to run it occasionally, not automatically
* **Getting started** - The easiest way to begin building a workflow

## Example: Document Processor

A workflow that processes different documents based on user input:

<Steps>
  <Step title="Add a Start node">
    Create a new workflow and add a Start node as the entry point.
  </Step>

  <Step title="Configure the workflow">
    Connect the Start node to an Ask AI node that processes the input:

    ```
    Summarize the following document:
    {{on_start_1.startingInputData}}
    ```
  </Step>

  <Step title="Run with input">
    Trigger the workflow and paste any document text as the starting input. Ask AI processes whatever text you provide.
  </Step>
</Steps>

### Input Example

When triggering the workflow, you might provide:

```json theme={null}
{
  "title": "Q4 Sales Report",
  "content": "Revenue increased 15% compared to Q3...",
  "format": "summary"
}
```

Then access specific fields:

```
Document: {{on_start_1.startingInputData.title}}
Content: {{on_start_1.startingInputData.content}}
Requested format: {{on_start_1.startingInputData.format}}
```

## Example: Customer Lookup

A support workflow that looks up customer information:

```
Workflow: Customer Lookup
├── Start (receives customer email)
├── External API (query CRM for customer data)
├── Ask AI (summarize customer history)
└── Update Variable (store summary for reference)
```

Input when triggering:

```json theme={null}
{
  "customerEmail": "jane@example.com",
  "reason": "billing inquiry"
}
```

## Tips

<Tip>
  Use structured JSON objects as input rather than plain strings. This makes it easier to access specific fields and extends the workflow's flexibility.
</Tip>

<Note>
  The Start node is perfect for development. Build your workflow with a Start trigger, then add other event types (webhook, schedule) once the logic is working.
</Note>

## Settings

<ParamField path="name" type="string" default="On Start">
  What to call this node (shown on the canvas).
</ParamField>

<ParamField path="key" type="string" default="on_start_1">
  A short code to reference this node's data.
</ParamField>

<ParamField path="description" type="string">
  Optional notes about this workflow.
</ParamField>

## Outputs

<ParamField path="startingInputData" type="any">
  Whatever you type in when you start the workflow.
</ParamField>

Use it in later nodes like this:

```
{{on_start_1.startingInputData}}
```

## Related Nodes

<CardGroup cols={2}>
  <Card title="Webhook" icon="webhook" href="/nodes/triggers/webhook">
    Trigger from external HTTP requests instead of manual execution.
  </Card>

  <Card title="Update Variable" icon="database" href="/nodes/actions/update-variable">
    Store the input data for use throughout the workflow.
  </Card>
</CardGroup>