From 971ce6a68878e504a89960d44263142ff02f176a Mon Sep 17 00:00:00 2001 From: Lindsey Zylstra Date: Thu, 2 Jul 2026 14:13:43 -0700 Subject: [PATCH 1/3] V12 integrations updates --- .../guides/12.integrations/1.n8n/0.index.md | 10 +++- .../1.n8n/directus-n8n-actions.md | 12 +++++ .../1.n8n/directus-n8n-advanced.md | 49 +++++++++++++++++-- .../12.integrations/3.zapier/0.index.md | 8 +++ .../12.integrations/3.zapier/actions.md | 36 ++++++++++++++ .../12.integrations/3.zapier/advanced.md | 9 +++- .../12.integrations/3.zapier/triggers.md | 1 + 7 files changed, 118 insertions(+), 7 deletions(-) diff --git a/content/guides/12.integrations/1.n8n/0.index.md b/content/guides/12.integrations/1.n8n/0.index.md index 68335682..538fd43e 100644 --- a/content/guides/12.integrations/1.n8n/0.index.md +++ b/content/guides/12.integrations/1.n8n/0.index.md @@ -24,7 +24,15 @@ The Directus community node provides two components: - **Directus Node**: Perform CRUD operations on items, users, and files - **Directus Trigger Node**: Automatically start workflows when events occur in Directus - + +## Directus v12 compatibility + +The Directus community node works with Directus 10 through 12, including Directus Cloud and self-hosted instances. + +For most workflows, especially collections without content versioning enabled, no changes are needed when you upgrade to Directus v12. + +If you use content versioning, see [Content Versioning](/guides/integrations/n8n/directus-n8n-advanced#content-versioning) for how to read and update draft content from n8n. + ## Installation ### Install the Community Node diff --git a/content/guides/12.integrations/1.n8n/directus-n8n-actions.md b/content/guides/12.integrations/1.n8n/directus-n8n-actions.md index 07e085b9..6785045f 100644 --- a/content/guides/12.integrations/1.n8n/directus-n8n-actions.md +++ b/content/guides/12.integrations/1.n8n/directus-n8n-actions.md @@ -76,6 +76,18 @@ Items are content entries in your Directus collections (blog posts, products, pa - Collection: `posts` - Fields: `title`, `content`, `status` +::callout{icon="i-lucide-triangle-alert" color="warning"} +**Content versioning (Directus v12+)** +
+On collections with content versioning enabled, Directus v12 blocks direct updates to published items. Running **Update** on a published item may return an error. + +To update draft content instead: +- Use **Get (Raw JSON)** with `{"version": "draft"}` to read the draft state (see the [Advanced guide](/guides/integrations/n8n/directus-n8n-advanced#content-versioning)) +- Use an **HTTP Request** node to call the Directus [Versions API](https://directus.com/docs/api/versions) directly, since neither **Update** nor **Update (Raw JSON)** can write to a draft + +Collections without versioning enabled aren't affected. Use **Update** as normal. +:: + ### Users #### Invite a User diff --git a/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md b/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md index 0ac1b42a..5d3f273d 100644 --- a/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md +++ b/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md @@ -36,12 +36,12 @@ Quick reference of all available raw operations organized by resource type: ::callout{icon="i-lucide-lightbulb"} **When to Use Raw Operations** -Use raw operations when you need complex filters with logical operators (`_and`, `_or`), relational field filtering, advanced query parameters (aggregation, search, etc.), or full control over the JSON payload structure. +Use raw operations when you need complex filters with logical operators (`_and`, `_or`), relational field filtering, advanced query parameters (aggregation, search, etc.), reading a specific content version (`draft` or `published`), or full control over the JSON payload structure. :: ## Using Raw Operations -Raw operations work similarly to their standard counterparts, but instead of using the node's form fields, you provide all data in the **JSON Data** field as a JSON object. +Raw operations work similarly to their standard counterparts, but instead of using the node's form fields, you provide data as a JSON object: the **JSON Data** field for Create/Update, or the **Query Parameters** field for Get/Get Many. ### Setting Up a Raw Operation @@ -49,7 +49,7 @@ Raw operations work similarly to their standard counterparts, but instead of usi 2. Set **Resource** to Item, User, or File 3. Select a **Raw JSON** operation (e.g., "Get Many (Raw JSON)", "Create (Raw JSON)") 4. For Items operations, select the **Collection** -5. Enter your JSON data in the **JSON Data** field +5. Enter your data in the **JSON Data** field (Create/Update) or the **Query Parameters** field (Get/Get Many) 6. For Get and Update operations, provide the **Item ID** if needed ::callout{icon="i-lucide-triangle-alert" color="warning"} @@ -114,7 +114,7 @@ Update items with complex data structures: ## Using Filters with Raw Operations -Raw operations allow you to use Directus's complete filter syntax. Specify filters in the `filter` parameter of your **JSON Data** field. +Raw operations allow you to use Directus's complete filter syntax. Specify filters in the `filter` parameter of the **Query Parameters** field (Get Many). ::callout{icon="i-lucide-info"} **Filter Documentation** @@ -157,7 +157,7 @@ For complete filter syntax, operators, and examples, see the [Directus Filter Ru ## Query Parameters -Raw operations support all Directus query parameters. Include them in your JSON Data alongside filters: +Get (Raw JSON) and Get Many (Raw JSON) support all Directus query parameters. Include them in the **Query Parameters** field alongside filters: **Common query parameters:** ```json @@ -193,6 +193,45 @@ Raw operations support all Directus query parameters. Include them in your JSON For complete query parameter documentation, see the [Directus Query Parameters documentation](https://directus.com/docs/guides/connect/query-parameters). :: +## Content Versioning + +### When it applies + +Only collections with content versioning enabled in Directus use the `version` query parameter. Non-versioned collections don't need it. + +::callout{icon="i-lucide-triangle-alert" color="warning"} +**Only use `version` on versioned collections** +Don't add it to every request by default. It's only relevant when content versioning is enabled for that collection. +:: + +### Reading versioned content + +Use **Get (Raw JSON)** and pass `version` in the **Query Parameters** field. The `version` parameter only applies to single-item retrieval, so it has no effect on **Get Many (Raw JSON)**: + +```json +{ + "version": "draft" +} +``` + +Or for the published version: + +```json +{ + "version": "published" +} +``` + +`version: "main"` still works for backward compatibility, but `published` is preferred. See [Directus v12 breaking changes](https://directus.com/docs/releases/breaking-changes/version-12#versionmain-renamed-to-versionpublished). + +### Updating draft content + +Directus doesn't accept a `version` parameter on item updates. Draft edits go through the dedicated [Versions API](https://directus.com/docs/api/versions) instead: `POST /versions/{id}/save` to save changes to a version, then `POST /versions/{id}/promote` to publish it. + +Neither **Update** nor **Update (Raw JSON)** can call these endpoints. Use an **HTTP Request** node to call them directly with your Directus credentials. + +See [Content Versioning](https://directus.com/docs/guides/content/content-versioning) for the full versioning workflow in Directus. + ## Working with Relations When using **Create (Raw JSON)** or **Update (Raw JSON)**, you can include related data directly in your JSON: diff --git a/content/guides/12.integrations/3.zapier/0.index.md b/content/guides/12.integrations/3.zapier/0.index.md index 0ac00f25..9d09c9b0 100644 --- a/content/guides/12.integrations/3.zapier/0.index.md +++ b/content/guides/12.integrations/3.zapier/0.index.md @@ -24,6 +24,14 @@ The Directus Zapier integration provides two main components: - **Directus Actions**: Perform CRUD operations on items, users, and files - **Directus Triggers**: Automatically start Zaps when events occur in Directus +## Directus v12 Compatibility + +The Directus Zapier integration is compatible with Directus v12. Most existing Zaps continue to work without changes. + +The only scenario that needs attention is **Update Item** on collections where you've enabled content versioning (**Settings > Data Model > select collection > Enable Versions**). In that case, updating published items from Zapier may fail because Directus v12 requires edits to go through a draft version. + +See [Content Versioning](/guides/integrations/zapier/actions#content-versioning-directus-v12) for workarounds. + ## Getting Started ### Connect Your Directus Account diff --git a/content/guides/12.integrations/3.zapier/actions.md b/content/guides/12.integrations/3.zapier/actions.md index 3876824c..e4afd551 100644 --- a/content/guides/12.integrations/3.zapier/actions.md +++ b/content/guides/12.integrations/3.zapier/actions.md @@ -104,6 +104,8 @@ The **Filter (JSON)** field in Find actions supports Directus's complete filter } ``` +This example assumes a string `status` field. Collections created in Directus v12 may use a boolean `archived` field instead. Adjust your filter to match your schema, for example `{"archived": {"_eq": false}}`. + ## Resource-Specific Operations ### Items @@ -115,6 +117,30 @@ Items are content entries in your Directus collections (blog posts, products, pa Fields are automatically discovered from your Directus schema and shown in the action configuration. You can map data from previous steps using the dropdown menus. :: +### Content Versioning (Directus v12+) + +Content versioning is opt-in per collection. If you haven't enabled it, skip this section. **Update Item** works as usual. + +When versioning is enabled, Directus v12 treats the published item as read-only. Edits must go through a version (typically the draft), using the dedicated [Versions API](https://directus.com/docs/api/versions) rather than the standard Items API. + +::callout{icon="i-lucide-triangle-alert" color="warning"} +**Zapier limitation** +
+**Update Item** and **Item Raw Request** both call the standard Items endpoint, so they work for published items but not drafts. Use one of the workarounds below. +:: + + + +**Workarounds for versioned collections:** + +- Edit and publish content in the Directus Studio instead of Zapier +- Call the Versions API directly from outside Zapier (`POST /versions/{id}/save` to save a draft, `POST /versions/{id}/promote` to publish it) +- Restructure your Zap to avoid updating published items in versioned collections + +**Find Items** returns published content by default. Reading a specific version, like draft, requires the Directus API `version` query parameter, which isn't available in the standard **Find Items** action. + +Publishing drafts isn't available through the Zapier integration. Use the Directus Studio or the [Versions API](https://directus.com/docs/api/versions). + ### Users #### Invite User @@ -236,6 +262,16 @@ If you get errors: 3. **Connection Errors**: Make sure your Directus URL is correct and accessible (must include `https://`, no trailing slash) +### Update Item fails on Directus v12 + +**Symptom**: **Update Item** returns an error on one collection, but other collections work fine. + +**Likely cause**: The collection has content versioning enabled, and you're trying to update a published item. Directus v12 requires edits to go through a draft version, and the Zapier integration doesn't support the `version` query parameter. + +**Fix**: Use one of the workarounds in [Content Versioning (Directus v12+)](#content-versioning-directus-v12), typically editing in the Directus Studio or using the Directus API directly. + +If the collection doesn't use versioning, the issue is likely unrelated. Check permissions, the item ID, and your connection settings. + ### Getting Help If you encounter issues: diff --git a/content/guides/12.integrations/3.zapier/advanced.md b/content/guides/12.integrations/3.zapier/advanced.md index 1f6fface..2922f1d9 100644 --- a/content/guides/12.integrations/3.zapier/advanced.md +++ b/content/guides/12.integrations/3.zapier/advanced.md @@ -13,7 +13,7 @@ This guide covers advanced Directus features in Zapier, including raw request ac ## Raw Request Actions -Raw Request actions provide full HTTP method control for Items, Users, and Files. These actions allow you to use Directus's native JSON syntax for filters, query parameters, and data manipulation. +Raw Request actions provide full HTTP method control for Items, Users, and Files, and let you use Directus's native JSON syntax for the request body. ## Available Raw Request Actions @@ -81,6 +81,11 @@ Ensure your Directus API token has the correct permissions for the resource and **DELETE** - Delete items by ID or using Filter (JSON) for bulk deletion +::callout{icon="i-lucide-info"} +**Content versioning** +Directus doesn't accept a `version` parameter on this endpoint. Updating a draft in a versioned collection requires the dedicated [Versions API](https://directus.com/docs/api/versions) (`POST /versions/{id}/save`), which **Item Raw Request** can't call since it's scoped to the standard Items endpoint. See [Content Versioning](/guides/integrations/zapier/actions#content-versioning-directus-v12) for workarounds. +:: + ### Users - Raw Request **POST** - Create users with full JSON control: @@ -185,6 +190,8 @@ For bulk operations: } ``` +Whether to filter on `status` or `archived` depends on your collection's schema. Collections created in Directus v12 may use the boolean `archived` field instead of a string `status` field. + --- ## Next Steps diff --git a/content/guides/12.integrations/3.zapier/triggers.md b/content/guides/12.integrations/3.zapier/triggers.md index caa06bbe..73ae3356 100644 --- a/content/guides/12.integrations/3.zapier/triggers.md +++ b/content/guides/12.integrations/3.zapier/triggers.md @@ -70,6 +70,7 @@ You can add Filter steps after the trigger to only process specific events: - Check if `status` equals `published` before sending notifications - Filter by collection or field values - Only process certain types of files +- On collections using a boolean `archived` field instead of `status`, filter where `archived` equals `false` ::callout{icon="i-lucide-info"} **Filtering Tip** From d6276462264ddba9a587ce1007ba0246ce3898da Mon Sep 17 00:00:00 2001 From: Lindsey Zylstra Date: Mon, 6 Jul 2026 15:13:23 -0700 Subject: [PATCH 2/3] Remove versioning info --- .../guides/12.integrations/1.n8n/0.index.md | 6 +-- .../1.n8n/directus-n8n-actions.md | 12 ------ .../1.n8n/directus-n8n-advanced.md | 41 +------------------ .../12.integrations/3.zapier/0.index.md | 6 +-- .../12.integrations/3.zapier/actions.md | 34 --------------- .../12.integrations/3.zapier/advanced.md | 7 +--- 6 files changed, 4 insertions(+), 102 deletions(-) diff --git a/content/guides/12.integrations/1.n8n/0.index.md b/content/guides/12.integrations/1.n8n/0.index.md index 538fd43e..19265a50 100644 --- a/content/guides/12.integrations/1.n8n/0.index.md +++ b/content/guides/12.integrations/1.n8n/0.index.md @@ -27,11 +27,7 @@ The Directus community node provides two components: ## Directus v12 compatibility -The Directus community node works with Directus 10 through 12, including Directus Cloud and self-hosted instances. - -For most workflows, especially collections without content versioning enabled, no changes are needed when you upgrade to Directus v12. - -If you use content versioning, see [Content Versioning](/guides/integrations/n8n/directus-n8n-advanced#content-versioning) for how to read and update draft content from n8n. +The Directus community node works with Directus 10 through 12, including Directus Cloud and self-hosted instances. No changes are needed when you upgrade to Directus v12. ## Installation diff --git a/content/guides/12.integrations/1.n8n/directus-n8n-actions.md b/content/guides/12.integrations/1.n8n/directus-n8n-actions.md index 6785045f..07e085b9 100644 --- a/content/guides/12.integrations/1.n8n/directus-n8n-actions.md +++ b/content/guides/12.integrations/1.n8n/directus-n8n-actions.md @@ -76,18 +76,6 @@ Items are content entries in your Directus collections (blog posts, products, pa - Collection: `posts` - Fields: `title`, `content`, `status` -::callout{icon="i-lucide-triangle-alert" color="warning"} -**Content versioning (Directus v12+)** -
-On collections with content versioning enabled, Directus v12 blocks direct updates to published items. Running **Update** on a published item may return an error. - -To update draft content instead: -- Use **Get (Raw JSON)** with `{"version": "draft"}` to read the draft state (see the [Advanced guide](/guides/integrations/n8n/directus-n8n-advanced#content-versioning)) -- Use an **HTTP Request** node to call the Directus [Versions API](https://directus.com/docs/api/versions) directly, since neither **Update** nor **Update (Raw JSON)** can write to a draft - -Collections without versioning enabled aren't affected. Use **Update** as normal. -:: - ### Users #### Invite a User diff --git a/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md b/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md index 5d3f273d..4543ddf9 100644 --- a/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md +++ b/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md @@ -36,7 +36,7 @@ Quick reference of all available raw operations organized by resource type: ::callout{icon="i-lucide-lightbulb"} **When to Use Raw Operations** -Use raw operations when you need complex filters with logical operators (`_and`, `_or`), relational field filtering, advanced query parameters (aggregation, search, etc.), reading a specific content version (`draft` or `published`), or full control over the JSON payload structure. +Use raw operations when you need complex filters with logical operators (`_and`, `_or`), relational field filtering, advanced query parameters (aggregation, search, etc.), or full control over the JSON payload structure. :: ## Using Raw Operations @@ -193,45 +193,6 @@ Get (Raw JSON) and Get Many (Raw JSON) support all Directus query parameters. In For complete query parameter documentation, see the [Directus Query Parameters documentation](https://directus.com/docs/guides/connect/query-parameters). :: -## Content Versioning - -### When it applies - -Only collections with content versioning enabled in Directus use the `version` query parameter. Non-versioned collections don't need it. - -::callout{icon="i-lucide-triangle-alert" color="warning"} -**Only use `version` on versioned collections** -Don't add it to every request by default. It's only relevant when content versioning is enabled for that collection. -:: - -### Reading versioned content - -Use **Get (Raw JSON)** and pass `version` in the **Query Parameters** field. The `version` parameter only applies to single-item retrieval, so it has no effect on **Get Many (Raw JSON)**: - -```json -{ - "version": "draft" -} -``` - -Or for the published version: - -```json -{ - "version": "published" -} -``` - -`version: "main"` still works for backward compatibility, but `published` is preferred. See [Directus v12 breaking changes](https://directus.com/docs/releases/breaking-changes/version-12#versionmain-renamed-to-versionpublished). - -### Updating draft content - -Directus doesn't accept a `version` parameter on item updates. Draft edits go through the dedicated [Versions API](https://directus.com/docs/api/versions) instead: `POST /versions/{id}/save` to save changes to a version, then `POST /versions/{id}/promote` to publish it. - -Neither **Update** nor **Update (Raw JSON)** can call these endpoints. Use an **HTTP Request** node to call them directly with your Directus credentials. - -See [Content Versioning](https://directus.com/docs/guides/content/content-versioning) for the full versioning workflow in Directus. - ## Working with Relations When using **Create (Raw JSON)** or **Update (Raw JSON)**, you can include related data directly in your JSON: diff --git a/content/guides/12.integrations/3.zapier/0.index.md b/content/guides/12.integrations/3.zapier/0.index.md index 9d09c9b0..9182c81e 100644 --- a/content/guides/12.integrations/3.zapier/0.index.md +++ b/content/guides/12.integrations/3.zapier/0.index.md @@ -26,11 +26,7 @@ The Directus Zapier integration provides two main components: ## Directus v12 Compatibility -The Directus Zapier integration is compatible with Directus v12. Most existing Zaps continue to work without changes. - -The only scenario that needs attention is **Update Item** on collections where you've enabled content versioning (**Settings > Data Model > select collection > Enable Versions**). In that case, updating published items from Zapier may fail because Directus v12 requires edits to go through a draft version. - -See [Content Versioning](/guides/integrations/zapier/actions#content-versioning-directus-v12) for workarounds. +The Directus Zapier integration is compatible with Directus v12. Existing Zaps continue to work without changes. ## Getting Started diff --git a/content/guides/12.integrations/3.zapier/actions.md b/content/guides/12.integrations/3.zapier/actions.md index e4afd551..587270cc 100644 --- a/content/guides/12.integrations/3.zapier/actions.md +++ b/content/guides/12.integrations/3.zapier/actions.md @@ -117,30 +117,6 @@ Items are content entries in your Directus collections (blog posts, products, pa Fields are automatically discovered from your Directus schema and shown in the action configuration. You can map data from previous steps using the dropdown menus. :: -### Content Versioning (Directus v12+) - -Content versioning is opt-in per collection. If you haven't enabled it, skip this section. **Update Item** works as usual. - -When versioning is enabled, Directus v12 treats the published item as read-only. Edits must go through a version (typically the draft), using the dedicated [Versions API](https://directus.com/docs/api/versions) rather than the standard Items API. - -::callout{icon="i-lucide-triangle-alert" color="warning"} -**Zapier limitation** -
-**Update Item** and **Item Raw Request** both call the standard Items endpoint, so they work for published items but not drafts. Use one of the workarounds below. -:: - - - -**Workarounds for versioned collections:** - -- Edit and publish content in the Directus Studio instead of Zapier -- Call the Versions API directly from outside Zapier (`POST /versions/{id}/save` to save a draft, `POST /versions/{id}/promote` to publish it) -- Restructure your Zap to avoid updating published items in versioned collections - -**Find Items** returns published content by default. Reading a specific version, like draft, requires the Directus API `version` query parameter, which isn't available in the standard **Find Items** action. - -Publishing drafts isn't available through the Zapier integration. Use the Directus Studio or the [Versions API](https://directus.com/docs/api/versions). - ### Users #### Invite User @@ -262,16 +238,6 @@ If you get errors: 3. **Connection Errors**: Make sure your Directus URL is correct and accessible (must include `https://`, no trailing slash) -### Update Item fails on Directus v12 - -**Symptom**: **Update Item** returns an error on one collection, but other collections work fine. - -**Likely cause**: The collection has content versioning enabled, and you're trying to update a published item. Directus v12 requires edits to go through a draft version, and the Zapier integration doesn't support the `version` query parameter. - -**Fix**: Use one of the workarounds in [Content Versioning (Directus v12+)](#content-versioning-directus-v12), typically editing in the Directus Studio or using the Directus API directly. - -If the collection doesn't use versioning, the issue is likely unrelated. Check permissions, the item ID, and your connection settings. - ### Getting Help If you encounter issues: diff --git a/content/guides/12.integrations/3.zapier/advanced.md b/content/guides/12.integrations/3.zapier/advanced.md index 2922f1d9..51f6ddb6 100644 --- a/content/guides/12.integrations/3.zapier/advanced.md +++ b/content/guides/12.integrations/3.zapier/advanced.md @@ -13,7 +13,7 @@ This guide covers advanced Directus features in Zapier, including raw request ac ## Raw Request Actions -Raw Request actions provide full HTTP method control for Items, Users, and Files, and let you use Directus's native JSON syntax for the request body. +Raw Request actions provide full HTTP method control for Items, Users, and Files. These actions allow you to use Directus's native JSON syntax for filters, query parameters, and data manipulation. ## Available Raw Request Actions @@ -81,11 +81,6 @@ Ensure your Directus API token has the correct permissions for the resource and **DELETE** - Delete items by ID or using Filter (JSON) for bulk deletion -::callout{icon="i-lucide-info"} -**Content versioning** -Directus doesn't accept a `version` parameter on this endpoint. Updating a draft in a versioned collection requires the dedicated [Versions API](https://directus.com/docs/api/versions) (`POST /versions/{id}/save`), which **Item Raw Request** can't call since it's scoped to the standard Items endpoint. See [Content Versioning](/guides/integrations/zapier/actions#content-versioning-directus-v12) for workarounds. -:: - ### Users - Raw Request **POST** - Create users with full JSON control: From a11fa37d44e9fe58f7cfdae3e3b3f94abd0ff900 Mon Sep 17 00:00:00 2001 From: Lindsey Zylstra Date: Wed, 8 Jul 2026 15:24:41 -0700 Subject: [PATCH 3/3] Remove v12 callout --- content/guides/12.integrations/1.n8n/0.index.md | 4 ---- content/guides/12.integrations/3.zapier/0.index.md | 4 ---- 2 files changed, 8 deletions(-) diff --git a/content/guides/12.integrations/1.n8n/0.index.md b/content/guides/12.integrations/1.n8n/0.index.md index 19265a50..5adeab58 100644 --- a/content/guides/12.integrations/1.n8n/0.index.md +++ b/content/guides/12.integrations/1.n8n/0.index.md @@ -25,10 +25,6 @@ The Directus community node provides two components: - **Directus Node**: Perform CRUD operations on items, users, and files - **Directus Trigger Node**: Automatically start workflows when events occur in Directus -## Directus v12 compatibility - -The Directus community node works with Directus 10 through 12, including Directus Cloud and self-hosted instances. No changes are needed when you upgrade to Directus v12. - ## Installation ### Install the Community Node diff --git a/content/guides/12.integrations/3.zapier/0.index.md b/content/guides/12.integrations/3.zapier/0.index.md index 9182c81e..0ac00f25 100644 --- a/content/guides/12.integrations/3.zapier/0.index.md +++ b/content/guides/12.integrations/3.zapier/0.index.md @@ -24,10 +24,6 @@ The Directus Zapier integration provides two main components: - **Directus Actions**: Perform CRUD operations on items, users, and files - **Directus Triggers**: Automatically start Zaps when events occur in Directus -## Directus v12 Compatibility - -The Directus Zapier integration is compatible with Directus v12. Existing Zaps continue to work without changes. - ## Getting Started ### Connect Your Directus Account