Before
A team member likely had to request subscriber records page by page, review the returned users, and copy each person’s details into a spreadsheet. Repeating the lookup and data-entry process created ongoing effort and increased the chance of omissions or inconsistent formatting.
How it works
- An incoming email triggers the workflow and establishes a five-page collection cycle.
- The workflow retrieves up to 100 WordPress subscriber accounts per page and processes each returned user.
- Each subscriber’s first name, last name, and email address is appended to the spreadsheet as a new row.
Workflow details
- Trigger: An incoming email event starts the workflow and initiates the subscriber export.
- Pagination: The workflow cycles through five predefined pages, requesting up to 100 subscriber accounts per page from WordPress.
- Data collection: Each returned subscriber is processed individually, with the workflow extracting the first name, last name, and email address.
- Spreadsheet update: The subscriber details are appended as rows to a spreadsheet, creating a consolidated list of existing subscribers for further use.
What changed
Subscriber collection now starts from an email event, retrieves the configured pages automatically, and writes each user’s core contact details directly to the spreadsheet without requiring manual copying between the user directory and the spreadsheet.
Work removed
Manually requesting subscriber pages, reviewing users one by one, copying first names, last names, and email addresses, and appending those details to the spreadsheet.
Expected outcome
A repeatable subscriber export covering up to 500 records per run, based on five pages of up to 100 users each, with manual lookup and data-entry actions removed.
