I’m trying to pass the data from Step 1 into Step 2 as a variable,
and then use the output from Step 2 in Step 3.
Passing from Step 1 to Step 2 works fine,
but I can’t seem to pass the result of Step 2 into Step 3.
When I try to select the variable from Step 2 in Step 3, the variable I want doesn’t appear as an option.
How can I fix this?
Additional information
There are 10 records in Step 1, and each of them triggers 10 results in Step 2.
As a result, a total of 100 data combinations are generated.
What I want to do is extract only the necessary field values from each of those 100 records,
apply them as variables in Step 3, and create individual records in the database using the “Create Record” module.
Over the weekend, I figured out how to access Step 2’s result using EJS syntax.
However, I was only able to retrieve a single data item from the list.
I believe this would require using a loop inside another loop,
but it seems Bika does not support nested loops.
I’d like to know how to handle this situation or what workaround is recommended in this case.
When using the “Scheduler” trigger in Automation, the trigger does not run according to my local time, even if I input the time based on my time zone.
If there is a way to set the scheduler to operate in my local time zone, please let me know.
Hi @Headchef.Yang , thanks for sharing the details. For the scheduler, we’ve tested and it’s running as expected when the correct time zone is set here:
The issue related to date and time still isn’t working properly.
Please refer to the following link to check what might be causing the issue.
If I’ve made a mistake, I would really appreciate it if you could point it out.
As for the nested loop issue, I was able to resolve it within 30 minutes on Make.com without any difficulties.
I’m not sure if this reflects a strength of Make.com, but I do wish Bika could offer similar functionality.
I understand that Bika is still being actively upgraded.
What’s often unclear to me is whether something isn’t working because I’m doing it wrong—or because the feature simply isn’t supported yet.
If I could just know that clearly, I’d be able to decide whether to keep trying or move on.
Unfortunately, there aren’t many places or resources to ask, so I constantly find myself wondering and struggling on my own.
Still, I truly appreciate your thoughtful and detailed responses every time. Thank you.
I noticed that the schedule trigger runs about 2 to 3 minutes late.
It would be nice if it could be more precise, but for now, it seems acceptable at this stage.
If I may be a bit hopeful, I would love to see this improved so that it can run exactly on time in the future.
The issue is related to the default timezone — automation runs on UTC (zero timezone) by default. You’ll need to set it explicitly to your local timezone (for example, UTC+9 if you’re in Korea). Sorry for the confusion; I’ve also submitted this as feedback to the team.
Regarding the 2–3 minute delay, this is likely due to network fluctuations. I’ve noted this as well for further review and possible optimization.
We understand that Bika.ai works differently from tools like Make.com, and our documentation still has room for improvement. We’re continuing to make it clearer and more helpful. In the meantime, feel free to keep sharing your questions here, we’re always happy to assist as much as we can.
Our team tested this workflow, and you can see from the screenshot:
• data […] is an array of results.
• paging {…} is a pagination object with structured fields you can drill into.
If you want to select a specific element from an array to insert as a variable, the variable selector does not support this—it can only use the entire array as a variable. The correct approach is to use a loop action, and then process the elements within the loop action.
As for the nested loops you mentioned, Bika.ai does not currently support multi-level loops. However, we’d be happy to explore alternative approaches with you. Could you share more about your specific business scenario or use case? That will help us recommend a suitable solution.
