Results 84 comments of Ahmad Kholid

The `Update previously opened tab` only works when the `new tab` block has the same workflow execution session. For example, when you have a workflow with two `new tab` blocks...

> In New tab block , User-Agent do not support mustache tag. hope can fix it. I'll fix it > by the way, i don't think use chrome.debugger.sendCommand to add...

The workflow stops executing because the element you try to check using the "Element exist" block doesn't exist and it also doesn't have a fallback. To fix this, try to...

> @Kholid060 What am I doing wrong? > > **Flow** HTTP request -> Loop data -> Condition (check link is exist) -> New tab -> Loop breakpoint > > **Loop...

You can use the 'Code' option in the condition block to check if the value is `null` ![image](https://github.com/AutomaApp/automa/assets/22908993/53907b4b-dc06-4163-a161-51a3a1f9aaf2)

If you do not intend to take a value from the user when running a workflow, use the [global data](https://docs.automa.site/workflow/global-data.html#global-data) to define your config instead.

If you want to use a variable as the value on an input of a block. You need to wrap it inside a mustache, so, in this case, it would...

Automa actually already supported Manifest V3. All you have to do is change the `chrome.manifest.json` into this chrome.manifest.json ```json { "manifest_version": 3, "name": "Automa", "action": { "default_popup": "popup.html", "default_icon": "icon-128.png"...

> > Automa actually already supported Manifest V3. All you have to do is change the `chrome.manifest.json` into this > > chrome.manifest.json > > However, the downside of using manifest...

Can you explain more about this issue like what browser you use, what version of Automa, and step by step to reproduce this issue?