Lindy Community Icon

Home
Events

00 Announcements
01 General
02 Support
03 Bugs
04 Requests and Feedback
05 Share Your Lindy
06 Intros

Community Guidelines

Troubleshooting Guide

Powered by Tightknit

Workaround for NextPageToken in Lead Gen Workflow using Search Places | Lindy Community

Workaround for NextPageToken in Lead Gen Workflow using Search Places

·Sep 24, 2025 08:50 PM·

I’m building a lead gen worflow with Search Places action. The API has pagination functionality where I need to supply a nextPageToken in subsequent requests, https://developers.google.com/maps/documentation/places/web-service/text-search#pagetoken. But the action form doesn’t have a parameter for that. How can I workaround this?

2 comments

· Sorted by Oldest

Alon J.
·
·
Hmmm, I'm not quite sure to be honest. Marvin A. Ethan K. Do either of you have any thoughts on this? 🙏
Adrian G.
·
·
I decided to switch to generic Http action. But the Search Places action should support nextPageToken because only 60 records max are returned.