I am building a connector for Sentry and using the List an Organization’s SCIM Members endpoint as an example. I want to use dynamic inputs so I’m using a helper flow to do that and it works fine.
I just can’t work out how to assign the correct values to my httpHelper flow to actually use when calling the Sentry API endpoint. Using the Get Multiple cards doesn’t work as I believe the Inputs comes through as an array. I’ve tried to use the Map card as a helper flow to get the values from each input but can’t seem to get that working.
How can I take the values from startIndex, count and filter and then add them into the query?
Thanks
Hi @simonmartin, welcome to the forum!
What data does your httpHelper flow expect?
How does the input look into this action flow?
We have two tutorials about building connectors that might help you:
Hey @maxkatz , thanks for the reply!
I couldn’t attach more than one screenshot previously so here’s the httpHelper.
In regards to the Input - I can’t see a way to display this. The execution history shows now runs, even when I run the whole flow so I can’t see the format of the JSON that is passed into the action flow. Those tutorials don’t help, I’m afraid - they don’t use dynamic input fields from what I can see.
My end goal is to get the JSON to look like the below so I can just use a Get Multiple card to get the values.
{
"startIndex": "0",
"count": "3",
"filter": "active"
}
This is the Dynamic Input group JSON:
[
{
"displayname": "Start Index",
"name": "startIndex",
"type": "Integer",
"required": false
},
{
"displayname": "Count",
"name": "count",
"type": "Integer",
"required": false
},
{
"displayname": "Filter",
"name": "filter",
"type": "Text",
"required": false
}
]
Could you use three static inputs instead of dynamic inputs?
Or does the ‘Count’ field depend on what you select in the ‘Start Index’ field?
You would still need three inputs if you decide to go with dynamic inputs. What is different, the value list depends on the previous field value.
I forgot to share this tutorial:
Well, I wanted to use dynamic inputs because it’s similar to other cards and not all the fields are needed - I think it makes for a nicer user experience. The ‘Count’ field doesn’t depend on the ‘Start Index’ field. I’ve also already read that link you sent but it doesn’t explain the JSON format received into the flow when a user uses the card in production. For example, if someone sets the ‘Count’ to 5 and leaves the others blank, what is the JSON that is received into my List Users flow in connector builder?
You dynamically load the list options, but the output is still a single value. In your case, you would still have three inputs and then map them directly:
The Set Up API Connector Dynamic Input Fields in the Okta Workflows Connector Builder tutorial shows how to set up dynamic inputs for Options, but Inputs work the same way.
This is the last screenshot in the tutorial:
Sorry, still not following! If the user selects Start Index, Count AND Filter, I can’t just drag and drop the values onto an Assign card as it doesn’t format the API call correctly. You can see that from the screenshot here.
So I need to extract the values that they’ve potentially entered for each option and then use that to format the API call correctly. This is why I reference the JSON format that the Action flow receives, I can’t see that so I can’t retrieve the values 
Use the Object - Construct card to create a JSON object:
{
"Start Index": "10",
"Filter": "none",
"Count": "20"
}
I tried that but I don’t know the format of the JSON so just get null values. The JSON isn’t formatted as you mention but because I can’t see it, I don’t know how to pull the values 
Can you try with static inputs first?
Using the flow you shared originally, set up the three inputs. You don’t need the Object - Get Multiple card. Send the three fields to the Object - Construct card.
