diff --git a/content/guides/12.integrations/1.n8n/0.index.md b/content/guides/12.integrations/1.n8n/0.index.md
index 68335682..5adeab58 100644
--- a/content/guides/12.integrations/1.n8n/0.index.md
+++ b/content/guides/12.integrations/1.n8n/0.index.md
@@ -24,7 +24,7 @@ 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
-  
+
 ## Installation
 
 ### Install the Community Node
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..4543ddf9 100644
--- a/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md
+++ b/content/guides/12.integrations/1.n8n/directus-n8n-advanced.md
@@ -41,7 +41,7 @@ Use raw operations when you need complex filters with logical operators (`_and`,
 
 ## 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
diff --git a/content/guides/12.integrations/3.zapier/actions.md b/content/guides/12.integrations/3.zapier/actions.md
index 3876824c..587270cc 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
diff --git a/content/guides/12.integrations/3.zapier/advanced.md b/content/guides/12.integrations/3.zapier/advanced.md
index 1f6fface..51f6ddb6 100644
--- a/content/guides/12.integrations/3.zapier/advanced.md
+++ b/content/guides/12.integrations/3.zapier/advanced.md
@@ -185,6 +185,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**