Automate your work

Automate repetitive steps so the team spends time on decisions, not data entry.

In Stackby, three pillars cover most needs: built-in automations, computed fields, and formulas used together, they eliminate manual nudges and keep data current.

1. Save time with automations

Use trigger-and-action workflows to react to changes, schedule tasks, or connect tools without code—for example, when Status changes to Approved, notify the Owner in Slack, create a task, or update a field. Triggers can include record updates, new records, scheduled times, or incoming webhooks; actions range from sending messages and emails to creating/updating records and calling web APIs.

Tips:

• Model data clearly first; automations work best on clean fields and stable views.youtube

• Prefer dynamic values from the triggering record over hardcoded text to keep flows reusable.

• Test and use run histories to troubleshoot; many triggers on formula fields evaluate on an interval.

2. Learn when (and how) to use computed fields

Computed fields auto-update based on configuration, giving live context without manual edits—common types include Created/Last modified (who/when), Lookup/Aggregation/Lookup Count across linked records, and Button to trigger actions. They compute per-column (not per-cell), ensuring consistency across all records and reducing errors versus ad‑hoc spreadsheet formulas.

Use cases:

• Governance: stamp who created/modified a record and when for audit trails.

• Analytics: summarize totals or counts from linked records with Rollup or Aggregation/Lookup Count.

• Cross-table context: pull key details via Lookup so teams see the latest info in related tables.

3. Write your first formula

Formula fields derive a value from other fields using math, text, and logical operators—for example, Price * Quantity, IF(Status="Blocked","⚠️",""), or DATEADD({Due date},-7,"days"). Field names with spaces are wrapped in curly braces, and expressions can be nested for complex logic.

Starter patterns:

• Numeric: {Budget} - {Actuals} for variance.

• Logical: IF({Score}>=90,"A","B") to categorize.

• Text: CONCAT({Client}," – ",{Project}) for human‑readable names.

4. Explore what’s possible with formulas

Go beyond basics with a rich library of functions—math (SUM, ROUND), text (LEFT, FIND), logic (IF, AND, OR), date/time (DATEADD, DATETIME_DIFF), and conditionals for color/status flags—plus a playground base to experiment safely. Formulas are column-level, so they recalculate automatically as inputs change, and they pair well with automations that trigger on formula-driven states.

Power tips:

• Use formulas to compute trigger conditions (e.g., “Ready to notify” flag), then let an automation send the message.

• Keep formulas readable: break complex logic into helper fields (e.g., clean text → categorize → final label).

• Remember: formulas can’t be directly edited by users; they reflect other fields—use regular fields for user input.

Practical checklist:

• Identify repetitive actions and convert them to triggers + actions.

• Add computed fields for audit, rollups, and cross-table context.

• Implement baseline formulas for dates, flags, and naming; expand with advanced functions as needs grow.