Respond.io Integration: Custom fields not showing on subsequent modules

I’m trying to retrieve information about my Respond .io contacts. I have multiple custom fields, and I can see them on the Respond .io module, but these fields are not visible to use as input into subsequent modules.
I’ve tried “Run Once”; “Run this module only” for all modules, and on different workflows, but for some reason it only brings up one custom fields.

In other scenarios that are published and On, this didn’t happen. I’m doing the exact same thing as I did then.
I’ve added my Blueprint too.

Do you know how I can get those custom fields to pull through to the next modules?

None of my Respond.io fields are hidden.



blueprint (4).json (6.2 KB)

Welcome to the Make Community!

You can use the built-in functions map and get (or first) to access variables within an array.

To do this, you can use the built-in function map

{{ map(complex array; key;[key for filtering];[possible values for filtering separated by a comma]) }}

and the built-in function get

{{ get(object or array; path) }}

e.g.:

{{ first(map(7.custom_fields; "value"; "name"; "onboarding_survey_score")) }}

(copy-paste the above into the field, or type it exactly as shown)

For more information, the function’s documentation can be found in the Help Centre and the “Mapping with Arrays” link below. You should also complete the tutorials in the Make Academy, especially Using get() and map() functions.

Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —

Getting Started

Help Centre Basics

Articles & Videos

Hope this helps! Let me know if there are any further questions or issues.

@samliew

Thanks, Sam
I really appreciate you getting back to me so quickly!

My confusion is that I used to be able to see all custom fields in subsequent modules, just as I am seeing it in the Respond module
in the screenshot attached.
I’ve used it like this in other scenarios, such as the one I’ve attached to my reply here.

blueprint (5).json (8.8 KB)