API on a List + Parsing Through YouTube Analytics API

[steven.h.liu.1]

Hi- I’m trying to Schedule an API on the List and the list being a YouTube Analytics API output (see below for the raw output). What I’m making it do is to parse through each row, separate the row into three different data fields, and record them into a designated dataType.

However, I encounter two issues:
1/ There are 10 rows with 3 data fields each, instead of recognizing the list as 10 items, it is recognizing the list for 30 (10*3)
2/ The recording to the dataType only stays on the first row, so it would just record “age13-17”, “male”,0.3 30 times

Below are the raw output and my setup details:

{
“kind”: “youtubeAnalytics#resultTable”,
“columnHeaders”: [
{
“name”: “ageGroup”,
“columnType”: “DIMENSION”,
“dataType”: “STRING”
},
{
“name”: “gender”,
“columnType”: “DIMENSION”,
“dataType”: “STRING”
},
{
“name”: “viewerPercentage”,
“columnType”: “METRIC”,
“dataType”: “FLOAT”
}
],
“rows”: [
[
“age13-17”,
“male”,
0.3
],
[
“age18-24”,
“female”,
0.1
],
[
“age18-24”,
“male”,
42
],
[
“age25-34”,
“female”,
0.2
],
[
“age25-34”,
“male”,
45.9
],
[
“age35-44”,
“female”,
0.1
],
[
“age35-44”,
“male”,
9.9
],
[
“age45-54”,
“female”,
0
],
[
“age45-54”,
“male”,
1.4
]
]
}

Backend
image 2725×1840 289 KB
image 2760×1455 242 KB

Frontend
750e00c24450fcb9c9de89cacdece174e09b51f8.png (2287×1675)

[Jici]

The main error is in your Schedule backend WF on a list that YT_age&gender should be set to This text. In backend WF, uncheck LIST for the key YT_age&gender
Hovewer, I believe you should do that:
The backend WF should be set of the type of the API list (Probably ending by "‘s’ rows as this is the list you have with the name of api before)
After, the backend WF should have 3 fields: age range (text), gender (text) and finally viewer percentage (number)
In the Schedule on a list, you will also set the data source to just result of step 1’s rows. Each field will be
This text:first item, This text: item #2 and this text item #3 (or last item). So you will have each data already split before sending it to backend WF. (I’ve included the viewerpercentage, but you can remove this if not needed.)

[steven.h.liu.1]

Thanks! I’m fairly new to the backend, could you guide me through this in more detail?

The main error is in your Schedule backend WF on a list that YT_age&gender should be set to This text.

Not sure what this means. I don’t have “This text” as an option to select.

In backend WF, uncheck LIST for the key YT_age&gender

Done

The backend WF should be set of the type of the API list (Probably ending by "‘s’ rows as this is the list you have with the name of api before)

You mean do a “schedule API on a list” on the backend? How would that work?

Also, when I get to only “rows” for the list, it returns the input as red

After, the backend WF should have 3 fields: age range (text), gender (text) and finally viewer percentage (number)

This would be the same I have currently, right?

In the Schedule on a list, you will also set the data source to just result of step 1’s rows. Each field will be This text:first item, This text: item #2 and this text item #3 (or last item). So you will have each data already split before sending it to backend WF. (I’ve included the viewerpercentage, but you can remove this if not needed.)

Not quite following

[Jici]

Be sure the type of things is … 's row. It’s hard to see because the dropdown is not large enough, but your issue actually is that you didn’t set both as the same type (but your list to run on is correct). So just change type of things.
Actually, you only have one fields in backend WF. You can keep it as a list in backend and set only the current parameters using This rows and do the :first item… in the action in backend wf.

[steven.h.liu.1]

Setting the field to …'s row worked! It reduced the entry from 30 to 10. Thank you!

However, the WF is still only grabbing the first row vs. all the sequential rows. Do you know how to solve this?

[Jici]

You probably didn’t set your parameter in schedule on a list using This row…

[steven.h.liu.1]

Thank you. You are right.