TexAu includes 14 built-in processing actions that automatically clean, normalize, and transform your data. Unlike formulas, which you write from scratch, processing actions are pre-built tools ready to use with a single click. They handle the tedious cleanup work so you can focus on outreach and analysis.
This guide covers every available action with real examples you can apply to your own data.
CleanDomain —extract and normalize domain names
What it does: Extracts the domain from any URL or email address and normalizes it by removing prefixes like "www." and converting to lowercase.
When to use it:
- You have a mix of email addresses and website URLs and need just the domain for matching.
- URLs are in inconsistent formats (some with "www.", some without, some with "https://").
- You want to group contacts by company domain for account-based analysis.
Examples:
This table scrolls sideways on small screens.
| Input | Output |
|---|---|
| john@acme.com | acme.com |
https://www.acme.com/about | acme.com |
| www.acme.com | acme.com |
| sarah@techstartup.io | techstartup.io |
https://enterprise-solutions.org | enterprise-solutions.org |
Tips:
- Removes the "www." prefix automatically for cleaner results.
- Handles both full URLs (with https://) and plain email addresses.
- Normalizes everything to lowercase for consistent matching across datasets.
- A good first step before deduplicating contacts by company.
PredictGender —predict gender from first name
What it does: Analyzes a first name and predicts the most likely gender, returning Male, Female, or Neutral.
When to use it:
- You want to personalize outreach email greetings (e.g., "Dear Mr." vs. "Dear Ms.").
- You are segmenting contacts for targeted messaging campaigns.
- You need to fill in missing demographic data for reporting.
Examples:
This table scrolls sideways on small screens.
| Input | Output |
|---|---|
| John | Male |
| Sarah | Female |
| Alex | Neutral |
| Michael | Male |
| Jennifer | Female |
| Casey | Neutral |
Tips:
- Predictions are based on statistical analysis of large name databases.
- The "Neutral" category includes names that are commonly used across genders (Alex, Casey, Morgan, Jordan).
- Always review results for uncommon or international names where predictions may be less accurate.
- Use for personalization purposes only —this is a statistical prediction, not a definitive classification.
EncodeURIComponents —URL-encode text
What it does: Converts special characters in text to URL-safe format so you can safely include dynamic data in links and URLs.
When to use it:
- You are building personalized tracking URLs that include contact names or company names.
- You need to include search terms or query parameters in URLs.
- Text values contain special characters (spaces, ampersands, slashes) that would break a URL.
Examples:
This table scrolls sideways on small screens.
| Input | Output |
|---|---|
| John Smith | John%20Smith |
| acme & co | acme%20%26%20co |
| $100/month | %24100%2Fmonth |
| hello@acme.com | hello%40acme.com |
| New York, NY | New%20York%2C%20NY |
Tips:
- Always use this action before inserting dynamic data into URLs to prevent broken links.
- Commonly used when building personalized tracking URLs for email campaigns.
- Spaces become
%20, ampersands become%26, and other special characters are similarly encoded.
CountOccurrences —count pattern appearances in text
What it does: Counts how many times a specific word, phrase, or character appears in a text field.
When to use it:
- You want to measure keyword density in company descriptions or bios.
- You are counting mentions of a product, competitor, or technology in scraped text.
- You need a simple way to score or rank text fields by relevance.
Examples:
This table scrolls sideways on small screens.
| Text | Search pattern | Output |
|---|---|---|
| "We use it daily, daily!" | daily | 2 |
| "Big company, enterprise scale" | enterprise | 1 |
| "URGENT! URGENT! Act now!!!" | ! | 5 |
| "AI-powered AI tools for AI teams" | AI | 3 |
| "No matches here" | cloud | 0 |
Tips:
- Searches are case-sensitive ("Daily" and "daily" are counted separately).
- Works with single characters as well as full words and phrases.
- Useful for data quality checks —count occurrences of "null", "N/A", or empty markers to find incomplete records.
- Combine with an IF formula afterward to categorize rows based on count thresholds.
FindSitemapURLs —discover sitemap URLs for a domain
What it does: Checks a domain for publicly available XML sitemaps, which show the pages a company considers most important on their website.
When to use it:
- You want to understand a company's web presence and content strategy.
- You are building a research file of key pages for target accounts.
- You need to discover blog, product, or resource pages for competitive analysis.
Examples:
This table scrolls sideways on small screens.
| Input domain | Output |
|---|---|
| acme.com | https://acme.com/sitemap.xml |
| enterprise.com | https://enterprise.com/sitemap.xml, https://blog.enterprise.com/sitemap.xml |
| startup.io | No sitemap found |
Tips:
- Not all websites have public sitemaps, so expect some empty results.
- Sitemaps indicate which pages the company wants search engines to index.
- Can reveal subdomains, blog structures, and product pages that are not immediately obvious from the homepage.
- Combine with other enrichment data for a fuller picture of each target account.
NormalizeDeduplicateList —clean and deduplicate lists
What it does: Takes a field containing a list of items (typically separated by commas or semicolons), removes duplicate entries, cleans up extra spaces, and returns a tidy unique list.
When to use it:
- A contact's skills, tags, or technologies field contains repeated entries.
- You merged data from multiple sources and ended up with duplicate values in list fields.
- You want a clean, unique list of items for display or analysis.
Examples:
This table scrolls sideways on small screens.
| Input | Output |
|---|---|
| python, javascript, python | python, javascript |
| Docker; kubernetes; Docker | Docker, kubernetes |
| Java , Java, Python | Java, Python |
| React, Vue, React, Angular, Vue | React, Vue, Angular |
Tips:
- Automatically detects common list separators (commas, semicolons).
- Removes extra whitespace around each item.
- Comparisons are case-sensitive, so "AWS" and "aws" are treated as different items. Standardize casing first if needed.
- Good for cleaning up technology stacks, skill lists, and tag fields after data imports.
IdentifyEmailType —classify as personal, work, or generic
What it does: Analyzes an email address and classifies it into one of three categories: Personal (Gmail, Yahoo, Outlook), Work (company domain), or Generic (info@, support@, noreply@).
When to use it:
- You want to prioritize work emails for B2B outreach (they are more likely to reach the right person).
- You need to filter out generic mailbox addresses that rarely convert.
- You are auditing the quality of your contact database.
Examples:
This table scrolls sideways on small screens.
| Type | |
|---|---|
| john@gmail.com | Personal |
| sarah@acme.com | Work |
| support@acme.com | Generic |
| info@company.org | Generic |
| michael@company.com | Work |
| david@yahoo.com | Personal |
Tips:
- Work emails show clear company affiliation and are typically the best for B2B outreach.
- Generic addresses (info@, support@, sales@, noreply@) go to shared inboxes and have lower response rates.
- Personal emails (Gmail, Yahoo, Outlook) may be useful for certain campaigns but indicate the contact did not provide a work address.
- A common workflow: run IdentifyEmailType, then use an IF formula to prioritize "Work" emails and deprioritize "Generic" ones.
ExtractURLsEmails —extract URLs and email addresses from text
What it does: Scans a block of text and pulls out every URL and email address it finds, returning them as a list.
When to use it:
- You have company descriptions, about pages, or bios with embedded contact information.
- You scraped website content and need to extract all links and email addresses.
- You want to find social media profiles or resource links mentioned in free-text fields.
Examples:
This table scrolls sideways on small screens.
| Input text | Output |
|---|---|
"Visit us at https://acme.com or email sales@acme.com" | https://acme.com, sales@acme.com |
"Contact: john@example.com or visit https://linkedin.com/company/acme" | john@example.com, https://linkedin.com/company/acme |
| "No links or emails here" | (empty) |
Tips:
- Recognizes standard URL formats (http://, https://, www.) and email address patterns.
- Returns an empty result if no URLs or emails are found in the text.
- Useful for mining contact information from unstructured data like company descriptions or scraped web pages.
- Combine with CleanDomain afterward to normalize any extracted URLs to their root domain.
NormalizePhoneNumber —standardize phone number format
What it does: Takes phone numbers in any format and strips them down to a clean, consistent digit-only format for storage and matching.
When to use it:
- Phone data comes from multiple sources with different formatting conventions.
- You need consistent formatting before deduplication or matching.
- You are preparing data for SMS campaigns or CRM imports that require a specific format.
Examples:
This table scrolls sideways on small screens.
| Input | Output |
|---|---|
| (555) 123-4567 | 5551234567 |
| 555.123.4567 | 5551234567 |
| +1 555 123 4567 | 5551234567 |
| 555-123-4567 | 5551234567 |
| 5551234567 | 5551234567 |
Tips:
- Removes all formatting characters: parentheses, dashes, dots, spaces, and country code prefixes.
- Works best with US and North American phone numbers.
- International numbers will be simplified to their core digit sequence.
- Run this action before deduplicating contacts to catch phone numbers that are the same but formatted differently.
NormalizeCompanyName —remove legal suffixes
What it does: Cleans up company names by removing common legal suffixes (Inc., LLC, Corp., Ltd., Co., etc.) and extra whitespace, leaving just the recognizable company name.
When to use it:
- You are matching companies across different datasets where naming conventions vary.
- Company names include inconsistent legal suffixes that make matching difficult.
- You want cleaner names for display in reports, exports, or outreach templates.
Examples:
This table scrolls sideways on small screens.
| Input | Output |
|---|---|
| Acme Inc. | Acme |
| Tech Solutions LLC | Tech Solutions |
| Enterprise Corp | Enterprise |
| Global Enterprises, Inc. | Global Enterprises |
| Digital Innovations Ltd. | Digital Innovations |
Tips:
- Handles the most common legal suffixes automatically (Inc., LLC, Corp., Ltd., Co., PLC, GmbH, and more).
- Also cleans up extra whitespace left behind after suffix removal.
- Improves company matching accuracy across datasets where one source uses "Acme Inc." and another uses "Acme Corporation".
- Use before company name comparisons or deduplication for best results.
RemoveExtraWhitespace —clean messy spacing
What it does: Removes leading spaces, trailing spaces, and reduces multiple consecutive spaces between words to a single space.
When to use it:
- Data from imports or exports has inconsistent spacing.
- You are cleaning up copy-pasted text before using it in outreach.
- You want consistent formatting across a column for quality checks or display.
Examples:
This table scrolls sideways on small screens.
| Input | Output |
|---|---|
| " Hello World " | "Hello World" |
| "John Smith" | "John Smith" |
| " Software Engineer " | "Software Engineer" |
| " Multiple Spaces " | "Multiple Spaces" |
Tips:
- Removes leading and trailing spaces completely.
- Collapses multiple consecutive spaces in the middle of text to a single space.
- Simple but effective —messy spacing causes silent failures in matching and comparisons.
- Often a good first step before running other text-based actions or formulas.
FormatDateTime —convert date formats
What it does: Takes a date value in one format and converts it to a different, standardized format of your choosing.
When to use it:
- Dates across your data are in different formats (US vs. international, short vs. long).
- You need consistent date formatting for reports, exports, or integrations.
- You want human-readable dates for display in outreach materials.
Examples:
This table scrolls sideways on small screens.
| Input | Target format | Result |
|---|---|---|
| 2024-01-15 | MM/DD/YYYY | 01/15/2024 |
| 1/15/2024 | YYYY-MM-DD | 2024-01-15 |
| 01/15/2024 14:30 | MMMM DD, YYYY | January 15, 2024 |
| 2024-01-15 | DD/MM/YYYY | 15/01/2024 |
Tips:
- Supports common date formats including ISO (YYYY-MM-DD), US (MM/DD/YYYY), European (DD/MM/YYYY), and long-form (MMMM DD, YYYY).
- Handles both date-only and date-with-time inputs.
- Match the output format to your audience —US teams typically expect MM/DD/YYYY, while European teams expect DD/MM/YYYY.
- Important when preparing data for CRM imports that require a specific date format.
FindRedirectPage —follow URL redirects
What it does: Takes a URL and follows any redirect chain (301, 302, etc.) to find the final destination page.
When to use it:
- You have shortened URLs (bit.ly, t.co) and need the actual destination.
- A company's website redirects to a new domain and you want the current URL.
- You are validating URLs to check if they still lead somewhere active.
Examples:
This table scrolls sideways on small screens.
| Input URL | Final destination |
|---|---|
| bit.ly/acme123 | https://acme-solutions.com/special-offer |
| company.com | https://company.io/home |
| old-site.com | https://new-site.com |
Tips:
- Follows the full redirect chain, not just the first hop.
- Useful for discovering a company's current primary domain when the URL you have is outdated.
- If a URL is broken or unreachable, no destination is returned.
- Some URLs do not redirect at all —the input URL is the final destination.
DistributeLeadsRoundRobin —distribute leads evenly
What it does: Takes a set of leads and assigns them to team members in round-robin order, cycling through your team list so that each person gets an approximately equal share.
When to use it:
- You want fair, automatic lead distribution across your sales team.
- You are assigning new prospects to account managers without manual intervention.
- You need to balance workload evenly as new leads come into your pipeline.
Examples:
This table scrolls sideways on small screens.
| Lead | Team members | Assignment |
|---|---|---|
| Lead 1 - Acme Corp | John, Sarah, Michael | John |
| Lead 2 - Tech Inc | John, Sarah, Michael | Sarah |
| Lead 3 - Enterprise LLC | John, Sarah, Michael | Michael |
| Lead 4 - Startup.io | John, Sarah, Michael | John (cycles back) |
| Lead 5 - DataCo | John, Sarah, Michael | Sarah |
| Lead 6 - CloudFirst | John, Sarah, Michael | Michael |
Tips:
- Assignment rotates through team members in the order you define them.
- Each person gets a roughly equal number of leads over time.
- If your team size changes, the distribution adjusts automatically from that point forward.
- Works well when combined with scheduled jobs —new leads that arrive on a schedule are automatically distributed without manual effort.
- Prevents any single team member from being overloaded while others have capacity.
Quick action finder
Use this table to quickly identify the right action for your task.
This table scrolls sideways on small screens.
| I need to... | Use this action |
|---|---|
| Extract a clean domain from URLs or emails | CleanDomain |
| Predict gender from a first name | PredictGender |
| Make text safe for use in URLs | EncodeURIComponents |
| Count how many times a word appears in text | CountOccurrences |
| Find a website's sitemap | FindSitemapURLs |
| Remove duplicates from a list field | NormalizeDeduplicateList |
| Classify an email as personal, work, or generic | IdentifyEmailType |
| Pull out all URLs and emails from a text block | ExtractURLsEmails |
| Standardize phone number formatting | NormalizePhoneNumber |
| Remove Inc., LLC, Corp. from company names | NormalizeCompanyName |
| Fix messy spacing in text | RemoveExtraWhitespace |
| Convert dates to a consistent format | FormatDateTime |
| Find where a URL actually leads after redirects | FindRedirectPage |
| Distribute leads fairly across a team | DistributeLeadsRoundRobin |
Combining processing actions with formulas
Processing actions and formulas work best together. Actions handle the cleanup; formulas handle the logic and analysis. Here are common combination patterns.
Clean, then validate: Run NormalizePhoneNumber to standardize phone digits, then use a LEN formula to check that the result has the expected number of digits.
IF(LEN(normalized_phone) >= 10, "Valid", "Too Short")
Classify, then prioritize: Run IdentifyEmailType to categorize emails, then use an IF formula to assign a priority score.
IF(email_type == "Work", "High Priority", IF(email_type == "Personal", "Medium Priority", "Low Priority"))
Extract, then combine: Run CleanDomain to extract domains from emails, then use CONCAT to build a company profile URL.
CONCAT("https://www.linkedin.com/company/", clean_domain)
Normalize, then deduplicate: Run NormalizeCompanyName to strip legal suffixes, then compare the cleaned names across rows to find duplicate accounts.
Format, then display: Run FormatDateTime to standardize dates, then use CONCAT to build a human-readable summary.
CONCAT("Last contacted on ", formatted_date)
The general pattern is: use processing actions first to prepare your data, then use formulas to analyze, categorize, and enrich it further.
Next steps
- Formula Basics —Learn how to write calculated columns that work alongside processing actions.
- Formula Functions Reference —A complete guide to every formula function available for analysis and transformation.
- Setting Up Scheduled Jobs —Automate your workflows so processing actions and formulas run on a schedule.
- Running Enrichments —Learn how to run enrichments on your table data to fill in missing information.