Why Does My n8n Workflow Translate Only One WordPress Page Instead of Iterating Through All?

Below is a checklist of things to verify that should help you ensure that nodes 4 and 5 process every page rather than just the first one:

---

1. Check Node Execution Settings

• Execute Once Option:
  Make sure that neither your translation node (node 4) nor your page creation node (node 5) has the "Execute Once" option enabled. When this option is toggled, the node processes only the first item instead of iterating over all incoming items.

• Multi-Item Processing:
  Confirm that these nodes are configured to process all items rather than running in bulk (single run for all items). In n8n, nodes generally iterate over each incoming item; however, if a node is explicitly set to run only once, that can cause the behavior you’re witnessing.

---

2. Verify Dynamic Expression References

• Dynamic Elements in Expressions:
  Double-check that the dynamic elements (for example, references like {{ $json.<property> }}) in nodes 4 and 5 correctly point to the data from each individual page. An incorrect reference might lead to one page’s data being processed repeatedly.

• Scope of Expression:
  Ensure that the expressions correctly reference values from the current item and are not inadvertently set to a static value (e.g., from the first item of the array).

---

3. Consider Data Splitting

• Using SplitInBatches (Loop Over Items) Node:
  Even though your WP REST API node returns all 34 pages in one go, if the subsequent nodes are not iterating over each item properly, consider inserting a SplitInBatches node between your WP node and node 4. Setting the Batch Size to 1 will enforce iterative processing for each page.

  For example:

  JSONCopied
  {
    "parameters": {
      "batchSize": 1
    },
    "name": "Loop Over Items",
    "type": "n8n-nodes-base.splitInBatches",
    "typeVersion": 3,
    "position": [
      700,
      400
    ]
  }

  This node will guarantee that every page fetched from WordPress is processed one at a time by the downstream nodes.

---

4. Inspect Workflow Connections

• Ensure Proper Chaining:
  Verify that the nodes are correctly chained so that the outputs from the WP REST API node (all pages) are reliably passed to the translation and creation nodes. If there’s a misconfigured connection, only a subset (or just one item) might be forwarded.

---

Summary

In essence, the most likely cause is that nodes 4 and/or 5 are either set to "Execute Once" or are not iterating over the entire set of input items due to a misconfiguration in dynamic expressions or workflow connections. Adjusting these settings or adding a SplitInBatches node should help ensure that all 34 pages are processed as expected.

If after these checks the issue persists, consider examining the node output by adding a simple debug/log node between the steps to verify that all items are flowing through the workflow correctly.

Feel free to ask if you have further questions regarding how to configure these specific nodes in n8n!

Below are some troubleshooting steps and considerations based on n8n's looping and node execution concepts:

1. Verify Node Execution Mode

n8n nodes process multiple items by default. However, if a node (like your translation or page creation node) has the Execute Once parameter enabled, it will run just once rather than once per incoming item. Double-check nodes 4 and 5 to ensure that:

• Execute Once is disabled so they process every item from the previous node.
• The dynamic expressions reference the current item (using expressions like {{$json["fieldName"]}}) rather than a static value.

2. Confirm That the WP REST API Node Returns Multiple Items

Even though you’ve set pagination (limit of 100), make sure the WP REST API node actually outputs all 34 pages as separate items. You can inspect the output by:

• Using a NoOp or Set node immediately after retrieving the pages.
• Checking the execution data to ensure each page is represented as an individual item.

3. Using a Loop Node if Necessary

If your workflow design requires running an action (such as translating for each language on every page), you might need to explicitly create a loop:

• Use the Loop Over Items node to iterate over each page.
• Alternatively, use a SplitInBatches node if you want to process pages in smaller groups. This can also help avoid issues if the following nodes require separate iterations for each item.

4. Check Dynamic Element Configuration

Since you mentioned the dynamic elements in nodes 4 and 5:

• Verify that the expressions correctly map to the current item’s data.
• Be sure that the node’s incoming data is not being merged or reduced to a single item by any preceding node or transformation.

Summary

In short, the issue could be that nodes 4 and 5 are set to Execute Once or are not correctly set up to iterate over multiple incoming items. Verify these node settings and confirm that each previous node is outputting all expected items. Adjusting the workflow to loop over each item—either automatically (by ensuring nodes process multiple items) or by inserting a loop node—should resolve the issue.

Give these steps a try and check the execution logs for additional insights on how many items each node receives during your workflow execution.