In my case, I need to scrape 2 things. One is the sku number, which is often not displayed on the ui, but if you look into the source code of the webpage, you can usually find it.

I also need to scrape all product variants, such as all colors and product sizes, all finishes, etc.

If I do this via UI, I need to click each product option, and wait for the ui change and then scrape the content. My work becomes easier if I can capture a json data exchange or a javascript object that contains this information. For most of the cases, I can find it. So I gave up on reading things directly from the UI.

I learned a new word, "ETL workflow". I have been doing this data scraping thing for a while, I didn't know there is a whole ecosystem existing. Scraping is such a pain, it's sad that there is a lack of common data exchange standards.

It sounds like this is a possible use-case, but it depends on the scale at which you want to scrape.

Axiom is good at pulling out data from complex workflows with forms.

It's not designed for doing large-scale scraping (...IP rotation etc.)

Do you have examples of the main uses cases we could try? Is this mainly made for engineers to automate prerecorded actions, or do you see another vertical apply?

Right now axiom isn't great for QA as we don't have conditional logic, but that inevitable feature will make QA pretty easy.

It's not good for scraping large-scale data-sets, but is good for data extraction from very complex forms.

The ideal use case is 'Extract, Transform, Load'. Most scrapers can only extract data, we can extract it, transform and input it into another system.

We've seen adoption for Sales and E-commerce admin in particular.

In your case, you could create a template for your emails and hangout invites, mail merge style. In addition to sending the hangout invite, you could trigger another action in your CRM.

I'm speculating as an example, it really depends on what particular processes you have that are repetitive.