Automations

Automations execute actions automatically when a specific event occurs — for example, send a notification when a deadline is approaching, trigger a webhook when a status changes, or sort photos into folders when they are uploaded.

Opening automations

In any database view, click the ⚡ icon in the right side of the toolbar. The automations panel opens as a sidebar.

Structure of an automation

Every automation consists of:

Trigger — the event that fires the automation
Conditions (optional) — filters that must pass before any actions run
Actions — what happens (one or more)

Templates (Recipes)

When creating a new automation, you can choose from 8 pre-built templates:

Template	Trigger	Action
Deadline reminder	Date reached	Notify workspace
New entry	Row added	Notify workspace
Create page	Row added	Create page
Status change	Property changed	Send webhook
External trigger (Webhook)	Webhook received	Notify workspace
Weekly reminder	Schedule (Mondays)	Notify workspace
Auto-sort photos	File uploaded	Move to media folder
Custom rule	freely configurable	freely configurable

Triggers

Row added

Fires whenever a new row is created in the database.

Use case: Automatically assign a new task to a team member.

Property changed

Fires when the value of a specific column changes. You can optionally specify a target value — for example, only when the status switches to “Done”.

Configuration:

Select a column (empty = any column)
Value (optional)

Use case: When Status → “Approved”, send a webhook to an external platform.

Date reached

Fires N days before or after the value of a Date column. Runs daily at 00:05.

Configuration:

Select a Date column
Offset: negative = days before, positive = days after, 0 = on the day itself

Use case: Reminder 2 days before a shooting date.

Webhook received

Fires when an external application sends an HTTP POST to the generated webhook URL.

Configuration: None — after saving, a unique URL is shown automatically.

URL format:

https://api.pachurros.com/v1/incoming/webhook/{TOKEN}

Request body (optional):

{ "row_id": 42 }

If row_id is provided, actions like “Set property” have access to the row data.

Rotate URL: Click “Rotate URL” to generate a new token and deactivate the old URL.

Use case: Zapier, Make, or a custom script triggers the automation from outside.

Scheduled

Fires at a fixed point in time, independent of row events. Runs daily at 00:05.

Configuration:

Daily — fires every day
Weekly — select a day of the week (Sun–Sat)
Monthly — select a day of the month (1–31)

Use case: Send a weekly status reminder to the team every Monday.

File uploaded

Fires when a file is uploaded to the workspace media library.

Configuration:

All files — fires on every upload
Images only — fires only for image files (JPEG, PNG, …)
Videos only — fires only for video files
Audio only — fires only for audio files
Documents only — fires only for documents (PDF, DOCX, …)

Use case: Automatically sort photos into dated folders when uploaded.

Conditions (global)

Conditions are evaluated before any actions run. If they are not met, the automation is skipped.

Supported operators:

is / is not
contains
is empty / is not empty

Conditions are available for row-based triggers (Row added, Property changed, Date reached, Webhook received) — not for Scheduled and File uploaded.

Actions

Set property

Changes the value of a column in the triggering row.

Example: Automatically set Status to “In Progress” when a new row is created.

Notify workspace

Sends an in-app notification to all members of a workspace.

Configuration:

Message text (optional)
Workspace (when multiple workspaces exist: select the target workspace)

Create row

Creates a new row in a database — including in a different database or a different workspace.

Configuration:

Select target workspace (when multiple workspaces exist)
Select target database
Fill in fields:
- Static — a fixed value
- From trigger — copy the value from a column in the triggering row

Create page

Creates a new page with a configurable title.

Configuration:

Title template — column placeholders {ColumnName} are replaced with values from the triggering row. Example: Brief — {Name} → Brief — Sample Production
Parent (optional) — the new page is created as a sub-page of an existing page

Send webhook

Sends an HTTP POST or GET request to any URL.

Configuration:

URL
Method: POST or GET
Include row data in body (toggle) — sends all cell values of the triggering row as a cells object
Custom headers (optional) — e.g. Authorization: Bearer TOKEN

Example body (POST with row data):

{
  "event": "automation_triggered",
  "database_id": 12,
  "row_id": 99,
  "timestamp": "2026-05-04T10:00:00.000Z",
  "cells": { "34": "Done", "35": "2026-05-10" }
}

Use case: Slack notification, Zapier/Make integration, calling a custom backend.

Move to media folder

Moves an uploaded file into a folder in the media library. Use together with the File uploaded trigger.

Folder patterns:

Pattern	Resulting folder	Example
By date	`YYYY/MM`	`2026/05`
By type	`Images` / `Videos` / `Audio` / `Documents`	`Images`
Custom name	freely defined text	`Jobs 2026`

Per-action conditions (branching)

Each individual action can have its own additional conditions — independent of the automation’s global conditions.

Click Only run if… inside an action to set conditions for that specific action. If they are not met, only that action is skipped — the remaining actions still run.

Use case: Three actions — always send a notification, create a row only if Status = “Urgent”, fire a webhook only if Priority is not empty.

Enabling / disabling an automation

Click the toggle next to an automation name to turn it on or off. Disabled automations are not executed but remain fully configured.

Run log

Expand Recent runs inside an automation to see the last 10 executions:

Timestamp
Status: Success (green dot) or Error (red blinking dot)
Error message (on error)

Multiple actions

An automation can run any number of actions in sequence. Click + Add action. Actions run in order — if one fails, the run is logged as an error.