I’m working on a workflow to search for people who fit an ideal client profile (ICP) and store their details in Airtable. There will be Airtable table called ICP_Parameter thatwill serve as input, holding client details that act as parameters for an API call to the Apollo.io People Search endpoint. The returned data will be stored in the corresponding Airtable table—for example, if the audience is “coaches,” then the data will go into the “coaches” table.
The challenge is that the table can hold multiple audiences, and if I use a single HTTP Request node, each audience becomes a new item in that node. Since Apollo.io doesn’t support adding custom fields or metadata to the payload, I can’t route based on ICP_Type.
As a workaround, I’d need to create a separate HTTP Request node for each audience type, which makes the workflow less scalable. Every time a new audience is added, I’d need to duplicate nodes, check rate limits, and handle pagination, which increases the workflow’s complexity and node duplication.
If there’s a more efficient solution or if someone has faced a similar issue, I’d appreciate any suggestions!