​

Edition limits

For details, see all rights. Click Upgrade or Book a consult.

​

What it does

An automation workflow is a rule you preset for an AI Table — and it runs automatically. Set a trigger and an action and AI Table fires the next steps when data changes.

​

How to use

​

Create a workflow

1. Start blank: click Automation at the top-right of the AI Table → Start blank.

2. From a template: click Automation at the top-right → pick a template. (Good for new users — templates ship with preset triggers and actions; you can edit on top.)

3. AI one-sentence creation This feature is in closed beta — submit the form to apply: Apply

​

Configure the workflow

1. Configure the trigger and the action.

2. All nodes must be configured for the workflow to run. When the red warning indicator in the top-right turns gray, the configuration is complete.

​

Manage automations

In an AI Table you can create, modify, and look up workflows.

1. Global management Click Automation — the left sidebar lists all workflows configured for this AI Table.

2. Execution log On the workflow editor, click Execution log in the top-right — see total runs, successes, and failures.

3. Enable / disable a workflow In the workflow list, the toggle switches state — on = running, off = disabled.

4. Edit / Copy / Delete a workflow Pick a workflow → click More → edit / copy / delete.

5. Troubleshoot errors

Click into an execution record’s detail to one-click copy the error and dig into the cause.

​

Run-count metering

Automation runs on the DingTalk Connector Platform — every workflow node consumes connection-flow node executions.

​

What is a node-execution count?

Connection-flow node executions (or “node executions”) is the commercial billing metric of the DingTalk Connector Platform. It tallies node runs across AI Table, bots, OA approvals, and the connector platform for the current org. Users with developer access can view details on the DingTalk Connector Platform.

​

How to view this month’s count

Go to Workflow management to see the org’s accumulated runs for the month.

​

Counting rules

​

Counted

• Successful action node — 1.
• Delay node call — 1.
• HTTP request node call — 1.
• Branch node — 1 per evaluation.
• A Loop node counts as 1 per workflow run, regardless of how many iterations. Set Max iterations carefully.
• When an action returns nothing, it still counts as a successful run (e.g. directory queries with no matches still count as 1).

​

Not counted

• Trigger event execution.
• Skipped nodes; failed nodes.
• Debug runs.

For details, see all rights. Click Upgrade or Book a consult. For details, see all rights. Click Upgrade or Book a consult.