Rashad Karanouh
bf1220883f
## Summary Follow-up to #22719 (merged), which added partner-marketplace CTAs to four **high-intent, low-traffic** docs pages (SSO, both migration guides, implementation services). Reviewing the docs' **top-visited pages** showed none of those four rank in the top ~20 — they're the high-intent tail, which is correct, but small reach. This PR extends the same pattern to three **high-traffic pages that also carry buying intent**, without touching the pure top-of-funnel intros/quickstarts (volume without intent → a CTA there is just noise). Same conventions as #22719: Mintlify-native `<Tip>` callouts, partner-first with `contact@twenty.com` secondary, directory deep-linked via `?categories=<scope>` and tagged with `?ref=docs-*`. No new snippet; no `docs.json`, navigation, or translation (`l/`) changes. ## Pages changed — screenshots (one per page) > Preview locally with `npx mintlify dev` from `packages/twenty-docs`, or use the Mintlify PR preview once it posts. Paths below are under `docs.twenty.com`. ### 1. `/user-guide/workflows/overview` (~593 views) New `## Need Help?` two-bullet `<Tip>` → **Done for you** (Solutioning partner) / **Onboarding pack** (Workflow Creation). Maps 1:1 to the named onboarding service. _screenshot:_ <img width="1440" height="818" alt="Screenshot 2026-07-10 at 14 34 32" src="https://github.com/user-attachments/assets/231f681d-b5be-4b1e-9b6a-a4947a9fca37" /> ### 2. `/user-guide/data-model/overview` (~954 views) Replaced the plain "Need Help?" line with a two-bullet `<Tip>` → **Done for you** (Solutioning partner) / **Onboarding pack** (Data Model Design). Keeps the existing Implementation Services link. _screenshot:_ <img width="1436" height="817" alt="Screenshot 2026-07-10 at 14 34 14" src="https://github.com/user-attachments/assets/c0fe1064-1030-4062-91c7-24644ac31654" /> ### 3. `/developers/self-host/capabilities/docker-compose` (~2421 views) New `## Managed Hosting` single-line `<Tip>` → *find a certified Twenty hosting partner* (Hosting), contact fallback. Framed as a lighter "prefer not to run it yourself?" alternative — deliberately low-pressure for the DIY self-host audience. _screenshot:_ <img width="1437" height="815" alt="Screenshot 2026-07-10 at 14 33 39" src="https://github.com/user-attachments/assets/a37207cd-2aaa-4aba-848d-cbf06a1e1321" /> ## Notes for reviewers - Page-selection rationale: intent × volume. Kept the four intent-tail pages from #22719; added the highest-traffic pages that also carry a natural partner-buying moment (self-host → Hosting; workflows / data-model → Solutioning). Intros/quickstarts/contribute pages intentionally left untouched. - **Attribution caveat (unchanged from #22719):** twenty.com's analytics (Cloudflare Web Analytics) is path-based, so `?ref=` is not measurable yet. Per-page measurement via a `/go/*` redirect Worker remains a planned, separate follow-up (out of scope here). - `mintlify validate` passes. Opened as a draft. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/twentyhq/twenty/pull/22808?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. -->
81 lines
3.6 KiB
Plaintext
81 lines
3.6 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)
|
|
|
|
## Need Help?
|
|
|
|
<Tip>
|
|
Want help automating your workflows?
|
|
|
|
- **Done for you:** [find a certified Twenty partner](https://twenty.com/partners/list?categories=SOLUTIONING&ref=docs-workflows) to design and build your automations end-to-end.
|
|
- **Onboarding pack:** a 4-hour guided Workflow Creation session with our team — [contact@twenty.com](mailto:contact@twenty.com).
|
|
</Tip>
|