> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/documentation/readme/powertable-sheets/concepts/automation.md).

# Automation

Automation in powertable enables you to streamline repetitive tasks and business processes by automatically executing predefined actions in response to specific events. Instead of performing manual updates, record creation, or data synchronization tasks, you can configure automation workflows that run automatically when defined conditions are met.

Automation helps maintain data consistency across related tables, reduces manual effort, and ensures that business processes run consistently. Data changes, user actions, form submissions, and other events can trigger workflows, allowing powertable to respond automatically to changes in your data.

### Common use cases

Powertable automations can be used to:

* Synchronize changes across related and dependent tables.
* Automatically create, update, or delete records based on data changes.
* Perform cascading updates to maintain data consistency.
* Trigger actions when users submit forms or click button columns.
* Execute bulk record operations without manual intervention.

### How automation works

An automation workflow consists of two components:

* **Trigger** – The event that starts the workflow.
* **Action** – The operation that is performed when the trigger occurs.

<figure><img src="/files/Znoc8EnzxbamojJPaz7y" alt="" width="375"><figcaption></figcaption></figure>

When a trigger event occurs, powertable automatically executes one or more configured actions.

#### Triggers

Triggers define when an automation workflow runs. Common trigger events include:

* Record creation
* Record updates
* Record deletion
* Form submissions
* Button clicks

You can further refine triggers by defining conditions or rules that determine when the workflow should execute.

#### Actions

Actions define what happens after a trigger is activated. Depending on your scenario, actions can

* Create records in another table
* Update existing records
* Delete records
* Find matching records
* Create records in bulk
* Perform cascading updates across related tables

Multiple actions can be combined within a single workflow to automate complex business processes.

### Benefits of automation

Automation helps organizations:

* Reduce manual and repetitive work.
* Improve data quality and consistency.
* Minimize errors caused by manual updates.
* Ensure dependent tables remain synchronized.
* Standardize business processes across teams.
* Scale operational workflows without custom code.

### Automation workflow

An automation workflow follows these steps:

1. A trigger event occurs.
2. Trigger conditions are evaluated.
3. The configured action or actions are then executed if the conditions are met.
4. Related records and tables are updated as required.
5. The workflow completes automatically without user intervention.

By combining triggers and actions, powertable enables you to build no-code automation workflows that keep data synchronized and business processes running efficiently.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.fabricplan.com/documentation/readme/powertable-sheets/concepts/automation.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.