TexAu Input Types
Like in many data extraction tools, there are five input data types you can use depending on your needs and use cases in TexAu.
TexAu needs proper input variables to generate the expected output variables after the data extraction process.
Ex: you need a LinkedIn People Search Url (input variable) to collect profile Urls (output variable).
Sometimes we want quick data extraction for a short period of time. Sometimes, we want to process a long list of URLs for weeks.
Let's see how you can leverage that.
Each module will give you an indication of the expected input values. It is necessary to input the correct extraction query for optimal results.
The variable input can be:
- A single URL: a search, profile, or post URL.
- A text query: a search query, keywords.
- Your cookies.
Useful when you have a list of URLs as the input dataset. This could be data from your CRM, the results of a form registration with contact details, a survey, a webinar attendees list.
It requires uploading a list of URLs in CSV file format in TexAu and mapping its columns as input variables.
Be sure to map the correct column on your CSV file to match the expected field validation input in TexAu.
Same as CSV but accessible from a shareable URL. You can also enrich the original data from your existing Sheet, which is impossible with a CSV file. That means you can write and enrich data on the same Google Sheet you used as input.
This is particularly helpful for incremental extraction, when you want to extract data every day from the same data source.
Same as CSV files, be sure to map the correct column on your Google Sheet to match the expected field validation input in TexAu.
This input serves the purpose of storing your cookies or API Keys when using integrations.
You can use the variable output from a previous automatoon execution as an input in the next module to chain multiple automation and create a workflow.
In workflows, this is similar but looks different.
In workflows, direct input is done in each automation module of a workflow from the right panel when you click on a module.
Each automation module will give you an indication of the expected input. The input can be:
- A single URL: a search, profile, or post URL.
- A text query: a search query, keywords.
- Your cookies.
Helpful when used from a list of URL inputs. Google Sheet inputs in workflows are the columns you map from the Sheet as a data source at the start of your workflow.
You can also enrich the original data from your existing Sheet, which is not possible with CSV.
But it can also be a Google Sheet variable that you can reuse as input in other modules of the workflow:
Helpful when used from a list of URL inputs. Requires to upload CSV file in TexAu and map its columns as input variables.
In workflows, local and global variables can serve the following purpose:
- Local variables: act as containers to store and link the data on a Sheet or CSV column
- Global variable: store your cookies and integration API keys to use them in all workflows.
Local and Global variables can process dynamic values stored in a CSV or Google Sheet column, for instance.
Module variables are the outputs generated from previous modules of your workflow and used as input in the next one.
In the example below, the automation called "Find an Email Address" uses the firstName, lastName, and domain output variables from the first two automation:
- The first name and last name from the automation called "Scrape a LinkedIn Sales Navigator Profile".
- The domain from the automation called "Company Name To Domain".
Each user input must match the expected input data type and validation rules in TexAu. This is essential to add the proper variable input to ensure a smooth data extraction process.
It's also important to check the additional options provided in the various dialog boxes of each automation.
Always pay attention to the data field property description to pass TexAu's data validity check before launching your automation. To prevent manual errors, we will later add a field validation feature to live check user input.
