that is absolutely possible. You will run into an issue when you have more than 99 groups as they can only be displayed through a "skiptoken" aka "odata.nextlink".
If you have more than 999 groups you need another connector and if you thank have more than the next 999 you also need another connector because you cant use the same "get api command " twice in1 connector.
//Page 1
ClearCollect(CorpGroups,APIGroups.GetGroups({'$top': 999 }).value);
Set(varSkiptoken,APIGroups.GetGroups({'$top': 999 }).'@odata.nextLink');
//Page 2 Right(varSkiptoken,Len(varSkiptoken) -60)
Collect(CorpGroups,APIGroupsPage2.GetPage2({'$skiptoken': Right(varSkiptoken,Len(varSkiptoken) -60) }).value);
Set(varSkiptoken2,APIGroupsPage2.GetPage2({'$top': 999,'$skiptoken': Right(varSkiptoken,Len(varSkiptoken) -60) }).'@odata.nextLink');
//Page 3 Right(varSkiptoken2,Len(varSkiptoken2) -60)
Collect(CorpGroups,APIGroupsPage3.GetGroupsPage3({'$skiptoken': Right(varSkiptoken2,Len(varSkiptoken2 ) -60) }).value);
//Set(varSkiptoken3,APIGroupsPage3.GetGroupsPage3({'$top': 999,'$skiptoken': Skiptoken_1.Text }).'@odata.nextLink');
you need to send the correct link to the API thats why i am getting rid of the https://.... with the length function.
i am useing this graph api command
https://graph.microsoft.com/v1.0/groups
with an extra query for $top and $Skiptoken