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

# Button

> In AI Table, the Button field can act as an automation trigger. Open the table, click the button — the preset action runs.

# 1 Overview

In AI Table, the Button field can act as an **automation trigger**. Open the table, click the button — the preset action runs.

**Common scenarios**:

* **Notifications** — in repair workflows, click the button to submit a repair ticket and notify the assigned technician.
* **Group creation** — in store ops, click the button to create a chat group and write the group ID back to the table.
* **Information flow** — in product intake, click the button to confirm kickoff: update the request table's status to "Kicked off" and add a new record in the project management table.

# 2 Basics

Click ➕ on the right of the title bar to **create a field** — pick **Button** under field types. In the config panel, set the field name, button label, button color, and success toast.

What runs after a click is configured via **automation**. Available automations include common actions (basic ops, control flow, HTTP request), AI capabilities, and business apps. See the automation actions reference.

After configuration, click **Save and enable** in the upper-right. Click **Run history** to inspect past runs.

# 3 Scenarios and steps

## 3.1 Click the button to send a notification with a link

Example: a repair workflow.

### 3.1.1 What it looks like

**Submitter:**

In the technicians table, assign a repair ticket to a technician with no current task — click **Button** to notify them.

**Technician:**

Once assigned, you receive the notification below. Click **View** to jump to the screen above, then click **In-progress repair** to see the request details.

### 3.1.2 Configuration

Set the button name.

Pick the recipient — set the notification title and body.

## 3.2 Click the button to create a group

Example: per-store group creation.

### 3.2.1 What it looks like

Click the create-group button — a new group appears in your chat list.

### 3.2.2 Configuration

Set the button name.

Set the group name, type, members, and target group.

Sync the new group's ID back to the Group field.

## 3.3 Click the button to edit records

Example: project kickoff.

### 3.3.1 What it looks like

Click **Confirm kickoff** — the status flips to **Kicked off**, and a new row syncs into the project management table.

### 3.3.2 Configuration

Set the button field.

Pick the destination table and map the synced fields.

Set up the update — point at the record that triggered the button and set what to change.

# 4 Button automation vs condition automation

## 4.1 Core differences

| Dimension   | Button automation           | Condition automation                   |
| ----------- | --------------------------- | -------------------------------------- |
| Trigger     | Manual (click)              | System (when condition met)            |
| Control     | User-authorized             | Rule-driven                            |
| Timing      | Immediate (manual decision) | Real-time / periodic (no human needed) |
| Flexibility | One-off / batch             | Auto                                   |

## 4.2 When to pick button over condition

| Scenario                                 | Example                                                            | Value                                                 |
| ---------------------------------------- | ------------------------------------------------------------------ | ----------------------------------------------------- |
| Sensitive ops needing human confirmation | Payment approval                                                   | Avoid loss from system mistakes                       |
| Dynamic business cases                   | "Urgent escalation" on support tickets, manual stock-issue recheck | Human judgment fills rule gaps                        |
| High-compliance domains                  | Medical prescription, e-signature on legal docs                    | Audit trail with click attribution                    |
| Resource-sensitive tasks                 | Bulk group creation, bulk email                                    | Avoid burning resources on high-frequency automations |

## 4.3 When to pick condition over button

| Scenario                               | Example                                | Value                      |
| -------------------------------------- | -------------------------------------- | -------------------------- |
| High real-time                         | Stock / FX price alerts                | Reacts immediately         |
| Repetitive standard ops                | Order status sync                      | Saves review time          |
| Standardized flows with no human input | Attendance sync, group welcome message | Fast and saves review time |

# 5 FAQ

* Q: What ops does the Button field support?

  A: All automation actions.
* Q: Can the Button field be **copied**?

  A: Yes — but only the title, label, and color copy; the automation does not.
* Q: Who can configure or click the Button field?

  A: **Configure** — without advanced permissions, owners and users with **manage / edit** access can configure. With advanced permissions on, only owners and **manage** users can; **edit** users can view the config but not modify it.

  **Click** — when the button is clickable, anyone who can see the field can click it.
* Q: How do I record who clicked the button?

  A: Set up an automation: trigger on **When the button is clicked**, action **Update record**, write the **button clicker** to a member field.

  **Note**: this only stores the most recent clicker — for full history, view the record's revision history.