Skip to content

The open alternative to Salesforce, designed for AI.

Docs update (#26793)

BOHEUS6e07bf207f66
diff --git a/packages/twenty-docs/developers/extend/apps/data/timeline-activity-types.mdx b/packages/twenty-docs/developers/extend/apps/data/timeline-activity-types.mdx
index 0f0d69eaf30..12a9c3737ba 100644
--- a/packages/twenty-docs/developers/extend/apps/data/timeline-activity-types.mdx
+++ b/packages/twenty-docs/developers/extend/apps/data/timeline-activity-types.mdx
@@ -7,8 +7,7 @@ icon: 'clock-rotate-left'
A timeline activity type defines the stable vocabulary for an event shown in a record's timeline. Standard objects and app objects use the same contract: a type has a label and icon, can optionally declare when it is emitted, and can optionally render through one of your app's [front components](/developers/extend/apps/layout/front-components).
<Note>
- Timeline activity types are in beta and are coming soon in Twenty 2.34. The
- API can evolve while we learn from app developers' use cases.
+ Timeline activity types are in beta, the API can evolve while we learn from app developers' use cases.
</Note>
Create one with the scaffolder:
diff --git a/packages/twenty-docs/user-guide/workflows/capabilities/workflow-actions.mdx b/packages/twenty-docs/user-guide/workflows/capabilities/workflow-actions.mdx
index 81be8e0053b..70d1683f12c 100644
--- a/packages/twenty-docs/user-guide/workflows/capabilities/workflow-actions.mdx
+++ b/packages/twenty-docs/user-guide/workflows/capabilities/workflow-actions.mdx
@@ -87,6 +87,29 @@ Creates a new record or updates an existing one based on matching criteria. This
**Output**: The created or updated record data is available for use in subsequent steps.
+### Pick Record
+Picks a single record out of a list of candidates, using a distribution strategy. Useful for assigning an incoming lead to a rep, or spreading records across a set of owners.
+
+**Configuration**:
+- Select the candidate records in the **Pick from** field
+<Note>
+**Pick from** only accepts a static, manually selected set of records, you cannot pass in a variable such as the output of a `Search Records` step.
+</Note>
+- Choose a strategy:
+
+| Strategy | Description |
+|---|---|
+| **Random** | Picks one candidate at random |
+| **Round Robin** | Cycles through candidates in order, remembering its position between runs |
+| **Load Balanced** | Picks the candidate currently linked to the fewest records on a field you choose (e.g., the sales rep with the fewest linked opportunities) |
+
+- For **Load Balanced**, select the object and field used to count existing load per candidate
+<Note>
+Load Balanced counts every linked record on that field, regardless of status, for example, all opportunities linked to a rep, not just open ones.
+</Note>
+
+**Output**: The picked record is available for use in subsequent steps.
+
## Flow Actions
### Iterator
@@ -175,6 +198,27 @@ Only one recipient is possible at the moment.
Adding HTML signatures is not possible at the moment.
</Note>
+### Draft Email
+Creates a draft email instead of sending it. Same configuration as Send Email, but the message is saved to the connected mailbox's Drafts folder for manual review and sending, rather than going out automatically.
+
+**Configuration**: Same fields as [Send Email](#send-email) — sender account, recipient, subject, and body.
+
+**Use case**: AI- or workflow-generated emails you want a human to review before they go out.
+
+### Create Calendar Event
+Creates an event on a connected calendar.
+
+**Configuration**:
+- Select the connected calendar account
+- Set the event title, description, and location
+- Set start and end date/time, or mark the event as full-day
+- Optionally set a time zone
+- Add attendees
+- Choose whether to send calendar invitations to attendees
+- Choose whether to add a conferencing link to the event
+
+**Output**: The created event data is available for use in subsequent steps.
+
### Form
Prompts a form during workflow execution to collect user input. The responses can then be used in subsequent steps to create records, send emails, or execute any other action based on the input.
<Warning>
@@ -260,7 +304,7 @@ Sends a request to an external API as part of your workflow.
## AI Actions
-### AI Agent - Coming Soon
+### AI Agent
Runs an AI agent within your workflow to perform intelligent tasks.
**Configuration**:
@@ -284,3 +328,20 @@ AI Agent actions consume workflow credits based on the AI model used. See [Workf
<Note>
AI agents respect role-based permissions. You can assign specific roles to agents under **Settings → Members → Roles** to control what data they can access. See [Permissions](/user-guide/permissions-access/capabilities/permissions) for details.
</Note>
+
+### Classify
+Asks an AI model to answer one or more structured questions about data from previous steps — for example, scoring a lead or categorizing an inbound message. Unlike AI Agent, Classify always returns a value in the shape you defined, so it's suited for driving branches deterministically.
+
+<Note>
+**Prerequisite**: Classify runs on Twenty's evaluation model (Jev), which an admin must enable and configure with a TypeSafe AI API key. Without it, running this step fails.
+</Note>
+
+**Configuration**:
+- **Input**: The data to classify (e.g., a record or text from a previous step)
+- **Questions**: Add one or more questions, each with:
+ - A **name** — used to read the answer downstream (e.g., `{{stepId.answers.<name>}}`)
+ - A **type**: `boolean`, `choice`, or `score`
+ - **Instructions** for the model
+ - **Criteria** — the possible choices, or the score levels from lowest to highest (not needed for `boolean`)
+
+**Output**: The answer to each question, keyed by its name, plus the model used.
diff --git a/packages/twenty-docs/user-guide/workflows/capabilities/workflow-branches.mdx b/packages/twenty-docs/user-guide/workflows/capabilities/workflow-branches.mdx
index 0aae418e8a3..ed9da78956b 100644
--- a/packages/twenty-docs/user-guide/workflows/capabilities/workflow-branches.mdx
+++ b/packages/twenty-docs/user-guide/workflows/capabilities/workflow-branches.mdx
@@ -29,9 +29,20 @@ Each branch is independent. Adding a branch doesn't affect other existing paths
Branches appear as parallel paths in the workflow editor. You can drag nodes to rearrange the visual layout without affecting execution.
-## Conditional Branches
+## If/Else Branches
-Since all branches run by default, use **Filter** nodes to control which paths actually execute:
+For mutually exclusive paths — where you want exactly one branch to run, not several — add an **If/else** action instead of splitting the canvas manually.
+
+**Configuration**:
+- The first branch (**If**) has a filter condition
+- Click **Add route** to insert additional **Else if** branches, each with its own condition
+- The last branch (**Else**) has no condition and catches everything the other branches didn't match
+
+**How it works**: Conditions are evaluated in order, top to bottom. The workflow continues down the first branch whose condition matches; every other branch is skipped.
+
+## Conditional Branches (Manual, with Filter)
+
+If/else covers most cases, but you can also build the same pattern by hand: since all manually created branches run by default, use **Filter** nodes to control which paths actually execute:
| Branch | Filter Condition | Action |
|--------|------------------|--------|
diff --git a/packages/twenty-docs/user-guide/workflows/how-tos/need-more-help/workflows-faq.mdx b/packages/twenty-docs/user-guide/workflows/how-tos/need-more-help/workflows-faq.mdx
index 2417ff9105c..f6c95e37fab 100644
--- a/packages/twenty-docs/user-guide/workflows/how-tos/need-more-help/workflows-faq.mdx
+++ b/packages/twenty-docs/user-guide/workflows/how-tos/need-more-help/workflows-faq.mdx
@@ -39,20 +39,8 @@ description: Frequently asked questions about workflows in Twenty.
See [Workflow Triggers](/user-guide/workflows/capabilities/workflow-triggers) for details.
</Accordion>
- <Accordion title="I don't see an If/Else node. What should I do?">
- An explicit If/Else node is not yet available but is on our roadmap.
-
- **Current workaround**: Create multiple branches from your step, each starting with a **Filter** action:
-
- ```
- Step 1
- │
- ├── Branch A: Filter (condition = true) → Actions...
- │
- └── Branch B: Filter (condition = false) → Actions...
- ```
-
- Only the branch where the filter condition passes will execute its subsequent actions.
+ <Accordion title="How do I add an If/Else node?">
+ Add an **If/else** action from the **Flow** section of the action picker, the same way you'd add any other action. Configure a condition on the **If** branch, optionally add **Else if** branches with their own conditions, and a final **Else** branch that catches everything else — only the first matching branch runs.
See [How to Use Branches](/user-guide/workflows/capabilities/workflow-branches) for a step-by-step guide.
</Accordion>
diff --git a/packages/twenty-docs/user-guide/workflows/overview.mdx b/packages/twenty-docs/user-guide/workflows/overview.mdx
index fef05fb5385..97e207e00aa 100644
--- a/packages/twenty-docs/user-guide/workflows/overview.mdx
+++ b/packages/twenty-docs/user-guide/workflows/overview.mdx
@@ -46,7 +46,7 @@ After your trigger, add one or more actions:
- **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
+- **AI Agent**: Run intelligent AI tasks
<img src="/images/user-guide/workflows/workflow_actions.png" style={{width:'100%'}}/>