Automations Tutorial

Automations in Dawiso help you reduce manual work, enforce consistency, and keep your data governance processes running smoothly, without needing to chase people or update everything by hand. By defining rules that respond to user actions or run on a schedule, you can make sure the right people are notified, the right metadata is updated, and nothing falls through the cracks.

Each automation consists of three core parts: triggers (what starts the rule), a stream (conditions and filters to target the right objects), and actions (what should happen).

You can use automations to:

• React to changes in workflows or metadata.
• Perform checks and updates on a regular schedule.
• Notify owners or stewards based on specific events.
• Apply changes across objects automatically when certain criteria are met.

Whether you are maintaining documentation, managing ownership, or ensuring quality standards, automations let you build helpful, hands-off workflows that save time and keep your environment organized.

In this tutorial series, we will go through a few examples to show you how to configure automation rules in Dawiso, step by step.

Automation Use Cases

Before we dive into the configuration, here are several real-world automation examples that support efficient governance, timely validation, and better collaboration across teams. Each use case shows how automation can reduce delays, enforce standards, and keep your data and documentation workflows consistent and on track.

1. SLA Deadline Monitoring (Financial Sector)

Financial institutions rely on timely data updates to meet internal and regulatory reporting standards (e.g., BCBS 239). Service Level Agreement (SLA) deadlines are often missed without anyone noticing, risking compliance violations. Automating SLA deadline monitoring ensures accountability and provides time for proactive remediation.

This is how the rule will be set up:

Trigger	Stream	Action
Daily schedule	Data products where the SLA Date is in 7 days	Set object status to Review, Notify the Owner and Steward

This automation rule ensures that approaching SLA deadlines are detected in advance and responsible users are notified to take timely action.

2. Transition to Review When Metadata Is Complete (Sales Strategy)

Sales teams often create and maintain strategic documents that require proper classification and review before they are finalized. But if all required metadata is not provided, the approval process can stall, leading to delays.

With this automation, once all key metadata fields are completed (such as content, owner, labels, and classification), the document is automatically moved to the Review workflow state for validation.

This is how the rule will be set up:

Trigger	Stream	Action
Object is updated	Objects in the Draft workflow state in the Sales Strategy space that have all required metadata filled in (summary, description, owner, steward, labels).	Set object status to Review, Notify the Steward

This automation rule ensures that once all required metadata is provided, sales strategy documents are promptly moved forward for validation, reducing delays and keeping the documentation workflow efficient and consistent.

3. Add Default Description

When users create new objects, they often skip documentation until much later. To prevent blank fields and improve visibility, a default description and tracking label can be applied immediately.

This is how the rule will be set up:

Trigger	Stream	Action
A new object is created	Objects in the Operational Metrics space	Set description to a variation of “AVERAGE DAILY TRANSACTION VOLUME IN Q1: Document number #001. Awaiting documentation,” where the title is based on the category and the document number is generated dynamically.

This automation rule ensures that newly created objects are clearly marked for follow-up and not overlooked during later documentation reviews.

4. Reopen Approved Objects After Comments or Changes

When changes to attributes of approved objects are made, or when new comments are added, the object should be reviewed again. Without automation, these updates could go unnoticed, compromising data quality or introducing undocumented changes into trusted sources.

This is how the rule will be set up:

Trigger	Stream	Action
An object update or a new comment	Objects in a specified space, where workflow state is Approved	Change workflow state to Review, Notify the assigned Steward

This automation rule ensures that approved content remains trustworthy and that any changes are properly reviewed before being accepted again.