Files
twenty/packages/twenty-docs/user-guide/workflows/overview.mdx
Félix Malfait 5d438bb70c Docs: restructure navigation, add halftone illustrations, clean up hero images (#19728)
## Summary

- **New Getting Started section** with quickstart guide and restructured
navigation
- **Halftone-style illustrations** for User Guide and Developer
introduction cards using a Canvas 2D filter script
- **Removed hero images** (`image:` frontmatter + `<Frame><img>` blocks)
from all user-guide article pages
- **Cleaned up translations** (13 languages): removed hero images and
updated introduction cards to use halftone style
- **Cleaned up twenty-ui pages**: removed outdated hero images from
component docs
- **Deleted orphaned images**: `table.png`, `kanban.png`
- **Developer page**: fixed duplicate icon, switched to 3-column layout

## Test plan

- [ ] Verify docs site builds without errors
- [ ] Check User Guide introduction page renders halftone card images in
both light and dark mode
- [ ] Check Developer introduction page renders 3-column layout with
distinct icons
- [ ] Confirm article pages no longer show hero images at the top
- [ ] Spot-check a few translated pages to ensure hero images are
removed

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: github-actions <github-actions@twenty.com>
2026-04-21 09:13:55 +02:00

72 lines
3.2 KiB
Plaintext

---
title: Workflows
description: Learn how to build automations in Twenty.
---
## Why Workflows Matter
Twenty was built to bring maximum flexibility to its users. Rather than forcing you to adapt your business processes to rigid, pre-built features, workflows enable you to build automations that create the CRM that best supports your unique business use cases.
Workflows are Twenty's in-app feature for building these automations. They give you the building blocks to create exactly what your business needs, when it needs it.
## What can I do with workflows?
We recommend building automations for two main purposes:
1. **Internal automations to facilitate your team's day-to-day**: Reduce the amount of manual entries and repetitive tasks that slow down your team.
2. **Bring data in and out of Twenty**: Connect Twenty via API calls and webhooks to your database and other tools.
## Building Your First Workflow
### Step 1: Create a New Workflow
1. Go to **Workflows** accessible below the other objects
2. Click **+ New Record**
3. Give your workflow a name
### Step 2: Add a Trigger
Every workflow starts with a trigger. Choose from:
- **Record events**: When a record is created, updated, or deleted
- **Schedule**: Run at specific times (daily, weekly, etc.)
- **Manual**: Triggered by a user action
- **Webhook**: Triggered by a webhook
<img src="/images/user-guide/workflows/workflow_triggers.png" style={{width:'100%'}}/>
### Step 3: Add Actions
After your trigger, add one or more actions:
- **Create Record**: Add new records to any object
- **Update Record**: Modify existing record data
- **Delete Record**: Remove records from objects
- **Search Records**: Find records matching criteria
- **Upsert Record**: Create or update based on matching criteria
- **Iterator**: Loop through arrays of records
- **Filter**: Control which records proceed
- **Delay**: Wait before continuing (duration or scheduled date)
- **Send Email**: Send emails via your connected account
- **Code**: Run custom JavaScript
- **HTTP Request**: Call external APIs
- **Form**: Get inputs from users within Twenty UI at the time of execution
- **AI Agent** (Coming soon): Run intelligent AI tasks
<img src="/images/user-guide/workflows/workflow_actions.png" style={{width:'100%'}}/>
### Step 4: Test and Activate
1. Use the **Test** button to run your workflow with sample data
2. Review the results to ensure it works as expected
3. Toggle the workflow **Active** when ready
## Workflow Best Practices
- **Edit step names**: Rename your workflow steps to clearly describe what each one does. This helps with maintenance and makes it easier to hand off to coworkers
- **Leverage previous step data**: You can use fields from records returned by any previous step in your workflow
- **Start simple**: Begin with basic workflows and add complexity over time as you become more comfortable with the system
- **Plan before building**: Map out your workflow logic before you start building to avoid getting stuck halfway through
## Next Steps
- [Workflow Triggers](/user-guide/workflows/capabilities/workflow-triggers)
- [Workflow Actions](/user-guide/workflows/capabilities/workflow-actions)
- [CRM Automations](/user-guide/workflows/how-tos/crm-automations/closed-won-automations)