I have the following issue:
Initial export gets an array of 3 element. I want each element to save/post in the destination one by one. Before posting each element, I do query to find out, how many elements are already posted. So I added lookup field before post.
The issue is that, it seems, Celigo executes 3 lookup query first and then makes 3 post, which causes problem, because for all 3 lookup query, I am receiving 0 count.
Is it possible, to finish one item fully and then continue to next item in the array?
Only way would be to make the export treat the elements as individual records, set your page size to one, then on your import use the composite api to do the lookup and post call in one.
I try to treat them as individual records.
My data from API looks like this :
{
"data": [
{
"id": 1,
"createdAt": "2026-04-17T00:00:00",
"type": null,
"projectId": 31
},
{
"id": 2,
"createdAt": "2026-04-18T00:00:00",
"type": null,
"projectId": 34
}
],
"pagination": {
"page": 1,
"pageSize": 2,
"totalPages": 3,
"total": 3
}
}
and I set "data" in the "Non-standard API response pattern"
so, I assume Celigo will treat records with Id:1 and Id:2 as individual items. But after doing this, pagination is not working, because in "Path to total number of pages field in HTTP response body" I have "pagination.totalPages", which is not evaluated when the node goes inside "data" array.
The "Path to total number of pages field in HTTP response body" field works from the raw response, not after evaluating the path to records. So pagination should still work. Are you expecting 6 total records (2 pageSize * 3 totalPages)?
I also expected this behavior. But when I set Path to records in HTTP response body to "data" and try to test, I see this:
"message": "Identical response received from next page request. No more page requests will be made.",
It looks like it paged, but then ended up getting the same response. Can you enable debug logs on the export step in the top right, then preview, then check the logs? You cans see each request. Also, can you share the rest of your export setup?
When I run it as a flow, it runs without above error. So, l assume putting as individual items is working.
Now I want each item to run sequentially, meaning finish first item and only after finishing first item, go to the next item.
You said, this should be done via composite api?
Yeah you could set your page size to 1 on your export, then use the composite option on http import. You could also build an API via API Builder and call that on import, still with page size 1.
Can't see composite option here, is there other way to set composite option?
That's an export, composite api is only on imports.
It is a lookup actually:
It seems lookup does not support composite, only export supports?
Only imports support composite. The idea of composite is it's a lookup and import in one. So it first does the lookup, then does the import. For example, lookup to see if a customer exists, if not, create them, etc.
