API Response and HTTPS

I'm developing a workflow to identify individuals matching an ideal client profile (ICP) and store their information in Airtable. The process begins with an Airtable table named ICP_Parameter, which serves as the input source. This table contains client details used as parameters for an API request to the Apollo.io People Search endpoint. The data retrieved from the API will then be saved into a corresponding Airtable table; for instance, if the target audience is "coaches," the data will populate the "coaches" table.

The primary challenge arises because the ICP_Parameter table can accommodate multiple audience types. If I utilize a single HTTP Request node, each distinct audience type is treated as a separate item within that node. Since Apollo.io does not permit the addition of custom fields or metadata to its payload, I am unable to implement routing based on ICP_Type.

As a workaround, I would need to create an individual HTTP Request node for every audience type. This approach significantly hinders the workflow's scalability. Each time a new audience is introduced, I would have to duplicate nodes, manage rate limits, and handle pagination, thereby increasing the workflow's complexity and leading to substantial node duplication.

If there's a more efficient method to achieve this, or if anyone has encountered and resolved a similar issue, I would greatly appreciate any suggestions!