"Next" button for pagination is not always available. In some cases, you may have to click through the page numbers to view all the available contents.
So in this case, to extract multiple pages of data, you will need to modify the XPath of "Click to pagination" step to make sure the next page number in the line is always located correctly.
(e.g. if you are on page 1 then you would want to click page 2, if you are on page 2, then you would want to click page 3, so on and so forth. )
There are two general steps:
Step 1 - Click on page 1，then select "Loop click single element".
Step 2 - Modify the auto-generated XPath to one that locates the next page in the line.
XPath syntax "following-sibling" is used most often for this case to select the siblings after the current node (Learn more about locating elements with XPath ).
Here’s an example:
Using Firefox XPath tool (Only available for Firefox 54 or earlier versions), you can easily find the XPath of the first-page element (check Locate elements with XPath for detailed instructions).
So for this example, the XPath for the first-page element "1" is
Then looking at the HTML codes you can easily spot where "page 2" is at, usually somewhere close to the first-page element.
Using XPath Syntax "following-sibling" which tracks for the next following node down the line, you can now modify the auto-generated XPath for the page-1 element to one that tracks the page following it (page-2 in this case). So here the correct XPath that will always locate the next page following the current page is:
By adding "/following-sibling::a" to the end of the auto-generated XPath, it now looks for the first href element (a) following the first-page element.
When you have the new XPath ready and tested, replace the auto-generated XPath for the pagination loop with the new XPath. Click "OK" to save the setting.
Now, check how the new XPath is working by clicking through the pagination steps in the workflow. If you have the next page loaded correctly every time you click "click to pagination", then you are sure that the new XPath is the right one.