# Getting Started with Nola

Getting started with Nola is simple. This guide will show you how to access Nola and start using her to build your app.

## How to Access Nola

Nola is available directly within the Noloco app builder. Here's how to open Nola:

1. **Open your Noloco app** in Build Mode
2. **Look for the Nola tab** in the top-left tab of your app studio
3. **Click the icon** to open the Nola chat interface

That's it! Nola is now ready to help you build.

{% hint style="info" %}
If you don't see the Nola tab, make sure you're on a supported plan (Free, Starter, Pro, or Business). Some legacy plans don't have access to Nola.
{% endhint %}

## Your First Conversation with Nola

When you first open Nola, you'll see a friendly welcome message and some suggested actions to get started. Here are some great first requests to try:

### Example Starter Requests

**For New Apps:**

* "Help me create a Customers table with contact information"
* "Generate 10 sample records for my Projects table"
* "Set up a basic CRM structure for my business"

**For Existing Apps:**

* "Link my Customers table to my Orders table"
* "Create a [workflow](/workflows/workflows.md) that sends an email when a task is marked complete"
* "Add a [dashboard page](/pages/blank-pages.md) with [charts](/views/display/charts.md) showing my sales data"

## Understanding Nola's Responses

When you make a request, Nola will:

1. **Confirm she understands** what you're asking for
2. **Take action** or ask clarifying questions if needed
3. **Explain what she did** so you can learn and verify
4. **Suggest next steps** to continue building

### Example Conversation

**You:** "Create a Tasks table"

**Nola:** "I'll create a Tasks table for you. What fields would you like to include? I suggest:

* Task Name (text)
* Description (long text)
* Due Date (date)
* Status (single select: To Do, In Progress, Complete)
* Assigned To (linked to Users)

Would you like me to proceed with these fields, or would you like to customize them?"

**You:** "That looks perfect, go ahead"

**Nola:** "Done! I've created your Tasks table with those 5 fields. The table is now available in your data sources. Would you like me to:

* Create a view to display these tasks?
* Generate some sample data?
* Set up a workflow for task notifications?"

## Tips for Communicating with Nola

### Be Specific

The more details you provide, the better Nola can help.

❌ **Vague:** "Add a form" ✅ **Specific:** "Add a form for creating new customer records that includes name, email, phone, and company fields"

### Break Down Complex Requests

For complex tasks, consider breaking them into steps.

❌ **Too Complex:** "Build me a complete project management system with tasks, clients, timesheets, and invoicing" ✅ **Step by Step:**

1. "Create a Projects table with name, client, start date, and status"
2. "Now create a Tasks table linked to Projects"
3. "Add a timesheet tracking feature"

### Use Natural Language

You don't need special commands or syntax—just talk to Nola naturally.

✅ "Can you help me..." ✅ "I need to..." ✅ "How do I..." ✅ "Show me how to..."

### Ask Questions

Not sure how something works? Just ask!

✅ "How do [workflows](/workflows/workflows.md) work in Noloco?" ✅ "What's the difference between a [rollup](/data/collections/rollups.md) and a [lookup field](/data/collections/lookup-fields.md)?" ✅ "Can you explain [permissions](/users-and-permissions/user-roles-and-permissions.md) to me?"

## What Happens When Nola Takes Action

When Nola makes changes to your app:

* **Changes are immediate** - You'll see them reflected in your app builder
* **Changes can be undone** - Use Noloco's undo button or manually revert changes
* **You stay in control** - Nola will ask for confirmation before making major changes

{% hint style="warning" %}
Always review changes Nola makes, especially before [publishing](/settings/publishing.md) your app to your team or clients.
{% endhint %}

## Nola's Current Context

Nola is context-aware, meaning she understands:

* What app you're working on
* What page you're looking at
* What tables and fields you have
* Where you are in the builder
* What you've previously discussed in the conversation

This means you can have natural, flowing conversations without repeating context.

**Example:** **You:** "Create a Customers table" **Nola:** \[creates table] **You:** "Now add an Orders table linked to it" **Nola:** \[knows "it" refers to Customers and creates the link]

## When to Use Nola vs. Manual Building

### Use Nola When:

* Setting up new data structures
* Generating sample data
* Creating [workflows](/workflows/workflows.md)
* Learning new features
* You want to save time on repetitive tasks

### Build Manually When:

* Fine-tuning visual design
* Making small tweaks to existing elements
* You want precise control over every detail
* Nola can't *yet* do what you need her to

{% hint style="success" %}
**Best Practice**: Use Nola to get 80% of the way there quickly, then manually fine-tune the remaining 20% to your exact preferences.
{% endhint %}

## Getting Help

If you're not sure what Nola can do, just ask:

* "What can you help me with?"
* "Show me examples of what you can do"
* "Help me understand \[feature name]"

## Next Steps

Now that you know how to access and communicate with Nola, learn more about what she can do:

{% content-ref url="/pages/OZcYeVgozL69b8jLqLgq" %}
[What Nola Can Do](/nola/what-nola-can-do.md)
{% endcontent-ref %}

{% content-ref url="/pages/0647kJQ2WZkWSoFTDaXF" %}
[Tips and Best Practices](/nola/tips-and-best-practices.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.noloco.io/nola/getting-started-with-nola.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.