Working with my first HTTP GET and I don't know what to do with the multiple results I'm getting

[Expiscornovus]

Hi @ImprintGroup,

It depends a bit on what you want to do with the results. You could for example use a Select action to only retrieve certain properties of each item of the set of results.

Can you share a screenshot of what you currently have as a flow and can you also describe what you want to achieve with the flow? We might be able to adapt an example to your situation and help you out.

[ImprintGroup]

Thank you for commenting!

Since posting I have made a little progress on this flow. Here is my use case.

We have a time tracking platform in which we enter Clients and then Projects for Clients. Our whole team is in the platform as users and we have various tags for types of work being done. Presently, when a new client or project is taken on it is entered into our CRM. I receive a notification of this new entry and have to take that and enter it manually into the time tracking platform so that the team can start coding their hours to the project. I'm trying to automate the addition of the projects to the time tracking platform. They have an API.

Here is how far I've made it in my quest.

When the new record is created in the CRM SQL database it starts the flow. I take information from the SQL record and set variables that I will need to eventually pass along to the time tracking platform.

The initial new record is created at the project level in the CRM and I need to retrieve the corresponding client that the project is for. That is the Get Rows step followed by initializing a variable for the client name that I'll need later. I do this with an initialize variable that I leave blank except for naming. Then I run a Set Variable that ends up in an Apply to Each (even though I'm just dealing with a single client name at this point). I set the variable to be the result of looking up the client name.

Now I get to the HTTP GET from the time tracking API. The API is a little strange to me in terms of what I have to send for a complete PUT command to create the new project there. For one, we attach all staff (40+) to each project so that they have access to code their time. If we didn't do this I would periodically get messages to have people added so they can code hours. So we just do everyone. In the PUT command I will have send the time tracking employee ID for each staff person I want to attach to the project. There is no "all" option.

Right now, my HTTP GET is sitting at pulling a list of all active projects so that I can search them for a match to the project name that I get in my very first step. I'm parsing the JSON from the HTTP GET and filtering the array by the project name from the CRM. This is working succesfully for a few days now.

Now I"m about to branch to start putting together the data needed for the PUT to create the new project assuming the outcome of the filter array is false for a match.

So, now I need to do another GET to pull all of the staff records. I know I'll be able to do that. Once I get that array of data I don't know what to do to pull from that the user IDs and hour_rate to make another array that I'll send as a part of the body in my PUT.

Here is the users requirement for the API PUT: Specifies the project users. It should be an array of users, with numerical user IDs and an hour_rate. For example: "users": [{ "user_id": 175551, "hour_rate": 25.0 },{ "user_id": 117861, "hour_rate": 27.0 }]

So this is where I'm stuck.

Here is a small sample of the array I get when I list all users from the API. It's the "id" and "default_hour_rate" that I need to put into an array in the PUT body to send.

[
{
"id": 2052738,
"email": "removed",
"name": "removed",
"active": true,
"day_view_onboarded": true,
"memory_onboarded": true,
"created_at": 1650943167,
"updated_at": 1661920649,
"last_received_memories_date": "2022-08-30",
"sign_in_count": 11,
"external_id": null,
"time_zone": "America/Los_Angeles",
"memory_retention_days": null,
"avatar": {},
"type": "User",
"work_days": "MON,TUE,WED,THU,FRI",
"weekdays": "MO,TU,WE,TH,FR",
"weekly_capacity": 40.0,
"user_level": "employee",
"admin": false,
"hide_hourly_rate": false,
"hide_internal_hourly_rate": true,
"deleted": false,
"default_hour_rate": 0.0,
"internal_hour_rate": 0.0,
"role_id": 1135466,
"role": {
"id": 1135466,
"name": "employee"
}
},
{
"id": 2051692,
"email": "removed",
"name": "removed",
"active": true,
"day_view_onboarded": true,
"memory_onboarded": true,
"created_at": 1650467932,
"updated_at": 1661918984,
"last_received_memories_date": "2022-08-30",
"sign_in_count": 23,
"external_id": null,
"time_zone": "America/Los_Angeles",
"memory_retention_days": null,
"avatar": {},
"type": "User",
"work_days": "MON,TUE,WED,THU,FRI",
"weekdays": "MO,TU,WE,TH,FR",
"weekly_capacity": 40.0,
"user_level": "employee",
"admin": false,
"hide_hourly_rate": false,
"hide_internal_hourly_rate": true,
"deleted": false,
"default_hour_rate": 15.0,
"internal_hour_rate": 0.0,
"role_id": 1135466,
"role": {
"id": 1135466,
"name": "employee"
}
},
{
"id": 2052730,
"email": "removed",
"name": "removed",
"active": true,
"day_view_onboarded": true,
"memory_onboarded": true,
"created_at": 1650943166,
"updated_at": 1661904385,
"last_received_memories_date": "2022-08-31",
"sign_in_count": 11,
"external_id": null,
"time_zone": "America/Denver",
"memory_retention_days": null,
"avatar": {},
"type": "User",
"work_days": "MON,TUE,WED,THU,FRI",
"weekdays": "MO,TU,WE,TH,FR",
"weekly_capacity": 40.0,
"user_level": "employee",
"admin": false,
"hide_hourly_rate": false,
"hide_internal_hourly_rate": true,
"deleted": false,
"default_hour_rate": 0.0,
"internal_hour_rate": 0.0,
"role_id": 1135466,
"role": {
"id": 1135466,
"name": "employee"
}
},
{
"id": 2045239,
"email": "removed",
"name": "removed",
"active": true,
"day_view_onboarded": true,
"memory_onboarded": true,
"created_at": 1645433463,
"updated_at": 1661904072,
"last_received_memories_date": "2022-08-31",
"sign_in_count": 7,
"external_id": null,
"time_zone": "America/Denver",
"memory_retention_days": null,
"avatar": {},
"type": "User",
"work_days": "MON,TUE,WED,THU,FRI",
"weekdays": "MO,TU,WE,TH,FR",
"weekly_capacity": 40.0,
"user_level": "employee",
"admin": false,
"hide_hourly_rate": false,
"hide_internal_hourly_rate": true,
"deleted": false,
"default_hour_rate": 15.0,
"internal_hour_rate": 0.0,
"role_id": 1135466,
"role": {
"id": 1135466,
"name": "employee"
}
},

I dont know if I provided enough screenshots or info. Just let me know. Since the point I'm at with the flow is working I didn't show much of that. I don't know where to start for this next step.

Thank you!

[Expiscornovus]

Hi @ImprintGroup,

Thanks for sharing all that information. That is very useful.

You can create that array for your PUT request by using a Select action and using the response of the list all users.

Obviously, I don't have access to your API. So, for demo purposes I stored your demo response in an array variable.

In the select you can use a key value mapping to turn it into the array you want.

As you can see I have used the new key names user_id and hour_rate.

In the value columns I used expression to point to the right properties:

item()?['id']

item()?['default_hour_rate']

[ImprintGroup]

This is really helpful and I think I'm following. I've added your suggestion in line with the rest of my flow.

My assumption was that I would then be able to call the user_id and hour_rate as dynamic content when I'm forming the body of the PUT request. But I don't see how I would do that as I can't find them in the dynamic content list.

I don't yet understand how I'll take those select items and format them into the PUT Body like the example:  [{ "user_id": 175551, "hour_rate": 25.0 },{ "user_id": 117861, "hour_rate": 27.0 }]

And I have other pieces of required info I have to place in front of those like the name, client id, color (for color coding)

Your help and patience mean a lot!

[ImprintGroup]

I've had a chance to see some results after adding your suggestion and it is working to create an array of the user_id and the hourly rate.

I'm guessing that when building my PUT request I just use the dynamic content of the "body" from that step in the spot where I need that employee info to be.

I'm going to work on getting the other required pieces I need and then will try building the PUT request and see what happens.