Hello,
When building an automation on a Tulip table base, there is a need to bring a value that depends on any kind of query, like for example, return last sample number order by update date or return id number filtered by field #1, field #2 and ordered descending by create date, doing this use case is possible only with connector function, so you have to create the query → aggregation → new connector function → use in automation.
Why can’t I use aggregation value (mod) directly in automation as I’m using it in app builder?
I guess that is actually not possible.
You can use the connector function, but directly define your filters and aggregation inside this function.
Prebuilt queries and aggregations are not useable by connector function are they? (correct me if I’m wrong here…)
Hi,
The feature I suggested does not exists, because of that I suggested to add one.
In connector function you can use aggregation you’ve created by using [GET] /tables/{tableId}/runAggregation but for using the aggregation inside an automation you have to do complete process as I wrote.
Thats where I think you might got something wrong (or me…I might have misunderstood your workflow?).
This does not call an aggregation on a query you prebuilt on the tables page.
You define your filters and aggregation type directly in this connector function.
So it is not query & aggregation & connector function
It is only the connector function itself.
Hi,
Thank you for your answer, I don’t have so much experience with connector function, so, it’s good to know how to deal with aggregations in connector function and use them in automations, but build a connector function for each value you want to import from a Tulip table sounds unnecessary and frustrating, using aggregation directly from the Tulip table will be much easier.