> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/database/microsoft-sql.md).

# Microsoft SQL

Read, add, and update business data in your Microsoft SQL database from a workflow.

## What this node helps you do

Use the **Microsoft SQL** node when your workflow needs data from a Microsoft SQL database.

This node helps you:

* find records from a selected table
* add new rows from workflow data
* update existing records when business data changes

<figure><img src="https://3864624312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRdo1pkMnofwxf3lpWftw%2Fuploads%2FGCTtc5VvOw4TbYYpMM5U%2FMicoSQL.png?alt=media&amp;token=7e37dbac-f77d-4919-b16b-9b603332f400" alt=""><figcaption></figcaption></figure>

### Common business examples

Teams often use this node to:

* check customer details before sending a response
* save a new request into an internal operations table
* update a case, order, or ticket status

## Available actions

The **Action** field gives you 3 options:

* **Query data from table** — find or retrieve data from a selected table
* **Add data to table** — create a new record in the table
* **Update record** — change an existing record in the table

<figure><img src="https://3864624312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRdo1pkMnofwxf3lpWftw%2Fuploads%2F35M2JfofNDQZXGcVSIfo%2FMicroSQL.gif?alt=media&amp;token=05fd4174-db55-484d-a9b6-cfb8724186cb" alt=""><figcaption></figcaption></figure>

## Basic setup

### 1. Select resource

Choose the Microsoft SQL connection your workspace should use.

If you do not see the right connection, open **Manage** and add it in **Workspace → Integrations**.

### 2. Select table

Choose the table that contains the business data you want to use.

Examples include `customers`, `orders`, `tickets`, or `requests`.

### 3. Choose the action

Pick what the workflow should do with that table:

* read data
* add data
* update data

## Query data from table

Choose **Query data from table** when you need to search or retrieve information.

This action includes **SQL Generate Method** with 2 options:

* **Use AI** — describe what you want in plain language
* **Manual enter SQL** — write the SQL query yourself

### Use AI

Choose **Use AI** if you want a faster setup and do not want to write SQL.

In **Input**, describe the result you want.

Examples:

* `Find open support tickets for this customer`
* `Get the latest order for this account`
* `Show requests created this week`

Diaflow uses that instruction to generate the SQL query for you.

### Manual enter SQL

Choose **Manual enter SQL** if your team already has a specific query.

Enter the SQL in the code editor.

Use this option when you need exact control over filters, joins, or sorting.

## Add data to table

Choose **Add data to table** when your workflow needs to save a new record.

This is useful after:

* a form submission
* a lead capture flow
* an approval or internal request flow

Make sure the values you send match the columns in the selected table.

## Update record

Choose **Update record** when your workflow needs to change data that already exists.

This is useful when you need to:

* change a status
* assign an owner
* save a workflow result back into the database

Make sure your workflow identifies the correct record before updating it.

## Field reference

* **Select resource** — chooses the Microsoft SQL connection
* **Table** — chooses the table the node will use
* **Action** — decides whether the node reads, adds, or updates data
* **SQL Generate Method** — appears for query actions and lets you use AI or manual SQL
* **Input** — plain-language instruction for AI-generated queries
* **Code editor** — SQL entry area for manual queries

## Tips for first-time users

* Start with **Query data from table** to confirm the connection works.
* Use a simple table first, such as customers or tickets.
* If you are not sure what to write, use **Use AI** before manual SQL.
* Check the **Result** tab after each test run.

{% hint style="info" %}
If you are unsure which table or fields to use, ask your database owner or technical team first.
{% endhint %}