Hi we're sorry to hear you are having issues. Canvas has different versions and we'd need a bit more information to help. Please email us at [email protected] and someone from our team will assist.

Yes, in the prompt just specify the list of text options it should use, then when you receive the response, just filter your option set to find the option that matches the returned value

Hi, you can go to your app's editor > database > app settings object > edit the first entry > under completed admin options field, add enable outgoing emails (this will mark it as completed in the setup checklist).

yes, it is in beta but you can still build on top of it using the API (not through ChatGPT)

We don't have a video like this yet but that's a great idea, we'll put it on the list!

Im also facing this too! Also afterpay/klarna not being available despite stripe saying it is active

@reaganpieter you can just create an API workflow that creates a single object and then schedule it on a the list of items returned from OpenAI

@@airdevco okay will try it out. Thanks!

That’s the type of thing I want to do, which is how I found myself here. I haven’t tested, but it seems this “recursive workflow” which acts as a loop, would allow for a nested recursive workflow (equivalent to a nested loop) - as you seem to understand by asking the question! There is another option “Schedule an API workflow on a list” to look into, but that might be a rabbit hole in the wrong direction. I think that might just be a shortcut to avoid having to set an exit condition - it would just run until the end of the list. I’d imagine your actual solution will use this single “API workflow” (But call it update-tags, because that’s what you’re trying to do) and the events will also use the normal “schedule API Workflow” - there will just be TWO of these events (after the first step, “make changes to a thing.. which I’ll get to) For this single workflow, do the same setup (2:05) but also include a parameter for Tag (also mark it as a list). ALSO add 2 more parameters: tag-index and tag-count. First step (event) would be to “make changes to a thing” and that thing would be a tag (more on that later) The THIRD step one would look almost exactly like the “schedule API workflow”, like shown at 5:50. But on this event, you’ll likely have to set the tag-index to 1. This represents getting through your tags on the single product, and calling the function again on the next product, starting with the first tag. Now going to the SECOND event, you’ll have to make ANOTHER “schedule API workflow” event, placed right before the THIRD event outlined above. In this one, you’ll instead be setting your tag-index to tag-index + 1, and condition is tag-index <= tag-count. This way, the second step will call itself for each tag on the item, until there are no more. Then it moves into the next step, triggering the workflow again, but for product#index+1. Now hopefully the THIRD event makes sense. It starts the whole process again on the next product, sets the tag-index to 1 to get the first tag, and runs the second step over and over until there are no more tags on that product. Move to step 3, rinse, and repeat. Remaining things to figure out: The first step, “make changes to a tag” seems straightforward, you’ll just set logic to add +1 to the field you’re using. The only issue is getting the “thing to change” expression correct. Based on what I outlined, I am pretty sure it will be “Tag item#tag-index”. That logic should be correct. FINALLY, and critically, you need to set up the front end workflow (as shown around 8:30). Similar to there, you’ll have to set both indexes to 1, and the product count as “search for.. (your products): count)” The remaining issue is setting the tag-count. It should be “product’s Tags: count” but this would only be correct for the first run through one product with tags. So a last adjustment - in step THREE above, where you reset tag-index to 1, the product-index to product-index *+1* you’ll also have to fetch the count for the number of tags on that next product. You can try “tag-count = product’s tags:count” but I worry this will be looking at the current product, not the NEXT one. So instead, you probably have to set “tag-count” on STEP TWO. I.e. “tag-count = product’s tags:count” This field will be rewritten for every iteration on the inner loop (step TWO, iterating through your tags), but it should be writing the same correct value every time: the current products total number of tags, which is the correct value you need. I am sort of hesitant that there might be another way to do this… Completely without a workflow. If you want to know how many times a tag appears in a list of tags on a product, you might be able to create a text elements on the repeating group of products where you use the dynamic data: search for tags.. with constraint “tag-name = current cell’s product’s list of tags:each tag’s tag-name: count” .. but maybe that doesn’t work Hope that helps - good luck!