Home Integrations

Integrations

Vikesh Tiwari Asif Sultan
By Vikesh Tiwari and 1 other
• 29 articles

Apify Integration Guide

Apify Integration Guide This guide covers all Apify actions available in TexAu. Apify actions scrape data from LinkedIn, Google Maps, Google Search, and websites. Before you begin - An Apify account is required. Sign up at apify.com. - Your Apify API token is at Settings > Integrations > API & Integrations in Apify. - In TexAu, go to Settings > Integrations, find Apify, enter your API token, and click Save. - Apify charges per actor run. Costs vary per action. Check apify.com/pricing. LinkedIn actions Get LinkedIn Profile Detail (Apify) Scrapes a LinkedIn profile and returns structured data about the person. Input: - LinkedIn Profile URL (required) Output: - First Name, Last Name - Headline - Current Job Title, Company Name - Location - Experience history (array) - Education history (array) - Skills (array) - Connections count - Follower count - Profile summary Typical use case: Deep profile enrichment when you want more than just email or phone. Search LinkedIn Profiles (Apify) Searches LinkedIn for people matching a query and returns a list of profiles. Input: - Search query (required): e.g., "VP Sales fintech San Francisco" - Result limit: number of profiles to return Output per profile: - First Name, Last Name - Headline - LinkedIn Profile URL - City, Country - Current company - Follower count - Connections count Typical use case: Build a prospecting list directly from a LinkedIn search query. Scrape LinkedIn Company Employees (Apify) Returns a list of employees at a given company on LinkedIn. Input: - LinkedIn Company URL (required) - Result limit Output per employee: - First Name, Last Name - Job Title - LinkedIn Profile URL - Location Typical use case: Build a full employee list for targeted account-based outreach. Search LinkedIn Companies (Apify) Searches LinkedIn for companies matching a keyword or filter. Input: - Search query (required) - Result limit Output per company: - Company Name - LinkedIn Company URL - Industry - Employee count - Location - Tagline Get LinkedIn Job Postings (Apify) Finds current job postings at a specific company. Input: - LinkedIn Company URL (required) Output: - Job title - Job location - Date posted - Job URL Typical use case: Identify companies that are hiring to infer growth signals. Get LinkedIn Job Listings (Apify) Searches LinkedIn for job listings matching a query. Input: - Job title or keyword (required) - Location (optional) - Result limit Output: - Job title - Company name - Job URL - Posted date Get LinkedIn Posts from Profile (Apify) Retrieves recent posts from a LinkedIn profile. Input: - LinkedIn Profile URL (required) - Number of posts (optional) Output: - Post text - Post date - Like count - Comment count - Post URL Typical use case: Research what a prospect has written about recently before outreach. Get LinkedIn Post Data (Apify) Retrieves data for a specific LinkedIn post. Input: - LinkedIn Post URL (required) Output: - Post text - Author name and title - Reactions count - Comments count - Published date Search LinkedIn Sales Navigator People (Apify) Searches Sales Navigator for people matching your filters. Requires a LinkedIn Sales Navigator subscription. Input: - Search URL from Sales Navigator (required) Output: - Full name - Job title - Company - LinkedIn profile URL - Location Search LinkedIn Sales Navigator Accounts (Apify) Searches Sales Navigator for companies matching your filters. Requires a LinkedIn Sales Navigator subscription. Input: - Search URL from Sales Navigator (required) Output: - Company name - LinkedIn company URL - Industry - Employee count - Location Google actions Get Google Maps Places (Apify) Finds businesses on Google Maps matching a search query in a specified location. Input: - Search query (required): e.g., "plumbers in Austin TX" - Location (optional) - Result limit Output per business: - Business name - Address - Phone number - Website URL - Rating and review count - Google Maps URL Typical use case: Build a local business prospect list from Google Maps. Get Google Maps Reviews (Apify) [see actions.json for display name] Retrieves reviews for a specific place on Google Maps. Input: - Google Maps Place URL (required) - Result limit Output: - Reviewer name - Rating - Review text - Date Get Google Search Results (Apify) Returns top search results from Google for a query. Input: - Search query (required) - Result count Output: - URL - Title - Snippet - Position Website actions Crawl Website Content (Apify) Crawls a website and returns the text content of pages. Input: - Starting URL (required) - Max pages to crawl Output: - Page URL - Page title - Page content (text) Typical use case: Pull website copy before passing to an AI Column for summarization. Scrape Website to Markdown (Apify) Fetches a URL and converts the content to Markdown. Input: - URL (required) Output: - Markdown content Take Webpage Screenshot (Apify) Loads a webpage and captures a screenshot. Input: - URL (required) Output: - Screenshot image URL Troubleshooting LinkedIn actions return empty or very few results. Apify's LinkedIn actors require a valid LinkedIn session. Some actors use Apify's proxy pool. If results are sparse, check the Apify dashboard to confirm your actor has sufficient resources and your account is in good standing. Google Maps actions return results from the wrong location. Be specific in the location field. Use city and state or city and country. Avoid country-only location inputs for large countries. Scraping actions time out on large pages. Reduce the result limit or the max pages setting. Very large pages or sites with anti-bot measures may slow down or block actor runs. I see charges on Apify but no data in TexAu. The actor ran but returned no results. Check the Apify dashboard for the specific actor run to see its output log.

Last updated on Apr 06, 2026

Apollo Integration Guide

Apollo Integration Guide This guide covers all Apollo actions available in TexAu, what each one needs as input, and what it returns. Before you begin - An Apollo account is required. Sign up at apollo.io. - Your Apollo API key is at Settings > Integrations > API Keys inside Apollo. - In TexAu, go to Settings > Integrations, find Apollo, enter your API key, and click Save. - Apollo API access is available on Apollo's paid plans. Check apollo.io/pricing for details. Find Email using Linkedin Url (Apollo) Finds a work email address using a LinkedIn profile URL. Credit cost: 2 credits per row Input: - LinkedIn Profile URL (required): full URL starting with https://linkedin.com/in/ Output: - Email Address - Email Verification Status - First Name - Last Name - Job Title - Company Name Typical use case: You have LinkedIn URLs and want to find verified work emails. Find Email using Name and Domain(Apollo) Finds a work email when you have a name and company domain, but no LinkedIn URL. Credit cost: 2 credits per row Input: - First Name (required) - Last Name (required) - Company Domain (required): e.g., acme.com Output: - Email Address - Verification Status Typical use case: You have a CRM list with names and company websites but no LinkedIn URLs and no emails. Find Mobile Number using Linkedin Url (Apollo) Finds a mobile or direct-dial phone number using a LinkedIn profile URL. Credit cost: 2 credits per row Input: - LinkedIn Profile URL (required) Output: - Phone Number - Phone Type (mobile, direct, headquarters) - Country Typical use case: Cold calling campaigns where you want to reach prospects on their personal device. Find Mobile Number using Name and Domain(Apollo) Finds a phone number using a person's name and company domain. Credit cost: 20 credits per row Input: - First Name (required) - Last Name (required) - Company Domain (required) Output: - Phone Number - Phone Type - Country Typical use case: Use this when LinkedIn URLs are not available and you need phone numbers from name + company data. Enrich Company (Apollo) Retrieves detailed company information for a given domain. Credit cost: 2 credits per row Input: - Company Domain (required): e.g., stripe.com Output: - Company Name - Industry - Employee Count - Annual Revenue (estimated) - Location (city, state, country) - LinkedIn Company URL - Technologies used - Funding information - Company description Typical use case: Enrich a list of company domains with firmographic data for segmentation and qualification. Building a waterfall with Apollo Apollo works well as a fallback provider in combination with other email or phone finders. Example sequence for email finding: 1. BetterEnrich: Find Work Email by LinkedIn URL (primary, highest accuracy) 2. Apollo: Find Email using Linkedin Url (fallback if BetterEnrich returns empty) 3. Findymail: Find Email Using LinkedIn URL (second fallback) Each column only runs when the previous one returned no result. Troubleshooting Actions return "person not found" for most rows. Apollo's database has strong coverage for North American and European companies. Coverage for other regions is lower. Verify your test data includes profiles that are likely in Apollo's database. Email results come back but the email is invalid. Apollo returns emails with a verification status. Filter your results to only use rows where the verification status is verified. Use a Formula Column with IF({{Verification Status}} == "verified", {{Email}}, "") to blank out unverified results. The API key saves correctly but requests return 401. Apollo API keys from free plans may not have programmatic access enabled. Check your Apollo plan or generate a new API key from your Apollo settings. Enrich Company returns empty for some domains. Apollo may not have data for small or very new companies. As a fallback, use Enrich Company (Hunter.io) or the Website Intelligence utility action.

Last updated on Apr 06, 2026

B2B Enrichment Integration Guide

B2B Enrichment Integration Guide This guide covers the B2B Enrichment integration available in TexAu. Use it to retrieve comprehensive LinkedIn profile data for a contact. Before you begin - The B2B Enrichment integration is built into TexAu. No external account is required. - No API key configuration is needed in Settings > Integrations for this integration. - Credit costs apply per row processed. Actions Enrich Contact (B2B Enrichment) Retrieves detailed profile information for a person based on their LinkedIn profile URL. Credit cost: 2 credits per row Input: - LinkedIn Profile URL (required): full URL starting with https://linkedin.com/in/ Output: - First Name - Last Name - Headline (LinkedIn headline) - Current Company Name - Current Company Domain - Current Job Title - Location Country - Location City - Open to Work: true/false - LinkedIn Premium: true/false - Profile Photo URL - Summary - Skills (array) - Experience (array: company, title, dates) - Education (array: school, degree, dates) Typical use case: Deep profile enrichment to populate a CRM or build context for personalized outreach. Why use Enrich Contact vs other enrichment actions Enrich Contact (B2B Enrichment) is best for getting complete profile data from a LinkedIn URL. It returns more fields than most email or phone finders. Use it when you need: - Job title and company information from a LinkedIn URL - LinkedIn headline for AI-generated personalization - Experience history for qualification or segmentation - Skills and education for recruiting or research For email finding only, use Find Work Email by LinkedIn URL (BetterEnrich). It is more targeted and may cost fewer credits. Common workflow pattern Build a prospect profile from a list of LinkedIn URLs 1. Start with a column of LinkedIn URLs. 2. Add an Action Column for Enrich Contact (B2B Enrichment). 3. Map the LinkedIn URL column as input. 4. Select the output fields you need (First Name, Last Name, Job Title, Company Name, Headline). 5. Add additional Action Columns for email and phone finding using the same LinkedIn URL input. 6. Run enrichment. You get a complete contact profile plus contact details in one run. Troubleshooting Output fields are empty even though LinkedIn URLs are valid. Check that the LinkedIn URLs in your table are current, public profile URLs. Private profiles or URLs with additional tracking parameters may not return full data. Strip any query string parameters from the URL before running. Enrich Contact returns data but the current job title is outdated. The enrichment reflects what is on the LinkedIn profile at the time of the run. If the person has not updated their profile recently, the data may be behind. This is a LinkedIn data limitation, not a bug. Partial output: some fields return data and others are blank. Not all fields are populated for every profile. Skills, summary, and education are optional on LinkedIn and may not be present for all contacts.

Last updated on Apr 06, 2026

BetterEnrich Integration Guide

BetterEnrich Integration Guide This guide covers all BetterEnrich actions available in TexAu, including what each action does, what inputs it requires, and what outputs it returns. Before you begin - A BetterEnrich account is required. Sign up at betterenrich.com. - Your BetterEnrich API key is on your BetterEnrich dashboard. - In TexAu, go to Settings > Integrations, find BetterEnrich, enter your API key, and click Save. Find Mobile Number by LinkedIn URL (BetterEnrich) Looks up a mobile phone number using a LinkedIn profile URL. Credit cost: 10 credits per row Input: - LinkedIn Profile URL -- the full URL of the person's LinkedIn profile (required) Output: - Mobile Number - Local Phone Format -- formatted for the person's country - Country -- detected country for the phone number - Timezone -- timezone based on phone number location - Status -- result status (found, not_found, pending) Notes: This action uses async processing. Results may take a few seconds per row. TexAu polls for completion automatically. Typical use case: You have a list of LinkedIn URLs and need mobile numbers for direct outreach. Find Work Email by LinkedIn URL (BetterEnrich) Finds a verified work email address using a LinkedIn profile URL. Credit cost: 2 credits per successful lookup Input: - LinkedIn Profile URL (required) Output: - Work Email - Email Verification Status - Domain Notes: Higher accuracy than name-based email lookups because the LinkedIn URL provides a strong identity signal. Find Email from LinkedIn (BetterEnrich) Alternative email lookup using LinkedIn URL. Use when Find Work Email by LinkedIn URL does not return a result. Credit cost: 2 credits per successful lookup Input: - LinkedIn Profile URL (required) Output: - Email address - Confidence score Find Work Email from Full Name and Company Domain (BetterEnrich) Finds a work email when you have a person's name and company domain but no LinkedIn URL. Credit cost: 8 credits per successful lookup Input: - First Name (required) - Last Name (required) - Company Domain (required) Output: - Work Email - Email type - Verification status Typical use case: Your data has names and company websites but no LinkedIn URLs. Find LinkedIn Profile URL by Name (BetterEnrich) Finds a LinkedIn profile URL for a person based on their name and optionally their company. Credit cost: 2 credits per successful lookup Input: - First Name (required) - Last Name (required) - Company Name (optional -- improves accuracy) Output: - LinkedIn Profile URL - Match confidence Typical use case: You have a CRM contact with no LinkedIn URL and want to enrich it. Find LinkedIn Profile URL by Email (BetterEnrich) Finds a LinkedIn profile URL when you have an email address. Credit cost: 4 credits per successful lookup Input: - Email Address (required) Output: - LinkedIn Profile URL - Match status Find Social Media URLs (BetterEnrich) Finds social media profiles across multiple platforms for a person. Credit cost: 2 credits per successful lookup Input: - LinkedIn Profile URL or Email (at least one required) Output: - Twitter URL - GitHub URL - Facebook URL - Instagram URL - Other detected social profiles Find Website from Company (BetterEnrich) Finds the website URL for a company based on its name. Credit cost: 1 credit per successful lookup Input: - Company Name (required) Output: - Company Website URL - Domain Typical use case: You have company names without domains and need domains for other enrichment actions. Verify Email (BetterEnrich) Validates whether an email address exists and can receive mail. Credit cost: 1 credit per row Input: - Email Address (required) Output: - Valid -- true/false - Deliverable -- true/false - Email type (work, personal, catch-all) - Reason -- explanation of verification result Verify Catch-All Email (BetterEnrich) Specifically checks whether an email address resolves to a catch-all domain. Catch-all domains accept mail addressed to any recipient, which means a standard verification passes even for invalid addresses. Credit cost: 1 credit per row Input: - Email Address (required) Output: - Is catch-all -- true/false - Confidence level Typical use case: Run this after standard email verification to flag catch-all addresses before sending campaigns. Check ESP (BetterEnrich) Identifies the email service provider (ESP) for an email address or domain. Credit cost: 2 credits per row Input: - Email Address or Domain (required) Output: - ESP name (e.g., Google Workspace, Microsoft 365, Zoho Mail) - MX records Typical use case: Segment your list by email provider to customize deliverability settings per campaign. Waterfall enrichment with BetterEnrich For maximum email coverage, combine BetterEnrich with other providers using waterfall enrichment: 1. Add an Action Column for email. 2. Set Find Work Email by LinkedIn URL (BetterEnrich) as the primary provider. 3. Add a second Action Column using Find Email Using LinkedIn URL (Apollo) or another provider. 4. Set the second column as a waterfall fallback. TexAu tries the primary provider first. If no result is returned, it tries the next provider automatically. Troubleshooting Find Mobile Number returns empty for most rows. Confirm that the LinkedIn URL column contains full URLs (starting with https://linkedin.com/in/), not short handles or names. BetterEnrich requires the full profile URL. Async results show "pending" after the run completes. TexAu polls for async results automatically, but very long queues at BetterEnrich can delay responses. Wait a few minutes and click Re-check results in the column settings. Email verification returns "unknown" for many addresses. Catch-all domains always return a status that is hard to classify. Run the Verify Catch-All Email action on those addresses separately. The integration saves but actions return authentication errors. Your BetterEnrich API key may have expired or been revoked. Go to the BetterEnrich dashboard, generate a new key, and update it under Settings > Integrations > BetterEnrich.

Last updated on Apr 06, 2026

Connect Integrations to TexAu

https://www.loom.com/share/2992ec79a78a40c592c0fff8f9042f2d Connect Integrations to TexAu Integrations connect TexAu to the tools and data sources you already use: your CRM, email platform, data providers, and more. They let you pull data from those tools into TexAu for enrichment, and push enriched data back out. Before You Begin Before connecting an integration, make sure you have: - A TexAu account with an active plan - An account on the external service you want to connect (Salesforce, HubSpot, a data provider, etc.) - Admin or API access on the external service (some integrations require admin-level permissions to authorize) - Your API key ready (if connecting via API key rather than OAuth) Why Connect Integrations? Pull Data In: Import leads and companies from Salesforce, HubSpot, LinkedIn, or custom databases directly into TexAu tables. Enrich with External Data: Use integrated data providers to automatically look up phone numbers, emails, company information, and more. Push Data Out: Send enriched data back to your CRM so your sales team always has the freshest information. Automate Workflows: Connect to Zapier or Make to trigger actions across your entire tool stack based on enrichment results. Sync in Real Time: Set up automatic syncing so new leads flow into TexAu, get enriched, and return to your systems without manual work. Two Ways to Connect: OAuth and API Keys TexAu supports two authentication methods. Understanding the difference helps you choose the right approach for each integration. OAuth 2.0: One-Click Connection OAuth is a secure, modern authentication standard. When you connect via OAuth: 1. You click Connect in TexAu 2. TexAu redirects you to the external service (for example, Salesforce or LinkedIn) 3. You see a permission screen asking what you want to allow TexAu to access 4. You click Allow or Authorize 5. You return to TexAu with an active connection You never share your password. TexAu never sees your login credentials. The external service grants TexAu permission to access only what you approve. Common services using OAuth: Salesforce, HubSpot, LinkedIn, Google, Microsoft (Office 365), GitHub, Slack, Zapier. Security note: OAuth is the most secure way to connect. Use OAuth whenever the integration offers it. API Key: Direct Authentication Some services do not support OAuth. Instead, they use API keys, which are unique tokens that act like passwords for applications. When you connect via API key: 1. You log into the external service and generate an API key 2. You copy that key and paste it into TexAu 3. TexAu stores it securely (encrypted) and uses it to access the service on your behalf Benefits of API keys: Direct access, full control, works with services that do not support OAuth. Trade-off: You are trusting TexAu with a credential. Your API keys are encrypted and never exposed. Common services using API keys: Custom APIs, some data providers, certain specialty tools. Connect an Integration via OAuth 1. Go to Settings, then Integrations From your TexAu dashboard, click Settings in the bottom left. Navigate to Integrations (or Connected Apps). 2. Find the integration you want Browse the list of available integrations. You see them grouped by category (CRM, Email, Data Providers, etc.). Find the one you want to connect. 3. Click Connect Click the Connect button next to the integration. 4. Authorize in the external service TexAu redirects you to the external service's login or permission screen. Log in if needed. You see a screen explaining what permissions TexAu is requesting (for example, "access to your leads," "ability to read and write contacts"). Review these permissions. 5. Click Allow or Authorize If you are comfortable with the permissions, click Allow, Authorize, or whatever the service calls it. 6. Verify the connection You return to TexAu with an active connection. You should see a green checkmark or "Connected" status next to the integration. Connect an Integration via API Key 1. Generate an API key in the external service Log into the external service (the data provider, custom tool, etc.). Navigate to API settings or developer settings. Look for a button like Generate API Key, Create Token, or New API Key. Click it. You get a unique string of characters. Copy it carefully (it usually displays only once). 2. Go to Settings, then Integrations in TexAu From your TexAu dashboard, click Settings. Navigate to Integrations. 3. Find the integration you want Find the integration in the list. 4. Click Connect Click the Connect button. 5. Paste your API key Instead of being redirected, you see a form asking for your API key. Paste the key you copied from the external service. Some integrations may also ask for a username, endpoint URL, or other credentials. Check the integration's documentation if you are unsure what to enter. 6. Click Connect or Authorize Click the button to establish the connection. 7. Verify the connection TexAu verifies the key and displays a success message. You should see "Connected" status next to the integration. Tip: Store your API keys securely. If you ever need to disconnect an integration, TexAu securely deletes the stored key. Manage Your Connected Integrations View All Connected Integrations Go to Settings, then Integrations. You see a list of all available integrations, and next to each one, you see the status: - Connected: This integration is active and ready to use. - Not Connected: You have not connected it yet. - Expired: The connection needs to be re-authenticated (usually for OAuth tokens that have timed out). Check Integration Status and Health Hover over or click a connected integration to see more details: - Connection date - Last activity - Any recent errors or issues - Permissions granted (for OAuth integrations) If an integration shows issues, check the Troubleshooting section below. Re-Authenticate an Expired Connection If an OAuth connection expires (this happens occasionally with some services), TexAu prompts you to re-authenticate. You see an "Expired" status next to the integration. Click Re-connect and follow the same OAuth flow as the initial connection. It is quick and usually takes just a few clicks. Understand Integration Permissions and Scopes For OAuth integrations, you see a list of permissions (called "scopes") that TexAu is requesting. Common ones include: - Read Contacts/Leads: TexAu can pull lead and contact data into your tables. - Write Contacts/Leads: TexAu can update contacts and leads in the external service. - Read Organizations: TexAu can pull company/account information. - Write Organizations: TexAu can update company information. You control which scopes you authorize. Do not authorize a scope unless you plan to use it. If you want to revoke a permission later, you can disconnect and reconnect with fewer scopes. Use Integrations in Your Workflows Sync Data from an Integration Many integrations support syncing. When you create a new table or add data to an existing table, you can choose to pull data from a connected integration. For example, you might create a table called "HubSpot Leads" and sync all your HubSpot contacts into it. TexAu then enriches that data and optionally pushes it back to HubSpot. Use Data Providers in Enrichment Some integrations are data providers (like email lookup services, company databases, etc.). When these are connected, you can use them in your enrichment workflows. For example, you might set up an Action column that uses a connected data provider to look up phone numbers and emails for each company in your table. Webhooks and Automation When you connect tools like Zapier or Make, you can create automated workflows. For example: "When enrichment completes in TexAu, send the results to Slack" or "When a new lead arrives in Salesforce, enrich it in TexAu and send it back." Standard vs. Premium Integrations Different integrations have different availability based on your TexAu plan. Standard Integrations: Available on all plans. These include popular tools like Salesforce, HubSpot, and basic data providers. Premium Integrations: Available on Premium plans and higher. These might include specialized data providers, advanced automation tools, or custom-built integrations. When you look at an integration you cannot connect, you see a note explaining which plan tier is required. Tip: If you need a premium integration but your plan does not include it, reach out to our sales team. We may have options to add it to your plan. Troubleshoot Connection Issues OAuth Connection Fails Problem: You click "Connect," get redirected, but then see an error. Solutions: - Check that you are using the correct login for the external service - Make sure your account has the necessary permissions (admin access for some integrations) - Clear your browser cookies and try again - Check that pop-ups are not being blocked (some services use pop-ups for OAuth) API Key Is Not Accepted Problem: You paste an API key, but TexAu says it is invalid. Solutions: - Double-check you copied the entire key (no extra spaces at the start or end) - Verify the key was generated from the correct account and service - Confirm the key has not expired (some APIs auto-expire keys after a set period) - Check that you are pasting the key in the correct field - Some services require extra info (like endpoint URL or username). Review the integration's documentation. Connection Shows "Expired" Problem: An OAuth connection suddenly shows as expired or disconnected. Solutions: - Click "Re-connect" and re-authorize the same way you did initially - This is usually temporary and happens with some OAuth providers - If re-connecting does not work, disconnect fully and reconnect from scratch Integration Is Not Syncing Data Problem: You connected an integration that supports syncing, but no data is coming through. Solutions: - Check that you actually set up syncing (connecting and syncing are two separate steps) - Verify the integration has read permissions - Check that there is actually data in the external service to sync - Try a manual sync if there is a "Sync Now" button Integrated Data Is Not Updating Problem: You synced data, but it is not refreshing when you make changes in the other tool. Solutions: - Check if the integration supports automatic syncing (some require manual syncs) - If it supports automatic syncing, check that you enabled it - Verify the integration has write permissions - Try a manual sync to see if that works Still Stuck? If none of these steps work, reach out to TexAu support with: - The integration you are trying to connect - Whether you are using OAuth or API key - The exact error message you are seeing - Screenshots if helpful We are here to help get you connected. What's Next? Once you have integrations connected, check out Managing Integrations to learn how to get the most out of them in your workflows.

Last updated on Apr 30, 2026

Datagma Integration Guide

Datagma Integration Guide This guide covers all Datagma actions available in TexAu. Datagma specializes in mobile phone number finding. Before you begin - A Datagma account is required. Sign up at datagma.com. - Your Datagma API key is on your Datagma dashboard. - In TexAu, go to Settings > Integrations, find Datagma, enter your API key, and click Save. Actions Find Mobile Number by LinkedIn URL (Datagma) Finds a mobile phone number using a LinkedIn profile URL. Credit cost: 15 credits per row Input: - LinkedIn Profile URL (required): full URL starting with https://linkedin.com/in/ Output: - Phone Number - Country - Local format - Number type (mobile, direct, company) Typical use case: Use as a fallback in a phone number waterfall after BetterEnrich and FullEnrich. Find Mobile Number Using Email (Datagma) Finds a mobile phone number when you have an email address. Credit cost: 20 credits per row Input: - Email Address (required) Output: - Phone Number - Country - Local format Typical use case: You have enriched email addresses and want to find associated phone numbers without LinkedIn URLs. Find Work Email Using Name and Company Domain (Datagma) Finds a work email address using a person's name and company domain. Credit cost: 4 credits per row Input: - First Name (required) - Last Name (required) - Company Domain (required): e.g., company.com Output: - Email Address - Confidence score - Verification status Using Datagma in a waterfall Datagma is particularly useful as a phone number fallback in waterfall enrichment. Phone waterfall example: 1. Find Mobile Number by LinkedIn URL (BetterEnrich), primary (10 credits, highest coverage) 2. Find Mobile Number using Linkedin Url (Apollo), fallback 1 (2 credits) 3. Find Mobile Number by LinkedIn URL (Datagma), fallback 2 (15 credits) 4. Find Mobile Number Using LinkedIn Profile URL (FullEnrich), fallback 3 Phone from email (no LinkedIn URL available): 1. If you have an email address but no LinkedIn URL, use Find Mobile Number Using Email (Datagma) to look up a phone number directly from the email address. This costs 20 credits per row. Troubleshooting Phone finding returns empty for most rows. Datagma's coverage varies by region. It is strongest in North America and Western Europe. If your list contains contacts from other regions, expect lower coverage. Find Mobile Number Using Email returns empty. The phone number may not be in Datagma's database for that email. Try passing the LinkedIn URL to Find Mobile Number by LinkedIn URL (Datagma) instead. Results include phone numbers but they are landlines, not mobiles. Datagma returns the best available number, which may be a direct line or company number. Check the Number type output field to filter for mobile-only results using a Formula Column: IF({{Number Type}} == "mobile", {{Phone Number}}, "").

Last updated on Apr 06, 2026

Findymail Integration Guide

Findymail Integration Guide This guide covers all Findymail actions available in TexAu. Findymail specializes in finding verified work and personal emails. Before you begin - A Findymail account is required. Sign up at findymail.com. - Your Findymail API key is on your Findymail dashboard under API. - In TexAu, go to Settings > Integrations, find Findymail, enter your API key, and click Save. Actions Find Email Using LinkedIn URL (Findymail) Finds a work email address using a LinkedIn profile URL. Credit cost: 2 credits per successful lookup Input: - LinkedIn Profile URL (required) -- full URL starting with https://linkedin.com/in/ Output: - Email Address - Verification status - Email type (work, personal) Typical use case: Email finding when BetterEnrich or FullEnrich return empty results. Findymail uses a different database so its coverage complements other providers. Find Email Using Name and Company Domain (Findymail) Finds a work email using a person's name and company domain. Credit cost: 2 credits per successful lookup Input: - First Name (required) - Last Name (required) - Company Domain (required) -- e.g., company.com Output: - Email Address - Verification status Find Mobile Number by LinkedIn URL (Findymail) Finds a mobile phone number using a LinkedIn profile URL. Credit cost: 10 credits per successful lookup Input: - LinkedIn Profile URL (required) Output: - Phone Number - Country - Local format Using Findymail in a waterfall Findymail is an effective fallback provider for email and phone finding. Email waterfall example: 1. Find Work Email by LinkedIn URL (BetterEnrich) -- primary 2. Find Email Using LinkedIn URL (Findymail) -- fallback 1 3. Find Work Email Using LinkedIn Profile URL (FullEnrich) -- fallback 2 Phone waterfall example: 1. Find Mobile Number by LinkedIn URL (BetterEnrich) -- primary (10 credits) 2. Find Mobile Number by LinkedIn URL (Findymail) -- fallback 3. Find Mobile Number Using LinkedIn Profile URL (FullEnrich) -- fallback Troubleshooting Findymail returns empty for many rows. This is expected for rows where no email is in Findymail's database. Use Findymail as a fallback in a waterfall, not as the only provider. The email output is a personal email, not a work email. Findymail sometimes returns personal emails when work emails are not available. Use a Formula Column to filter by domain: IF(CONTAINS({{Email}}, "{{Company Domain}}"), {{Email}}, ""). Rate limits are being hit. TexAu retries automatically with backoff. For very large tables, split the run into batches. Contact Findymail for information about your API rate limits.

Last updated on Apr 06, 2026

FullEnrich Integration Guide

FullEnrich Integration Guide This guide covers all FullEnrich actions available in TexAu. FullEnrich specializes in waterfall enrichment for work emails and mobile numbers. Before you begin - A FullEnrich account is required. Sign up at fullenrich.com. - Your FullEnrich API key is on your FullEnrich dashboard. - In TexAu, go to Settings > Integrations, find FullEnrich, enter your API key, and click Save. Email finding actions Find Work Email Using LinkedIn Profile URL (FullEnrich) Finds a work email address using a LinkedIn profile URL. Credit cost: 15 credits per successful lookup Input: - LinkedIn Profile URL (required) -- full URL starting with https://linkedin.com/in/ Output: - Email Address - Email Verification Status - Domain - Confidence score Typical use case: Primary email finding action when you have LinkedIn URLs. FullEnrich aggregates data from multiple sources internally to maximize coverage. Find Work Email by Name and Domain (FullEnrich) Finds a work email using a person's full name and company domain. Credit cost: 10 credits per successful lookup Input: - First Name (required) - Last Name (required) - Company Domain (required) -- e.g., company.com Output: - Email Address - Verification Status - Confidence score Typical use case: Use when LinkedIn URLs are not available and you have names plus company data. Phone finding actions Find Mobile Number Using LinkedIn Profile URL (FullEnrich) Finds a mobile phone number using a LinkedIn profile URL. Credit cost: 20 credits per successful lookup Input: - LinkedIn Profile URL (required) Output: - Phone Number - Country - Local format - Number type (mobile, direct) Find Mobile Number by Name and Domain (FullEnrich) Finds a mobile number using a person's name and company domain. Credit cost: 25 credits per successful lookup Input: - First Name (required) - Last Name (required) - Company Domain (required) Output: - Phone Number - Country - Local format Using FullEnrich in a waterfall FullEnrich works well as a secondary or tertiary provider in waterfall enrichment alongside BetterEnrich or Apollo. Example waterfall for email (recommended order): 1. Find Work Email by LinkedIn URL (BetterEnrich) -- primary, high accuracy 2. Find Work Email Using LinkedIn Profile URL (FullEnrich) -- fallback 1 3. Find Email Using LinkedIn URL (Apollo) -- fallback 2 Set each subsequent column to run only when the previous column is empty. Example waterfall for phone: 1. Find Mobile Number by LinkedIn URL (BetterEnrich) -- primary 2. Find Mobile Number Using LinkedIn Profile URL (FullEnrich) -- fallback 1 3. Find Mobile Number by LinkedIn URL (Apollo) -- fallback 2 Troubleshooting Email finding returns empty for rows where other providers find data. Coverage varies by provider. FullEnrich has its own database. Rows where FullEnrich returns empty may be found by another provider in the waterfall. This is expected behavior. Mobile numbers return with country code but not local format. Use the Normalize Phone Number utility action to convert the output to the format you need. The API key is accepted but requests return 429 (rate limit). Your FullEnrich plan may have request rate limits. TexAu retries automatically, but very large batches may take longer to complete. Run smaller batches or contact FullEnrich to upgrade your plan's rate limit. Results quality is lower than expected. FullEnrich enriches internally using multiple sources. If accuracy is lower than needed, supplement with a verification step using Verify Email (BetterEnrich) on the output.

Last updated on Apr 06, 2026

GoHighLevel / LeadConnector Integration Guide

GoHighLevel / LeadConnector Integration Guide This guide covers all GoHighLevel (also called LeadConnector) actions available in TexAu. All LeadConnector actions in TexAu cost 0 credits. You only pay for the credits on your GoHighLevel side. Before you begin - A GoHighLevel account is required. Sign up at gohighlevel.com. - Your GoHighLevel API key is at Settings > Integrations > API Key inside GoHighLevel. - In TexAu, go to Settings > Integrations, find LeadConnector or GoHighLevel, enter your API key, and click Save. Contact actions Create Contact Creates a new contact in GoHighLevel. Input: - Email (optional -- email or phone is required) - Phone (optional -- email or phone is required) - First Name, Last Name (optional) - Address (optional) - Tags (optional -- comma-separated list) - Company Name (optional) Output: - Contact ID - Creation status Upsert Contact Creates a new contact or updates an existing one if a match is found by email or phone. Input: - Email or Phone (required for matching) - Fields to update Output: - Contact ID - Upsert action (created or updated) Get Contact Returns details for a single contact by ID. Input: - Contact ID (required) Output: - All contact fields including custom fields Update Contact Updates fields on an existing contact. Input: - Contact ID (required) - Fields to update Output: - Update status Delete Contact Deletes a contact from GoHighLevel. Input: - Contact ID (required) Output: - Deletion status Search Contacts Searches contacts by name, email, or phone. Input: - Search query Output: - Array of matching contacts Add Tag Adds one or more tags to a contact. Input: - Contact ID (required) - Tags (required -- one tag or comma-separated list) Output: - Tag addition status Remove Tag Removes one or more tags from a contact. Input: - Contact ID (required) - Tags to remove Output: - Removal status Business / Company actions Create Business/Company Creates a new business record. Input: - Name (required) - Website (optional) - Phone (optional) - Email (optional) - Address (optional) - Description (optional) Output: - Business ID Get Business/Company Returns details for a specific business record. Input: - Business ID (required) Output: - All business fields Update Business/Company Updates an existing business record. Input: - Business ID (required) - Fields to update Output: - Update status Delete Business/Company Deletes a business record. Input: - Business ID (required) Output: - Deletion status Get Businesses by Location Returns all businesses associated with a specific sub-account (location). Input: - Location ID (required) Output: - Array of business records Opportunity actions Create Opportunity Creates a new opportunity (deal) in a pipeline. Input: - Pipeline ID (required) - Stage ID (required) - Name (required) - Contact ID (optional) - Monetary value (optional) - Status (optional) Output: - Opportunity ID Upsert Opportunity Creates or updates an opportunity based on matching criteria. Input: - Pipeline ID (required) - Contact ID (required) - Fields Output: - Opportunity ID - Upsert action Get Opportunity Returns details for a specific opportunity. Input: - Opportunity ID (required) Output: - All opportunity fields Update Opportunity Updates an existing opportunity. Input: - Opportunity ID (required) - Fields to update Output: - Update status Update Opportunity Status Changes the status of an opportunity (open, won, lost, abandoned). Input: - Opportunity ID (required) - Status (required) Output: - Update status Delete Opportunity Deletes an opportunity. Input: - Opportunity ID (required) Output: - Deletion status Search Opportunities Searches opportunities by contact or pipeline. Input: - Search query or Pipeline ID Output: - Array of matching opportunities Appointment and calendar actions Create Appointment Creates a new appointment. Input: - Calendar ID (required) - Contact ID or email (required) - Start date/time (required) - End date/time (required) - Title (optional) Output: - Appointment ID Get Appointment Returns details for a specific appointment. Input: - Appointment ID (required) Output: - Appointment details Get Calendars Returns all calendars in the GoHighLevel account. Input: None Output: - Array of calendar IDs and names Create Calendar Creates a new calendar. Input: - Name (required) - Location ID (required) - Timezone (optional) Output: - Calendar ID Get Calendar Events Returns events for a specific calendar in a date range. Input: - Calendar ID (required) - Start date (required) - End date (required) Output: - Array of calendar events Conversation and messaging actions Get Conversation Returns a conversation record by ID. Input: - Conversation ID (required) Output: - Conversation details including contact, channel, and messages Search Conversations Searches conversations by contact or keyword. Input: - Search query Output: - Array of conversations Get Conversation Messages Returns messages within a specific conversation. Input: - Conversation ID (required) Output: - Array of messages with content, timestamp, and direction (inbound/outbound) Send Message Sends a message to a contact in GoHighLevel. Input: - Contact ID or Conversation ID (required) - Message type (SMS, email, etc.) - Message body (required) Output: - Message ID - Send status Add Inbound Message Adds an inbound message record to a conversation. Input: - Conversation ID (required) - Message body (required) Output: - Message ID Update Message Status Updates the delivery status of a message. Input: - Message ID (required) - Status (required) Output: - Update status Workflow and task actions Get Workflows Returns all automation workflows in GoHighLevel. Input: None Output: - Array of workflow IDs and names Get All Tasks Returns all tasks. Input: - Contact ID (optional -- filter by contact) Output: - Array of tasks with due date, title, and status Sub-account / location actions Get Sub-Account/Location Returns details for a specific GoHighLevel sub-account (location). Input: - Location ID (required) Output: - Sub-account name, address, phone, email, timezone Search Locations Searches sub-accounts by name. Input: - Search query (required) Output: - Array of matching sub-accounts Custom fields and values Get Custom Fields Returns all custom field definitions for contacts in a sub-account. Input: - Location ID (optional) Output: - Array of field keys and types Get Custom Values Returns the custom values (snippets) set in a sub-account. Input: - Location ID (optional) Output: - Array of custom keys and values Get Tags Returns all tags available in the account. Input: None Output: - Array of tag names Get Pipelines Returns all opportunity pipelines. Input: None Output: - Array of pipeline IDs and names Troubleshooting Create Contact fails with no error but the contact does not appear. GoHighLevel may have silently rejected the record due to a validation issue. Confirm that at least one of email or phone is provided. Custom fields are not saving on Create Contact. Custom fields in GoHighLevel use internal key names (not the display names shown in the UI). Use Get Custom Fields to retrieve the exact field keys, then map them in the action configuration. The API returns "Location not found". GoHighLevel sub-accounts (locations) each have a unique ID. Confirm you are using the Location ID, not the location name or account name. Opportunities are being created without a contact. Contact ID is optional in Create Opportunity but assignments are recommended. If the Contact ID column is empty for some rows, those opportunities will be created unassigned.

Last updated on Apr 06, 2026

HeyReach Integration Guide

HeyReach Integration Guide This guide covers all HeyReach actions available in TexAu. Use these actions to manage your LinkedIn outreach campaigns through HeyReach. All HeyReach actions in TexAu cost 0 credits. You only pay for the credits on your HeyReach side. Before you begin - A HeyReach account is required. Sign up at heyreach.io. - Your HeyReach API key is at Settings > Integrations inside HeyReach. - In TexAu, go to Settings > Integrations, find HeyReach, enter your API key, and click Save. Campaign actions Get All Campaigns (HeyReach) Returns a list of all campaigns in your HeyReach account. Input: None Output: - Array of campaigns with: - Campaign ID - Campaign Name - Status (active, paused, completed) - Number of leads - Number of LinkedIn accounts assigned Use this action first to find the Campaign ID you need for other actions. Add Leads to Campaign (HeyReach) Adds one or more leads to a specific HeyReach outreach campaign. Input: - Campaign ID (required) - LinkedIn Profile URL (required) - First Name (optional) - Last Name (optional) - Company Name (optional) - Custom variables (optional -- used in message templates) Output: - Lead addition status - Lead ID in HeyReach Typical use case: After building a prospecting list in TexAu, send qualified leads directly to a HeyReach LinkedIn outreach campaign. Get Leads from Campaign (HeyReach) Returns the leads in a specific HeyReach campaign along with their outreach status. Input: - Campaign ID (required) - Limit (optional) Output per lead: - LinkedIn Profile URL - First Name, Last Name - Connection status - Message sent status - Reply status Account actions List LinkedIn Accounts (HeyReach) Returns all LinkedIn accounts connected to HeyReach. Input: None Output: - Array of LinkedIn accounts with: - Account ID - LinkedIn profile name - Connection status - Daily limit settings Typical use case: Use before adding leads to confirm your LinkedIn accounts are active. Common workflow pattern Identify leads on LinkedIn and add to HeyReach 1. Start with a list of company names or job titles in a TexAu table. 2. Add an Action Column for Search LinkedIn Profiles (Apify) to find relevant profiles. 3. Add a second Action Column for Get LinkedIn Profile Detail (Apify) for enrichment. 4. Add a third Action Column for Add Leads to Campaign (HeyReach) mapping LinkedIn URL and first/last name. 5. Run enrichment. LinkedIn URLs flow automatically from the search results into HeyReach. Troubleshooting Add Leads to Campaign returns "campaign not found". Run Get All Campaigns to confirm the Campaign ID. HeyReach Campaign IDs are numeric. Do not use the campaign name. Leads are added but are not being contacted. Verify that: - The campaign is active (not paused or completed). - At least one LinkedIn account is assigned to the campaign. - The assigned LinkedIn account is connected and not restricted. Run List LinkedIn Accounts to check account status. Custom variables are not appearing in messages. Check that the variable names in your HeyReach message template match exactly the variable keys you send in the Add Leads action (including case). Get Leads from Campaign returns empty. The campaign may have no leads yet, or the Campaign ID is incorrect. Use Get All Campaigns to confirm the campaign ID and lead count.

Last updated on Apr 06, 2026

HubSpot Integration Guide

HubSpot Integration Guide This guide covers all HubSpot actions available in TexAu. Use these actions to read from and write to your HubSpot CRM directly from a table. All HubSpot actions in TexAu cost 0 credits. You only pay for the credits on your HubSpot side. Before you begin - A HubSpot account is required. Free and paid plans are both supported. - Connect HubSpot to TexAu using OAuth. Go to Settings > Integrations, find HubSpot, and click Connect with OAuth. - Sign in to HubSpot in the window that opens and click Grant access. - The integration is now connected. TexAu uses your HubSpot user's access level. Contact actions Search Contacts Searches your HubSpot contacts by name, email, or other properties. Input: - Search query -- email address, name, or keyword - Property filters (optional) Output: - Contact ID - First Name, Last Name - Email - Company Name - Job Title - HubSpot Contact URL Get Contact Retrieves full details for a single HubSpot contact by ID. Input: - Contact ID (required) Output: - All standard contact properties - Lifecycle stage - Creation date - Last modified date Get Contact by ID Same as Get Contact. Use when you already have the HubSpot Contact ID in your table. Input: - HubSpot Contact ID (required) Output: - Full contact property set Create Contact Creates a new contact in HubSpot. Input: - Email (required) - First Name (optional) - Last Name (optional) - Job Title (optional) - Company Name (optional) - Phone (optional) - LinkedIn URL (optional) - Additional properties (optional) Output: - HubSpot Contact ID - HubSpot Contact URL - Creation status Typical use case: Push enriched prospects from TexAu into HubSpot after enrichment run. Update Contact Updates properties on an existing HubSpot contact. Input: - HubSpot Contact ID (required) - Properties to update (supply column references for each) Output: - Update status - Updated Contact ID Delete Contact Deletes a contact from HubSpot by Contact ID. Input: - HubSpot Contact ID (required) Output: - Deletion status Merge Contacts Merges two HubSpot contacts into one. Input: - Primary Contact ID (the one to keep) - Secondary Contact ID (the one to merge into the primary) Output: - Merge status - Resulting Contact ID List Contacts Returns a list of contacts from HubSpot, with optional filtering. Input: - Limit (number of results to return) - Filters (optional) Output: - Array of contacts (ID, email, name, company for each) Enrol Contact in Sequence Adds a contact to a HubSpot email sequence. Input: - Contact ID (required) - Sequence ID (required) Output: - Enrollment status Company actions Create Company Creates a new company record in HubSpot. Input: - Company Name (required) - Domain (optional) - Industry (optional) - Employee Count (optional) - Phone (optional) - City, Country (optional) Output: - HubSpot Company ID - Company URL List Companies Returns a list of company records. Input: - Limit (optional) Output: - Array of companies (ID, name, domain for each) Get Company by ID Retrieves a HubSpot company record by its ID. Input: - Company ID (required) Output: - All company properties Update Company Updates properties on an existing company record. Input: - Company ID (required) - Properties to update Output: - Update status Delete Company Deletes a company record from HubSpot. Input: - Company ID (required) Output: - Deletion status Search Companies Searches company records by name, domain, or other properties. Input: - Search query Output: - Array of matching companies Merge Companies Merges two company records into one. Input: - Primary Company ID - Secondary Company ID Output: - Merge status Deal actions Create Deal Creates a new deal in HubSpot. Input: - Deal Name (required) - Pipeline ID (required) - Stage ID (required) - Amount (optional) - Close Date (optional) - Associated Contact ID (optional) Output: - Deal ID - Deal URL List Deals Returns a list of deals from HubSpot. Input: - Limit (optional) - Pipeline ID (optional) Output: - Array of deals (ID, name, stage, amount) Get Deal by ID Retrieves a deal record by its ID. Input: - Deal ID (required) Output: - All deal properties Search Deals Searches deals by name or other properties. Input: - Search query Output: - Array of matching deals Update Deal Updates properties on an existing deal. Input: - Deal ID (required) - Properties to update Output: - Update status Delete Deal Deletes a deal from HubSpot. Input: - Deal ID (required) Output: - Deletion status Merge Deals Merges two deal records. Input: - Primary Deal ID - Secondary Deal ID Output: - Merge status Get Deal Properties Returns the list of all available deal properties in your HubSpot account. Input: None Output: - Array of property names, types, and labels Lead actions Create Lead Creates a new lead in HubSpot. Input: - Associated Contact ID or Email (required) - Lead Name (optional) - Pipeline and Stage (optional) Output: - Lead ID - Lead URL List Leads Returns a list of lead records. Input: - Limit (optional) Output: - Array of leads Pipeline and property actions Get All Pipelines Lists all deal pipelines in your HubSpot account. Input: None Output: - Array of pipeline IDs and names Get Pipeline Stages Returns the stages for a specific pipeline. Input: - Pipeline ID (required) Output: - Array of stage IDs, names, and positions Get All Properties Returns all contact or company properties defined in HubSpot. Input: - Object type (contact or company) Output: - Array of property names and types Get All Property Groups Returns property groups for contacts or companies. Input: - Object type Output: - Array of group names and associated properties Create Property Creates a custom property in HubSpot. Input: - Object type (contact, company, deal) - Property name - Property label - Property type (text, number, date, checkbox, select) - Group name Output: - Property creation status Other actions Get Owners Returns a list of HubSpot users (owners). Input: None Output: - Array of owner IDs, names, and email addresses List Users Returns all users in your HubSpot account. Input: None Output: - User ID, email, name, role for each user Get Engagements Returns engagement records (calls, emails, notes) for a contact or deal. Input: - Object type (contact or deal) - Object ID Output: - Array of engagements with type, date, and content Create Engagement Creates a note, call, or email record in HubSpot. Input: - Engagement type (note, call, email) - Associated contact or deal ID - Content or body - Date (optional) Output: - Engagement ID Get All Campaigns Returns a list of HubSpot marketing campaigns. Input: None Output: - Array of campaign IDs, names, and statuses Get CRM Associations, Create CRM Association, Delete CRM Association, Get Association Labels These actions manage the relationships (associations) between CRM records (e.g., linking a contact to a deal). Input: - Object type and ID for the source - Object type and ID for the target Output: - Association status or list of associations Troubleshooting Contact creation fails with "email already exists". HubSpot does not allow duplicate contacts by email. Use Search Contacts first to check if the contact exists, then use Update Contact if it does. Pipeline Stage ID is required but I do not know it. Run Get Pipeline Stages without input. It returns all stage IDs for each pipeline. Copy the ID of the stage you want. The integration returns "insufficient permissions". The HubSpot user who authorized TexAu does not have permission to write to the object you are trying to create. Ask a HubSpot admin to reconnect TexAu using an account with the required permissions. I see a 429 error in the run log. HubSpot has rate limits on API calls. TexAu backs off and retries automatically, but very large runs may hit the limit. Run smaller batches or contact support for guidance on bulk operations.

Last updated on Apr 06, 2026

Hunter.io Integration Guide

Hunter.io Integration Guide This guide covers all Hunter.io actions available in TexAu. Hunter.io specializes in finding and verifying work emails and enriching company data. Before you begin - A Hunter.io account is required. Sign up at hunter.io. - Your Hunter.io API key is at API in the left sidebar of your Hunter.io dashboard. - In TexAu, go to Settings > Integrations, find Hunter.io, enter your API key, and click Save. Email finding actions Find Email Using Name and Company Domain (Hunter.io) Finds a work email address using a person's name and company domain. Credit cost: 2 credits per successful lookup Input: - First Name (required) - Last Name (required) - Company Domain (required) -- e.g., stripe.com, not the full URL Output: - Email Address - Email type (personal or generic) - Confidence score (0-100) - Verification status - Sources Typical use case: Find emails for a list of prospects when you have names and company domains but no LinkedIn URLs. Phone finding actions Find Mobile Number by LinkedIn URL (Hunter.io) Finds a phone number using a LinkedIn profile URL. Credit cost: 20 credits per successful lookup Input: - LinkedIn Profile URL (required) Output: - Phone Number - Phone type Find Mobile Number Using Email (Hunter.io) Finds a phone number when you have an email address. Credit cost: 20 credits per successful lookup Input: - Email Address (required) Output: - Phone Number - Phone type Typical use case: After finding an email with another action, pass it to Hunter.io to find a phone number. Company enrichment Enrich Company (Hunter.io) Returns information about a company based on its domain. Credit cost: 2 credits per successful lookup Input: - Company Domain (required) -- e.g., stripe.com Output: - Company Name - Industry - Employee Count - Location (city, state, country) - LinkedIn Company URL - Twitter URL - Technologies - Patterns -- the email format the company uses (e.g., {first}.{last}@domain.com) Typical use case: Understand the company structure and email format before running email finding at scale. Understanding confidence scores Hunter.io returns a confidence score (0-100) with email results. - 90-100: Very high confidence. The email is almost certainly correct and deliverable. - 70-89: High confidence. Run email verification before sending. - 50-69: Medium confidence. Verify before sending. - Below 50: Low confidence. The email may be wrong or outdated. Use a Formula Column to filter out low-confidence results: IF({{Confidence Score}} >= 70, {{Email}}, "") Troubleshooting Find Email returns an email but the confidence score is low. Hunter.io could not confirm the email with a strong signal. Run Verify Email (BetterEnrich) on these results to confirm deliverability before sending. Enrich Company does not return an email pattern. Not all domains have discoverable email patterns. Hunter.io returns patterns only when it has enough confirmed email data for that domain. API returns "over the quota". Your Hunter.io plan has a monthly request limit. Check your usage at hunter.io/account/billing. Upgrade your Hunter.io plan or use a different provider for the remainder of the month. Email finding returns empty for a domain that definitely has employees. The domain may use a custom email server that Hunter.io has not indexed. Try Find Email Using Name and Domain (Apollo) or Find Work Email from Full Name and Company Domain (BetterEnrich) as a fallback.

Last updated on Apr 06, 2026

Icypeas Integration Guide

Icypeas Integration Guide This guide covers the Icypeas integration available in TexAu. Use it to find professional email addresses using a person's name and company domain. Before you begin - You need an active Icypeas account. Sign up at icypeas.com. - Retrieve your API key from your Icypeas account dashboard under API Settings. - In TexAu, go to Settings > Integrations, find Icypeas, and paste your API key. Actions Find Email by Name and Domain (Icypeas) Finds a professional email address for a contact using their first name, last name, and company domain. Credit cost: 2 credits per successful lookup Input: - First Name (required) - Last Name (required) - Domain (required) -- company domain only, e.g. acme.com -- not the full website URL Output: - Email Address - First Name - Last Name - Full Name - Status -- indicates whether an email was found Typical use case: Email discovery when you have a contact list with names and company domains but no email addresses. How Icypeas works Icypeas uses an email pattern detection approach. It searches known email patterns for the domain and matches them against the name you provide. This makes it reliable for companies with consistent email naming conventions (e.g., [email protected]). Note on the Domain field: Enter only the domain portion. Strip https://, www., and any paths. For example: - Correct: acme.com - Incorrect: https://www.acme.com/contact Common workflow pattern Find emails for a contact list 1. Start with a table that has First Name, Last Name, and Company Domain columns. 2. Add an Action Column and select Find Email by Name and Domain (Icypeas). 3. Map First Name, Last Name, and Domain to the appropriate input fields. 4. Run the column. 5. Review the Email Address and Status output columns. Place this action in a Waterfall after other email finders to catch contacts the primary source misses. Troubleshooting The Status field shows no result but contact details look correct. Icypeas relies on the company domain having a detectable email pattern. Some companies use individual email formats, personal accounts, or privacy-protected domains. In these cases, try a different email finder as a fallback. Domain field is mapped correctly but returning errors. Confirm the domain does not include http://, www., or trailing slashes. Use a formula column to clean the domain before passing it to this action: REPLACE(REPLACE(domain_column, "https://www.", ""), "https://", ""). API key not accepted in Settings. Check for leading or trailing spaces when copying the key. Icypeas API keys are case-sensitive. Generate a new key from your Icypeas dashboard if the problem persists.

Last updated on Apr 06, 2026

Instantly Integration Guide

Instantly Integration Guide This guide covers all Instantly actions available in TexAu. Use these actions to manage leads and campaigns in your Instantly email outreach account. All Instantly actions in TexAu cost 0 credits. You only pay for the credits on your Instantly side. Before you begin - An Instantly account is required. Sign up at instantly.ai. - Your Instantly API key is at Settings > API inside Instantly. - In TexAu, go to Settings > Integrations, find Instantly, enter your API key, and click Save. Lead actions Create Lead Creates a new lead in Instantly. Input: - Email (required) - First Name (optional) - Last Name (optional) - Company Name (optional) - Phone (optional) - Website (optional) - Custom variables (optional -- key-value pairs for personalization) Output: - Lead ID - Creation status Typical use case: After enriching a TexAu table with verified emails, push leads to Instantly for outreach. Update Lead Updates an existing lead's fields in Instantly. Input: - Email (required -- used to identify the lead) - Fields to update Output: - Update status List Leads Returns a list of leads in your Instantly account. Input: - Limit (optional) - Campaign ID (optional -- filter by campaign) Output: - Array of leads with email, name, and campaign status Add Lead To Sequence Adds an existing lead to a specific Instantly email sequence. Input: - Email (required) - Campaign ID (required) Output: - Enrollment status Campaign actions List Campaigns Returns all campaigns in your Instantly account. Input: None Output: - Array of campaigns with ID, name, and status Common workflow pattern Enrich then add to Instantly campaign 1. Paste a list of LinkedIn URLs into a TexAu table. 2. Add an Action Column for email finding (e.g., Find Work Email by LinkedIn URL (BetterEnrich)). 3. Add an Action Column for Verify Email (BetterEnrich) to confirm deliverability. 4. Add a Formula Column: IF({{Deliverable}} == "true", {{Email}}, "") to blank out bad emails. 5. Add an Action Column for Create Lead (Instantly) mapping First Name, Last Name, and Email. 6. Add an Action Column for Add Lead To Sequence (Instantly) using the Campaign ID. 7. Run enrichment. Only rows with deliverable emails advance to Instantly. Troubleshooting Create Lead returns "lead already exists". Instantly uses email as the unique identifier for leads. If the email already exists, use Update Lead instead. Add Lead To Sequence returns "campaign not found". Use List Campaigns to retrieve the correct Campaign ID. Campaign IDs are alphanumeric strings, not the campaign name. Leads are created in Instantly but are not being emailed. Check that the campaign is active and that your Instantly sending account is connected and warmed up. Leads added to paused campaigns queue but do not receive emails until the campaign resumes. I need to add custom personalization variables. Use the custom variables input in Create Lead. Map a TexAu column to a custom variable key (e.g., {{variable_icebreaker}} = your AI Column output). These variables are available in your Instantly email templates.

Last updated on Apr 06, 2026

LeadMagic Integration Guide

LeadMagic Integration Guide This guide covers all LeadMagic actions available in TexAu. Use these actions to find and validate contact data. Before you begin - A LeadMagic account is required. Sign up at leadmagic.io. - Your LeadMagic API key is on your LeadMagic dashboard. - In TexAu, go to Settings > Integrations, find LeadMagic, enter your API key, and click Save. Contact finding actions Find Email by Name and Domain (LeadMagic) Finds a work email address using a person's name and company domain. Credit cost: 2 credits per successful lookup Input: - First Name (required) - Last Name (required) - Company Domain (required) -- e.g., stripe.com Output: - Email Address - Confidence score - Verification status Typical use case: Use when you have names and company websites but no LinkedIn URLs. Find Personal Email (LeadMagic) Finds a personal (non-work) email for a contact. Credit cost: 2 credits per successful lookup Input: - LinkedIn Profile URL or name + company (required) Output: - Personal Email Address - Email type Typical use case: Reach contacts who are hard to reach on work email, or to verify a contact's identity. Find Mobile Number using LinkedIn URL (LeadMagic) Finds a mobile phone number using a LinkedIn profile URL. Credit cost: 10 credits per successful lookup Input: - LinkedIn Profile URL (required) Output: - Phone Number - Country - Local format Enrich Company (LeadMagic) Returns firmographic data for a company based on its domain. Credit cost: 1 credit per successful lookup Input: - Company Domain (required) Output: - Company Name - Industry - Employee Count - Revenue Range - Location - LinkedIn Company URL - Technologies Validation actions Validate Email (LeadMagic) Checks whether an email address is deliverable. Credit cost: 1 credit per row Input: - Email Address (required) Output: - Valid -- true/false - Deliverable -- true/false - Email type (work, personal, catch-all, unknown) - SMTP check result - Reason Typical use case: Run this after finding emails to remove invalid addresses before sending to an outreach tool. Common workflow pattern Find, verify, and enrich in one table 1. Start with a list of names and company domains. 2. Add an Action Column for Find Email by Name and Domain (LeadMagic). 3. Add a second Action Column for Validate Email (LeadMagic) using the email output. 4. Add a third Action Column for Enrich Company (LeadMagic) using the domain column. 5. Run enrichment. You end up with verified emails and company details in the same table, ready for export. Troubleshooting Find Email returns empty for most rows. Check that the Company Domain field contains the root domain only (e.g., acme.com) with no https://, www., or trailing slashes. Validate Email returns "unknown" for many addresses. Catch-all domains return "unknown" because the server accepts all mail. Use a different provider (e.g., Verify Catch-All Email (BetterEnrich)) to specifically identify catch-all domains. Find Mobile Number returns empty for all rows. LeadMagic's phone database is strongest for North American and Western European numbers. Coverage for other regions may be limited. API key is accepted but returns 401 on first run. Your LeadMagic account may need to be activated for API access. Check your LeadMagic dashboard for any prompts to enable API access.

Last updated on Apr 06, 2026

Manage Your Integrations

Manage Your Integrations Once you have connected your integrations, this guide covers how to monitor their health, re-authenticate expired connections, and use them effectively in your enrichment workflows. View All Your Connected Integrations Go to Settings, then Integrations. You see a dashboard showing: - Integration Name: The name of the service (for example, "Salesforce," "HubSpot," "DataProvider XYZ") - Status: Connected, Not Connected, Expired, or Error - Connection Date: When you first connected it - Last Activity: The most recent time TexAu used this integration - Actions: Buttons to manage the integration (re-authenticate, disconnect, etc.) At a glance, you can see which integrations are active, which need attention, and which have not been used recently. Check Integration Status and Health Green Status = All Good If an integration shows a green checkmark and "Connected" status, it is healthy and ready to use. No action needed. Yellow/Amber Status = Caution A yellow status usually means the integration is working but there is something you should know: - Soon to Expire: Some OAuth tokens have expiration dates. If you see this status, re-authenticate within the next few days to avoid interruptions. - Limited Permissions: The integration has fewer permissions than typical. This might be by design (you limited permissions for security), but check that you have the permissions you need. Red Status = Action Required A red status means the integration is not working and needs your attention: - Expired: The OAuth token has expired. Click Re-connect to refresh it. - Invalid API Key: An API key is no longer valid. Generate a new key in the external service and update it in TexAu. - Authorization Revoked: You revoked TexAu's access in the external service. Disconnect in TexAu and reconnect to re-authorize. - Service Unavailable: The external service is temporarily down or unreachable. Try again in a few minutes. Check Detailed Integration Info Click on an integration to see more details: - Full permission list (for OAuth) - API endpoint or URL (for API key integrations) - Data sources available (if the integration provides multiple data sources) - Recent sync history (if the integration supports syncing) - Any error messages or issues This is useful for diagnosing problems or understanding what data the integration can access. Re-Authenticate Expired Connections OAuth connections sometimes expire. This typically happens when: - The external service's token expires (varies by service, but often 30 to 90 days) - You revoke TexAu's access in the external service and want to reconnect - You want to update the permissions TexAu has When you see an "Expired" status next to an integration: 1. Click Re-connect next to the expired integration 2. You are redirected to the external service 3. Authorize TexAu again. You may be asked to update permissions. Review them and confirm. 4. You return to TexAu with a refreshed connection This usually takes less than a minute. Tip: Set a calendar reminder to check your integrations monthly. Proactively re-authenticating expiring connections prevents disruptions to your enrichment workflows. Integration Permissions and Scopes For OAuth integrations, permissions are managed through "scopes." A scope is a set of permissions (like "read leads" or "write organizations"). Understand What Permissions You Have Granted When you view an OAuth integration, you see the list of scopes TexAu has access to. Common scopes include: - Read Contacts/Leads: Can pull contact and lead information - Write Contacts/Leads: Can update contact and lead records - Read Organizations: Can pull company/account information - Write Organizations: Can update company/account records - Read Custom Fields: Can access custom fields in the external system - Delete Contacts: Can remove contacts (rarely needed) Review this list and make sure it matches what you are actually using. Update Permissions If you want to change permissions (grant new ones or revoke existing ones): 1. Click Disconnect next to the integration 2. Click Connect again to reconnect 3. During the authorization flow, you see the updated permission request 4. Approve only the permissions you want 5. Complete the connection This reconnects the integration with a new set of permissions. The Principle of Least Privilege Security recommendation: Only authorize permissions you actually need. If you only pull data but never write data back, do not authorize write permissions. This reduces risk if anything ever goes wrong. Use Integrations in Your Enrichment Workflows Use Integrations as Data Sources When you create a new table or add data to an existing table, many integrations let you sync data directly. Example: You have Salesforce connected. You want a table of all your B2B leads from the "Enterprise" segment in Salesforce. 1. Create a new table in TexAu called "Enterprise Leads" 2. Choose Sync from Integration 3. Select Salesforce as the source 4. Configure filters (for example, "Segment = Enterprise") 5. Click Sync TexAu pulls your data from Salesforce into the table. Now you can enrich it and optionally push results back to Salesforce. Use Data Providers in Enrichment Columns Some integrations are data providers (like email lookup services, company databases, etc.). When you create an Action column, you can use these providers to automatically look up or enrich data. Example: You have a data provider connected that provides phone numbers and emails. You have a table of companies with only names and domains. 1. Create a new column in your table called "Company Email" 2. Choose Action Column as the column type 3. Select your connected email provider 4. Map the company name or domain as the input 5. The provider looks up the email and populates the column Sync Enriched Data Back to External Tools After you enrich data in TexAu, you can push it back to your CRM, email tool, or other connected service. Example: You have enriched a table of leads with scores, personalized messages, and company insights. Now you want to sync that enriched data back to Salesforce. 1. In the enriched table, click Sync Results 2. Choose Salesforce as the destination 3. Map TexAu columns to Salesforce fields (for example, "Lead Score" to "Salesforce Custom Field: Lead Score") 4. Click Sync TexAu pushes your enriched data back to Salesforce, updating records in real time. Real-Time Syncing and Automation For some integrations, you can set up automatic syncing: - Inbound: New data in the external service automatically flows into TexAu tables - Outbound: Enriched data in TexAu automatically syncs back to the external service Once set up, this happens automatically with no manual work required. Example: You set up automatic inbound syncing from Salesforce. Every time a new lead is created in Salesforce, it automatically appears in your TexAu table, gets enriched, and syncs back to Salesforce with enrichment results. Standard vs. Premium Integrations TexAu offers integrations at different plan levels: Standard Integrations Available on all plans. Examples: - Salesforce - HubSpot - Basic data providers - Popular automation tools (Zapier, Make) Premium Integrations Available on Premium plans and higher. Examples: - Specialized data providers (industry-specific databases) - Advanced CRM systems (certain niche tools) - Custom-built integrations for enterprise customers - High-volume data providers with advanced features Not seeing a premium integration on your plan? You have options: 1. Upgrade Your Plan: If you need just one premium integration, upgrading might make sense. 2. Use Zapier/Make as a Bridge: If the integration does not exist natively, you can often use Zapier or Make to connect to almost any service. 3. Contact Sales: Reach out to our sales team. We sometimes add premium integrations to certain plans based on customer needs. Best Practices for Integration Management 1. Regularly Check Integration Health Once a month, visit Settings, then Integrations and do a quick health check: - Are all your active integrations showing "Connected"? - Do any show "Expired" status? - Are there any error messages? This takes 5 minutes and prevents problems down the line. 2. Disconnect Integrations You Do Not Use If you are no longer using an integration, disconnect it. This reduces clutter, improves security (fewer credentials exposed), and simplifies your settings. Disconnecting is safe. You can always reconnect later. 3. Document Your Integration Setup Keep a simple record of which integrations you are using and what you use them for: - "Salesforce: Sync leads in, push enrichment back" - "HubSpot: Data provider for company info lookup" - "Zapier: Send enrichment notifications to Slack" This helps when you are troubleshooting or onboarding team members. 4. Test After Re-Authentication If you re-authenticate an expired connection, do a quick test to make sure it is working: - Sync a small batch of data - Run an enrichment that uses the integration - Check that data is flowing correctly This catches any permission or configuration issues before they affect your full workflows. 5. Be Intentional About Permissions When authorizing an integration, review the permissions carefully. Only authorize what you need. This is especially important for write permissions (which modify data in the external service). Disconnect an Integration If you want to fully disconnect an integration: 1. Go to Settings, then Integrations 2. Find the integration you want to disconnect 3. Click Disconnect 4. Confirm that you want to disconnect When you disconnect: - TexAu no longer has access to the external service - Any stored credentials (API keys, tokens) are deleted - Active syncs pause (you can resume later by reconnecting) - You can reconnect at any time Disconnecting does not delete any data in TexAu or the external service. It only severs the connection. Troubleshoot Common Integration Issues Integration Shows "Expired" But Re-connect Does Not Work Solutions: - Wait a few minutes and refresh the page - Try disconnecting completely, then reconnecting fresh - Check that the external service still has your account in good standing - If the external service has an API dashboard, verify that TexAu's app is still authorized there Data Is Not Syncing from Integration Solutions: - Verify the integration is "Connected" (not Expired or Error status) - Check that the integration has read permissions - Confirm there is actually data in the external service to sync - Try clicking "Sync Now" manually to see if that works - Check the sync history for error messages Cannot See All Your Data in the Integration Solutions: - Check if you applied any filters when syncing (you might have filtered some data out) - Verify permissions. The integration might not have access to all data types. - Check if there is a data limit (some integrations limit how much data syncs) - Review the integration's documentation for limitations Synced Data Is Not Updating in Real Time Solutions: - Not all integrations support real-time syncing. Some require manual refresh. - Try clicking "Sync Now" to force a manual sync - Check if automatic syncing is enabled (some require explicit enablement) - Wait a few minutes. Automatic syncs might be on a schedule (for example, every 15 minutes). Getting Errors When Syncing Solutions: - Check that nothing changed in the external service (deleted accounts, schema changes, etc.) - Try syncing a smaller subset of data to narrow down the issue - Check the integration's status page (some services post outage notices) - Disconnect and reconnect the integration to refresh the connection - Contact support with the specific error message

Last updated on Apr 06, 2026

Ocean.io Integration Guide

Ocean.io Integration Guide This guide covers the Ocean.io integration available in TexAu. Use it to find companies that look like your best customers. Before you begin - You need an active Ocean.io account with API access. - Retrieve your API key from your Ocean.io dashboard under API Settings. - In TexAu, go to Settings > Integrations, find Ocean.io, and paste your API key. Actions Search Companies (Ocean) Finds companies similar to a given company domain. Returns enriched company profiles based on lookalike matching. Credit cost: 10 credits per row Input: - Domain (required) -- the company domain you want to find lookalikes for, e.g. salesforce.com Output: - Company Name - Company Domain - Company Description - Company Size Range - Employee Count (LinkedIn) - Employee Count (Ocean) - Primary Country Code - Match Relevance Typical use case: Build a prospect list from a single example company. Paste in a domain for a company that matches your ideal customer profile, and get back a list of similar companies. How Ocean.io lookalike matching works Ocean.io analyzes firmographic and technographic signals to find companies with similar profiles. The Match Relevance field in the output tells you how closely each result matches the seed domain. Higher relevance means stronger similarity. The action returns multiple companies per row (because one lookalike search produces many results). Each result row in your table represents one matched company. Common workflow pattern Build a lookalike prospect list 1. Create a table with a column of seed company domains -- one per row. 2. Add an Action Column and select Search Companies (Ocean). 3. Map the domain column to the Domain input. 4. Run the column. 5. Filter results by Match Relevance or Employee Count to narrow the list. 6. Add additional Action Columns to enrich the returned domains with contacts: use Enrich Company (Apollo) or Enrich IP Address (Versium) for further firmographic data. Tip: Start with 5-10 known customers as seed domains. The resulting prospect list mirrors your best customers by company profile. Troubleshooting Results include companies that do not match the expected size or industry. Ocean.io looks for structural and behavioral similarity, not just industry. A fintech SaaS company might match a healthcare SaaS company because of shared characteristics like company size, growth rate, and technology stack. Adjust your filtering on the output columns to narrow by Country or Employee Count after the run. Domain input returns no results. Check that the domain is a real, indexed company domain. Very small companies, newly registered domains, or personal domains may not be in Ocean.io's database. Try a larger competitor's domain as the seed instead. Multiple rows are returned for one seed domain. This is expected behavior. The action returns multiple lookalike companies per search. Each match becomes a separate row in your table. Filter or sort by Match Relevance to keep only the closest matches.

Last updated on Apr 06, 2026

People Data Labs Integration Guide

People Data Labs Integration Guide This guide covers the People Data Labs integration available in TexAu. Use it to enrich contact records with professional profile data including emails, phone numbers, experience history, and social profiles. Before you begin - You need an active People Data Labs account. API access is required. Sign up at peopledatalabs.com. - Retrieve your API key from the People Data Labs developer console. - In TexAu, go to Settings > Integrations, find People Data Labs, and paste your API key. Actions Enrich Person by LinkedIn URL (People Data Labs) Returns a comprehensive professional profile for a contact using their LinkedIn URL. Credit cost: 30 credits per row (charged only on successful matches) Input: - LinkedIn URL (required): full LinkedIn profile URL Output: - Person ID - Full Name - Current Job Title - Current Company - LinkedIn URL - Work Email - All Emails (array) - Phone Numbers (array) - Location - Skills (array) - Experience History (array) - Education History (array) - Social Profiles (array) - Match Score: likelihood that this is the correct person Typical use case: Deep enrichment for priority prospects where you need the most complete profile possible, including verified work email, phone numbers, and full contact history. Enrich Person by Name and Company (People Data Labs) Returns the same set of profile data using a person's full name and company name instead of a LinkedIn URL. Credit cost: 30 credits per row (charged only on successful matches) Input: - Full Name (required) - Company Name (required) Output: Same as above: Person ID, Full Name, Current Job Title, Work Email, Phone Numbers, Location, Match Score, and full history arrays. Typical use case: When you have contact names and companies but no LinkedIn URLs. Use this as an alternative enrichment path. When to use People Data Labs vs other enrichers People Data Labs is best for: - High-priority accounts where data completeness matters - Contacts where other providers have failed - Research workflows where you need full employment history At 30 credits per row, People Data Labs is more expensive than most email finders. Use it selectively: either as a primary enricher for your top accounts, or as a last step in a Waterfall for contacts other providers could not find. The Match Score output tells you how confident the system is in the result. A score below 5 means the match is uncertain. Filter out low-confidence rows before using the data. Common workflow pattern Enrich high-value accounts with full profile data 1. Create a table with LinkedIn URLs for your target contacts. 2. Add an Action Column for Enrich Person by LinkedIn URL (People Data Labs). 3. Map the LinkedIn URL column to the LinkedIn URL input. 4. Select outputs you need: Work Email, Phone Numbers, Current Job Title, Match Score. 5. Add a filter step or formula column: IF(match_score < 5, "low confidence", "use data"). 6. Use the Work Email output to populate downstream outreach columns. Troubleshooting Match Score is low even though the LinkedIn URL looks correct. A low Match Score means People Data Labs had difficulty confirming the identity. This can happen with LinkedIn URLs that have been recently changed, profiles with limited public data, or unusual name formats. Verify the URL is current and publicly accessible. Work Email is empty but other fields are populated. Work Email is sourced from verified sightings in People Data Labs' data. Not every profile has a confirmed work email. Use the All Emails array: it may contain alternative email addresses that were observed. 30 credits per row depletes my balance quickly. People Data Labs is charged at 30 credits per successful match. Run a test batch of 10-20 rows to check your hit rate before running a large list. For lower-budget enrichment, consider BetterEnrich, FullEnrich, or Apollo as alternatives. No results returned for a contact. People Data Labs may not have indexed the profile. This is more common for people with very limited LinkedIn activity or non-English language profiles. Try Enrich Person by Name and Company (People Data Labs) as an alternative if you have the company name.

Last updated on Apr 06, 2026

Pipedrive Integration Guide

Pipedrive Integration Guide This guide covers all Pipedrive actions available in TexAu. Use these actions to read, create, update, and delete records in your Pipedrive CRM. All Pipedrive actions in TexAu cost 0 credits. You only pay for the credits on your Pipedrive side. Before you begin - A Pipedrive account is required. Sign up at pipedrive.com. - Your Pipedrive API key is at Personal preferences > API inside Pipedrive. - In TexAu, go to Settings > Integrations, find Pipedrive, enter your API key, and click Save. Person (contact) actions Get All Persons Returns a list of all persons in your Pipedrive account. Input: - Limit (optional) Output: - Array of persons with ID, name, email, phone, organization Create Person Creates a new person record in Pipedrive. Input: - Name (required) - Email (optional) - Phone (optional) - Organization ID (optional) Output: - Person ID - Person URL Get Person Returns details for a single person by ID. Input: - Person ID (required) Output: - All person fields including name, email, phone, organization, and custom fields Update Person Updates an existing person record. Input: - Person ID (required) - Fields to update Output: - Update status Delete Person Deletes a person record from Pipedrive. Input: - Person ID (required) Output: - Deletion status Search All Persons Searches person records by name, email, or phone. Input: - Search term (required) Output: - Array of matching persons with ID, name, and email Merge Persons Merges two person records into one. Input: - Primary Person ID (the record to keep) - Merge Person ID (the record to merge in) Output: - Merge status Get Person Fields Returns all custom and standard field definitions for person records. Input: None Output: - Array of field keys, names, and types Get Persons by Organization Returns all persons associated with a specific organization. Input: - Organization ID (required) Output: - Array of persons Get Activities by Person Returns all activities linked to a specific person. Input: - Person ID (required) Output: - Array of activities (type, due date, subject, status) Organization (company) actions Get All Organizations Returns a list of all organizations in Pipedrive. Input: - Limit (optional) Output: - Array of organizations with ID, name, address Create Organizations Creates a new organization record. Input: - Name (required) - Address (optional) - Custom fields (optional) Output: - Organization ID - Organization URL Get Organization Returns details for a single organization. Input: - Organization ID (required) Output: - All organization fields Update Organization Updates an existing organization record. Input: - Organization ID (required) - Fields to update Output: - Update status Delete Organization Deletes an organization from Pipedrive. Input: - Organization ID (required) Output: - Deletion status Search Organizations Searches organizations by name or custom field. Input: - Search term (required) Output: - Array of matching organizations Merge Organizations Merges two organization records. Input: - Primary Organization ID - Merge Organization ID Output: - Merge status Deal actions Get All Deals Returns a list of deals from Pipedrive. Input: - Limit (optional) - Pipeline ID (optional) - Status (optional -- open, won, lost) Output: - Array of deals with ID, title, value, stage, owner Create Deal Creates a new deal in Pipedrive. Input: - Title (required) - Pipeline ID (optional) - Stage ID (optional) - Value and currency (optional) - Person ID or Organization ID (optional) Output: - Deal ID - Deal URL Get Deal Details Returns full details for a single deal. Input: - Deal ID (required) Output: - All deal fields including value, stage, contacts, and custom fields Update Deal Updates properties on an existing deal. Input: - Deal ID (required) - Fields to update Output: - Update status Delete Deal Deletes a deal from Pipedrive. Input: - Deal ID (required) Output: - Deletion status Search Deals Searches deals by title or custom field. Input: - Search term (required) Output: - Array of matching deals Merge Deals Merges two deal records. Input: - Primary Deal ID - Secondary Deal ID Output: - Merge status Get Deals by Person Returns all deals associated with a specific person. Input: - Person ID (required) Output: - Array of deals Get Deals by Pipeline Returns all deals in a specific pipeline. Input: - Pipeline ID (required) Output: - Array of deals Get Activities by Deal Returns all activities linked to a specific deal. Input: - Deal ID (required) Output: - Array of activities List Deal Products Returns the products linked to a specific deal. Input: - Deal ID (required) Output: - Array of products (name, price, quantity) Add Product to Deal Adds a product to a deal. Input: - Deal ID (required) - Product ID (required) - Quantity (optional) - Item price (optional) Output: - Addition status Lead actions Add Lead Creates a new lead in Pipedrive. Input: - Title (required) - Person ID or Organization ID (optional) - Value (optional) Output: - Lead ID Get All Leads Returns a list of all leads. Input: - Limit (optional) Output: - Array of leads with ID, title, status Get Lead Details Returns full details for a specific lead. Input: - Lead ID (required) Output: - All lead fields Update Lead Updates an existing lead record. Input: - Lead ID (required) - Fields to update Output: - Update status Pipeline and stage actions Get All Pipelines Returns all pipelines in your Pipedrive account. Input: None Output: - Array of pipeline IDs and names Get Pipeline Details Returns details for a single pipeline including its stages. Input: - Pipeline ID (required) Output: - Pipeline name and array of stages Get All Stages Returns all stages across all pipelines. Input: None Output: - Array of stage IDs, names, and associated pipeline IDs Activity actions Add Activity Creates a new activity in Pipedrive. Input: - Subject (required) - Type (required -- call, meeting, email, task) - Due date (optional) - Deal ID or Person ID to link (optional) Output: - Activity ID Get All Activities Returns a list of all activities. Input: - Limit (optional) Output: - Array of activities Other actions List Users Returns all users in the Pipedrive account. Input: None Output: - Array of user IDs, names, and emails Add Note Adds a note to a deal, person, or organization. Input: - Content (required) - Deal ID, Person ID, or Organization ID (at least one required) Output: - Note ID Get All Notes Returns all notes from Pipedrive. Input: - Limit (optional) Output: - Array of notes Create Webhook Creates a Pipedrive webhook to receive real-time notifications in another system. Input: - Subscription URL (required) - Event action (required -- added, updated, deleted) - Event object (required -- deal, person, organization, etc.) Output: - Webhook ID and subscription status Get Recent Changes Returns a list of all recent changes across all object types in Pipedrive. Input: - Since timestamp (optional) Output: - Array of change events Troubleshooting Create Person fails with "duplicate record". Pipedrive detects duplicates by email. Use Search All Persons first, then branch your workflow: update if found, create if not. Stage ID is not known. Run Get All Stages to retrieve all stage IDs for your pipelines. Copy the ID for the stage you want to use. API returns "Permission denied" for some actions. Your Pipedrive API key is tied to your user account permissions. If you cannot access certain pipelines or deals, the key's user may not have visibility into those records. The Get All Deals action returns more records than expected. Apply a pipeline or status filter in the action input to narrow results. Running on all deals without filtering may return thousands of records.

Last updated on Apr 06, 2026

Prospeo Integration Guide

Prospeo Integration Guide This guide covers all Prospeo actions available in TexAu. Prospeo provides email and mobile number finding from LinkedIn URLs and name/website combinations. Before you begin - A Prospeo account is required. Sign up at prospeo.io. - Your Prospeo API key is on your Prospeo dashboard under API. - In TexAu, go to Settings > Integrations, find Prospeo, enter your API key, and click Save. Email finding actions Find Email by LinkedIn URL (Prospeo) Finds a work email address using a LinkedIn profile URL. Credit cost: 2 credits per successful lookup Input: - LinkedIn Profile URL (required) -- full URL starting with https://linkedin.com/in/ Output: - Email Address - Verification status (valid, catch-all, invalid) - Email source Find Email Using Full Name and Company Website (Prospeo) Finds a work email using a person's full name and company website. Credit cost: 2 credits per successful lookup Input: - Full Name (required) -- first and last name combined - Company Website (required) -- e.g., https://company.com or company.com Output: - Email Address - Verification status Typical use case: Use when you have merged name fields and company websites instead of separate first/last name columns. Phone finding actions Find Mobile Number by LinkedIn URL (Prospeo) Finds a mobile phone number using a LinkedIn profile URL. Credit cost: 20 credits per successful lookup Input: - LinkedIn Profile URL (required) Output: - Phone Number - Country code - Local format Find Mobile Number Using Full Name and Company Website (Prospeo) Finds a mobile phone number using a full name and company website. Credit cost: 15 credits per successful lookup Input: - Full Name (required) - Company Website (required) Output: - Phone Number - Country Using Prospeo in a waterfall Prospeo works well as a secondary provider for both email and phone finding. Example email waterfall: 1. Find Work Email by LinkedIn URL (BetterEnrich) -- primary 2. Find Email by LinkedIn URL (Prospeo) -- fallback 1 3. Find Work Email Using LinkedIn Profile URL (FullEnrich) -- fallback 2 Example phone waterfall: 1. Find Mobile Number by LinkedIn URL (BetterEnrich) -- primary 2. Find Mobile Number by LinkedIn URL (Prospeo) -- fallback 1 3. Find Mobile Number Using LinkedIn Profile URL (FullEnrich) -- fallback 2 Tips - Prospeo's Find Email Using Full Name and Company Website accepts a combined full name, which is useful when your table has a single Name column. Use it directly without splitting into first/last name first. - The company website input can include or omit the https:// prefix. Prospeo handles both. Troubleshooting Email finding returns empty for rows with valid LinkedIn URLs. Prospeo may not have data for some profiles. This is expected. The profile may be private, deleted, or outside Prospeo's database. Use a waterfall sequence with other providers to maximize coverage. Find Email Using Full Name and Company Website fails for unusual names. Names with special characters or non-standard formatting may not match Prospeo's records. Try cleaning the name in a Formula Column (TRIM and proper capitalization) before passing it to the action. Rate limit errors during large runs. TexAu handles retries automatically. If large batches consistently hit rate limits, reduce the batch size or contact Prospeo about your API limits.

Last updated on Apr 06, 2026

Reply.io Integration Guide

Reply.io Integration Guide This guide covers all Reply.io actions available in TexAu. Use these actions to manage contacts and campaigns in Reply.io. All Reply.io actions in TexAu cost 0 credits. You only pay for the credits on your Reply.io side. Before you begin - A Reply.io account is required. Sign up at reply.io. - Your Reply.io API key is at Settings > API inside Reply.io. - In TexAu, go to Settings > Integrations, find Reply.io, enter your API key, and click Save. Contact actions Create Contact (Reply.io) Creates a new contact in Reply.io. Input: - Email (required) - First Name (optional) - Last Name (optional) - Company (optional) - Job Title (optional) - Phone (optional) - Custom fields (optional) Output: - Contact ID - Creation status Typical use case: After enriching a prospect list in TexAu, push contacts directly to Reply.io. Create Contact and Push to Campaign (Reply.io) Creates a new contact in Reply.io and immediately enrolls them in a campaign. Input: - Email (required) - First Name (optional) - Last Name (optional) - Campaign ID (required) - Other contact properties (optional) Output: - Contact ID - Enrollment status Typical use case: Skip the two-step create-then-enroll process when you already know which campaign the contact should enter. Get All Contacts Returns a list of contacts from your Reply.io account. Input: - Limit (optional) - Page (optional, for pagination) Output: - Array of contacts with ID, email, name, and campaign enrollment status Get Contact by ID Returns details for a single contact. Input: - Contact ID (required) Output: - All contact fields Get Contact by Email Returns details for a contact matched by email address. Input: - Email (required) Output: - Contact ID - All contact fields Update Contact Updates fields on an existing Reply.io contact. Input: - Contact ID (required) - Fields to update Output: - Update status Delete Contact by Email Deletes a contact from Reply.io identified by email address. Input: - Email (required) Output: - Deletion status Delete Contact By ID Deletes a contact from Reply.io by Contact ID. Input: - Contact ID (required) Output: - Deletion status Push Existing Contact to Campaign Enrolls an existing Reply.io contact into a campaign. Input: - Contact ID or Email (required) - Campaign ID (required) Output: - Enrollment status Get Contacts by List Name Returns contacts that belong to a specific Reply.io list. Input: - List Name (required) Output: - Array of contacts in the list Campaign actions Get All Campaigns Returns a list of all campaigns in your Reply.io account. Input: None Output: - Array of campaigns with ID, name, and status Get Campaign Details Returns full details for a specific campaign. Input: - Campaign ID (required) Output: - Campaign name - Status - Step count - Contact count - Metrics (sent, opened, replied, bounced) Common workflow patterns Enrich then push to Reply.io 1. Start with a list of LinkedIn URLs in a TexAu table. 2. Add an Action Column for Find Work Email by LinkedIn URL (BetterEnrich). 3. Add a second Action Column for Find Mobile Number by LinkedIn URL (BetterEnrich). 4. Add a third Action Column for Create Contact and Push to Campaign (Reply.io). 5. Map First Name, Last Name, Email, and Campaign ID. 6. Run enrichment. Contacts with verified emails get created in Reply.io and enrolled immediately. Check for existing contacts before creating 1. Add an Action Column for Get Contact by Email (Reply.io) using the email output from BetterEnrich. 2. Add a Formula Column: IF({{Contact ID}} != "", "exists", "new") 3. Use this status in a conditional column to decide whether to create or update. Troubleshooting Create Contact fails with "contact already exists". Reply.io uses email as the unique key. Use Get Contact by Email first to check. If the contact already exists, use Update Contact instead. Push to Campaign returns "campaign not found". Use Get All Campaigns to find the correct Campaign ID. Campaign IDs are numeric, not the campaign name. Contacts are created but do not appear in campaigns. Check that the campaign is active and accepting new contacts. Paused campaigns do not enroll new contacts even if the API call succeeds. The API key saves but actions return 401 errors. Your Reply.io API key may be tied to a specific workspace. Verify the key is for the Reply.io account and workspace where your campaigns are active.

Last updated on Apr 06, 2026

SerpApi Integration Guide

SerpApi Integration Guide This guide covers the SerpApi integration available in TexAu. Use it to run Google searches programmatically and extract data from the top organic result. Before you begin - You need an active SerpApi account. Sign up at serpapi.com. Free tier is available. - Retrieve your API key from the SerpApi dashboard. - In TexAu, go to Settings > Integrations, find SerpApi, and paste your API key. Actions Search Google Top Result (SerpApi) Runs a Google search for a given query and returns detailed information for the first organic result. Credit cost: 2 credits per row Input: - Search Query (required): the text to search on Google Output: - Title: page title of the top result - Link: URL of the top result - Description: source description from Google's knowledge about the result - Region: geographical region associated with the result Typical use case: Look up a person's LinkedIn URL from their name and company, find a company's website from its name, or verify that a URL is the correct web presence for an organization. Common use cases Find a LinkedIn URL from name and company Build a search query using a formula column, then run the search to get the LinkedIn URL in the result: 1. Add a formula column: CONCAT(first_name, " ", last_name, " ", company_name, " site:linkedin.com/in") 2. Use that formula column as input for Search Google Top Result (SerpApi). 3. Map the formula output to the Search Query input. 4. The Link output will contain the LinkedIn profile URL if the person has a public profile. Find a company domain from company name 1. Add a formula column: CONCAT(company_name, " official website") 2. Use that column as input for Search Google Top Result (SerpApi). 3. The Link output returns the company website. 4. Use a formula to extract the domain: EXTRACT_DOMAIN(link_output) or strip the path manually. Verify that a URL belongs to the right company 1. Feed the company name as the search query. 2. Compare the Link output to your expected domain. 3. Use an IF formula column to flag mismatches. Building effective search queries The quality of your output depends on your query. Keep these patterns in mind: - For LinkedIn URL lookup: [Full Name] [Company] site:linkedin.com/in - For company domain: [Company Name] official website - For generic research: [Company Name] [Topic] filetype:pdf or "[Company Name]" "annual report" Use formula columns to build your queries dynamically from other columns in your table. The CONCAT function works well for this. Troubleshooting Link output returns a news article or directory listing, not the target result. Your search query may be too broad. Add more specifics to the query formula. For LinkedIn lookups, use site:linkedin.com/in to constrain results to LinkedIn profiles only. Search returns the right page but the Link field has a redirect URL. Some Google results include redirect wrappers. Add this to your output processing: run the Link output through the Resolve URL Redirect utility action to get the final destination URL. Results are consistent across many rows but clearly wrong. Google sometimes returns the same top result for variations of a query. Add a second column with the description or title and check visually whether the result matches your intent before building any automation on top of the Link output. API key is valid but queries are failing. SerpApi has a monthly search credit limit on free plans. Check your SerpApi dashboard to confirm your quota has not been exhausted.

Last updated on Apr 06, 2026

Slack Integration

Slack Integration Extract member data from public Slack channels for lead generation and community analysis. Before you begin - You need an active TexAu account with available credits. - You need access to the Slack workspace you want to extract data from. - You need your Slack authentication cookie (starts with xoxd-) and API token (starts with xoxc-). You can find these in your browser's developer tools while logged into Slack. - You need the Slack channel ID. Right-click a channel name in Slack and select Copy link to find the channel ID in the URL. Get Slack Channel Members Retrieves the member list and their profile details from a public Slack channel using workspace credentials. Credit cost: 2 credits per execution Input parameters | Parameter | Display name | Required | Description | |-----------|-------------|----------|-------------| | workspace | Workspace | Yes | The Slack workspace slug (e.g., 'texauhq'). | | channel_id | Channel ID | Yes | The Slack Channel ID. | | cookie | Slack Auth Cookie | Yes | Your Slack authentication cookie (starts with 'xoxd-'). | | token | Slack API Token | Yes | Your Slack API token (starts with 'xoxc-'). | Output fields | Field | Display name | Type | |-------|-------------|------| | workspace | Workspace | text | | channel_id | Channel ID | text | | total_members | Total Members Extracted | number | | user_ids | User IDs | text | | real_names | Real Names | text | | display_names | Display Names | text | | emails | Emails | text | | titles | Titles | text | | phones | Phone Numbers | text | | status_texts | Status Texts | text | | timezones | Timezones | text | | is_admins | Is Admin Status | text | | is_owners | Is Owner Status | text | | avatar_urls | Avatar URLs | url | This action returns multiple results per execution. Up to 50 members are extracted per run. How to find your Slack credentials 1. Open Slack in your web browser (not the desktop app). 2. Open the browser developer tools (press F12 or right-click and select Inspect). 3. Go to the Application tab (Chrome) or Storage tab (Firefox). 4. Under Cookies, find the cookie named d. Its value is your Slack Auth Cookie (starts with xoxd-). 5. For the API token, go to the Console tab and look for network requests to Slack's API. The token starts with xoxc-. How to find a Slack channel ID 1. In Slack, right-click the channel name in the sidebar. 2. Select Copy link. 3. The channel ID is the last segment of the URL (e.g., C01ABC2DEFG). Troubleshooting Authentication error Your Slack cookie or token may have expired. Log into Slack in your browser again and re-extract the credentials. No members returned Make sure the channel ID is correct and that you have access to the channel. Private channels require you to be a member. Only partial member list The action extracts up to 50 members per execution. For larger channels, run the action multiple times or use it as part of a workflow. Workspace slug not recognized The workspace slug is the subdomain you see when using Slack in a browser (e.g., for texauhq.slack.com, the slug is texauhq).

Last updated on Jun 03, 2026

Smartlead Integration Guide

Smartlead Integration Guide This guide covers all Smartlead actions available in TexAu. Use these actions to manage campaigns, leads, and sending accounts in Smartlead. All Smartlead actions in TexAu cost 0 credits. You only pay for the credits on your Smartlead side. Before you begin - A Smartlead account is required. Sign up at smartlead.ai. - Your Smartlead API key is at Settings > API inside Smartlead. - In TexAu, go to Settings > Integrations, find Smartlead, enter your API key, and click Save. Lead actions Add Leads to Campaign Adds one or more leads to a specific Smartlead campaign. Input: - Campaign ID (required) - Email (required) - First Name (optional) - Last Name (optional) - Company Name (optional) - Custom fields (optional -- for email personalization) Output: - Lead ID - Addition status Typical use case: After running email enrichment and verification in TexAu, push confirmed deliverable contacts to Smartlead to start outreach. Update Campaign Lead Updates a lead's properties inside a specific campaign. Input: - Campaign ID (required) - Email (required -- identifies the lead) - Fields to update Output: - Update status List Leads by Campaign ID Returns all leads in a specific campaign. Input: - Campaign ID (required) - Limit (optional) - Offset (optional) Output: - Array of leads with email, name, reply status, and sequence stage Campaign actions List Campaigns Returns all campaigns in your Smartlead account. Input: None Output: - Array of campaigns with ID, name, and status (active, paused, completed) Email account actions Create Email Account Adds a new sending email account to Smartlead. Input: - Email address (required) - SMTP host (required) - SMTP port (required) - SMTP username (required) - SMTP password (required) - IMAP host (optional) - IMAP port (optional) - Daily sending limit (optional) Output: - Account ID - Creation status Typical use case: Provision new sending accounts programmatically when scaling outreach. Common workflow pattern Enrich and add leads to Smartlead 1. Add your raw LinkedIn profile URLs or company domains to a TexAu table. 2. Run email enrichment using BetterEnrich or FullEnrich. 3. Run email verification using Verify Email (BetterEnrich). 4. Add a Formula Column to filter: IF({{Deliverable}} == "true", {{Email}}, ""). 5. Add an Action Column for Add Leads to Campaign (Smartlead). 6. Map Email, First Name, Last Name, and any custom personalization variables. 7. Paste the Campaign ID from Smartlead into the fixed-value input for Campaign ID. 8. Run enrichment. Troubleshooting Add Leads to Campaign returns "campaign not found". Run List Campaigns to confirm the Campaign ID. Campaign IDs are numeric. Do not use the campaign name as the ID. Leads are added but the campaign is not sending. Confirm that the campaign status is active in Smartlead and that your sending email accounts are connected and warmed up. Leads added to paused campaigns do not receive emails until the campaign is resumed. Custom fields are not appearing in emails. Custom fields must match the variable names used in your Smartlead email template exactly (including capitalization). Check the variable names in your Smartlead template and use the same names in the TexAu column mapping. List Leads by Campaign ID returns 0 leads despite having leads in Smartlead. Confirm you are using the correct Campaign ID. Use List Campaigns to get all campaign IDs and verify.

Last updated on Apr 06, 2026

Snov.io Integration Guide

Snov.io Integration Guide This guide covers the Snov.io integration available in TexAu. Use it to enrich contact records with profile, company, and social data starting from an email address. Before you begin - You need an active Snov.io account with API access. API access is available on paid plans. - Retrieve your API key from your Snov.io account under Settings > API. - In TexAu, go to Settings > Integrations, find Snov.io, and paste your API key. Actions Enrich Contact (Snov.io) Retrieves contact and company information for a person using their email address. Credit cost: 4 credits per row Input: - Email (required): the contact's email address Output: - Profile ID - Source - Full Name - First Name - Last Name - Profile Photo - Industry - Country - Locality - LinkedIn URL - Twitter URL - Current Company - Current Position - Current Company Website - Current Company City - Current Company State - Current Company Country - Current Company Industry - Current Company Size - Current Company Type - Current Job Start Date - Last Update Date Typical use case: Start with a list of email addresses and expand each contact to include their job title, company, location, and social profiles without needing a LinkedIn URL. Why use Enrich Contact vs other enrichment actions Most email finders in TexAu work from LinkedIn URL to email. Enrich Contact (Snov.io) reverses this. It starts from an email and returns profile data. This is useful when: - You have a list of email addresses from a form submission or event export. - You want to append job title and company data to existing contacts. - A LinkedIn URL is not available. Common workflow pattern Enrich an email list from a form upload 1. Import your CSV with email addresses. 2. Add an Action Column and select Enrich Contact (Snov.io). 3. Map the email column to the Email input. 4. Select the output fields you want: Full Name, Current Position, Current Company, LinkedIn URL. 5. Run enrichment. From the enriched data, you can then add a BetterEnrich action to find a mobile number using the LinkedIn URL that Snov.io returns. Troubleshooting Current Position and Current Company are empty even though the contact exists. Snov.io returns data based on their own index of email addresses. If the contact's email is not in their database, the profile will be blank. Try using a LinkedIn URL-based enricher as a fallback. Profile ID is returned but most other fields are empty. This can happen when Snov.io has indexed the email address but does not have a full profile linked to it. The record exists, but the data is sparse. Use another enrichment source for further data. Credit cost is higher than expected. Snov.io charges 4 credits per row regardless of whether data is found. If your list has many contacts not in the Snov.io database, your hit rate will affect cost efficiency. Run a test batch of 20-50 rows first to assess coverage before running the full list.

Last updated on Apr 06, 2026

Versium Integration Guide

Versium Integration Guide This guide covers the Versium integration available in TexAu. Use it to enrich IP addresses with company and firmographic data. Before you begin - You need an active Versium REACH account with API access. - Retrieve your API key from the Versium developer portal. - In TexAu, go to Settings > Integrations, find Versium, and paste your API key. Actions Enrich IP Address (Versium) Looks up a company associated with an IP address and returns firmographic data including company name, domain, industry, employee range, and revenue range. Credit cost: 4 credits per successful lookup Input: - IP Address (required) -- IPv4 address, e.g. 203.0.113.42 Output: - IP Usage Type - Is ISP -- true/false - Company Name - Company Address - Company City - Company State - Company ZIP - Company Country - Phone - Domain - Website - Industry - Employee Range - Sales Revenue Range - Year Founded - SIC - NAICS - NAICS Description Typical use case: De-anonymize website visitors. If you have server logs or a reverse IP feed with visitor IP addresses, this action maps each IP to a company, giving you firmographic data for anonymous traffic. How IP enrichment works Versium maps IP address ranges to organizations and companies. When a company's network traffic originates from a registered IP block, Versium can identify the company behind that IP. Important limitations: - Consumer ISPs and home internet connections return Is ISP = true. These are not useful for B2B prospecting. - Mobile IP addresses and VPN exits often cannot be attributed to a specific company. - Corporate IP ranges are the most reliably enriched addresses. Filter your results on Is ISP = false to keep only corporate-attributed records. Common workflow pattern Enrich website visitor IPs for ABM prospecting 1. Export visitor IP addresses from your web analytics or server logs. 2. Import them into a TexAu table. 3. Add an Action Column and select Enrich IP Address (Versium). 4. Map the IP column to the IP Address input. 5. Select outputs: Company Name, Domain, Industry, Employee Range, Sales Revenue Range. 6. Add a formula column to filter out ISPs: IF(is_isp = "true", "skip", "prospect"). 7. Use the Company Name and Domain columns to feed into further enrichment actions. Troubleshooting Most rows return Is ISP = true. Your IP list likely contains home internet addresses. This is common if your website visitors are a mix of businesses and individuals. Versium is built for corporate IP ranges. Filter these out and focus on rows where Is ISP = false. Company fields are empty but Is ISP is false. Some corporate IP ranges are not in Versium's database. This can happen for smaller companies, recently moved offices, or companies that use cloud-hosted hosting rather than their own IP blocks. Coverage varies by geography and company size. IP addresses from the same company return different company names. Large companies with multiple offices or business units may have IP ranges registered under different legal entity names. Normalize company names after enrichment using the Normalize Company Name utility action in TexAu.

Last updated on Apr 06, 2026

YouTube Integration

YouTube Integration Extract video metadata, channel details, and search results from YouTube directly inside TexAu. No separate YouTube API key is required. Before you begin - You need an active TexAu account with available credits. - No external YouTube API key is needed. TexAu handles YouTube data retrieval for you. YouTube Video Search Search YouTube for videos matching a keyword query and extract their metadata. Credit cost: 1 credit per execution Input parameters | Parameter | Display name | Required | Description | |-----------|-------------|----------|-------------| | query | Search Query | Yes | The search keyword or query to look up on YouTube. | Output fields | Field | Display name | Type | |-------|-------------|------| | video_ids | Video IDs | text | | titles | Video Titles | text | | channels | Channel Names | text | | channel_ids | Channel IDs | text | | view_counts | View Counts | text | | durations | Durations in Seconds | text | | publish_dates | Publish Dates | text | | thumbnails | Thumbnail URLs | url | | descriptions | Video Descriptions | text | This action returns multiple results per execution. Get YouTube Video Details Fetch full metadata for a YouTube video, including tags, statistics, and optionally its captions/transcript. Credit cost: 1 credit per execution Input parameters | Parameter | Display name | Required | Description | |-----------|-------------|----------|-------------| | url | YouTube Video URL | Yes | The YouTube video URL (e.g., https://www.youtube.com/watch?v=...). | Output fields | Field | Display name | Type | |-------|-------------|------| | video_id | Video ID | text | | title | Video Title | text | | description | Video Description | text | | channel | Channel Name | text | | channel_id | Channel ID | text | | view_count | View Count | number | | like_count | Like Count | number | | duration | Duration (Seconds) | number | | upload_date | Upload Date (YYYYMMDD) | text | | tags | Video Tags | array | | categories | Categories | array | | thumbnail_urls | Thumbnail URLs | array | | captions | Video Captions / Transcript | text | | chapters | Video Chapters | array | Get YouTube Channel Details Fetch metadata, statistics, and social links for a specific YouTube channel. Credit cost: 1 credit per execution Input parameters | Parameter | Display name | Required | Description | |-----------|-------------|----------|-------------| | url | Channel URL | Yes | The YouTube channel URL (e.g., https://www.youtube.com/@ChannelName). | Output fields | Field | Display name | Type | |-------|-------------|------| | channel_id | Channel ID | text | | name | Channel Name | text | | description | Channel Description | text | | subscriber_count | Subscriber Count | text | | video_count | Video Count | number | | view_count | Total View Count | number | | joined_date | Joined Date | text | | country | Country | text | | avatar_url | Avatar URL | url | | banner_url | Banner URL | url | | links | Channel Links | text | Get YouTube Channel Videos Fetch the video listing for a specific YouTube channel. Credit cost: 1 credit per execution Input parameters | Parameter | Display name | Required | Description | |-----------|-------------|----------|-------------| | url | Channel URL | Yes | The YouTube channel URL (e.g., https://www.youtube.com/@ChannelName). | Output fields | Field | Display name | Type | |-------|-------------|------| | channel_name | Channel Name | text | | total_count | Total Videos Extracted | number | | video_ids | Video IDs | text | | video_titles | Video Titles | text | | video_views | Video View Counts | text | | video_durations | Video Durations in Seconds | text | | video_publish_dates | Video Publish Dates | text | | video_thumbnails | Video Thumbnails | url | This action returns multiple results per execution. Troubleshooting No results returned for a search query Check that the search term is not too narrow. Try broader keywords. YouTube may also return no results for very niche or misspelled queries. Video details return empty captions Not all YouTube videos have captions. If the uploader has not added captions or auto-captions are disabled, the captions field will be empty. Channel URL not recognized Make sure you use the full channel URL in the format https://www.youtube.com/@ChannelName. Shortened or custom URLs may not resolve correctly. Action returns an error Verify that the YouTube video or channel is publicly accessible. Private or age-restricted content cannot be scraped. Credit usage Each of the four YouTube actions costs 1 credit per execution, regardless of how many results are returned.

Last updated on Jun 03, 2026

Zoho CRM Integration Guide

Zoho CRM Integration Guide This guide covers all Zoho CRM actions available in TexAu. Use these actions to manage leads, contacts, accounts, and deals in Zoho CRM. All Zoho CRM actions in TexAu cost 0 credits. You only pay for the credits on your Zoho side. Before you begin - A Zoho CRM account is required. Free and paid plans are both supported. - Connect Zoho CRM to TexAu using OAuth. Go to Settings > Integrations, find Zoho CRM, and click Connect with OAuth. - Sign in to your Zoho account in the window that opens and authorize TexAu. - The integration connects using the permissions of the authorizing user. Lead actions Search Leads Searches Zoho CRM leads by name, email, or other criteria. Input: - Search criteria (field name and value) Output: - Array of matching leads with ID, name, email, phone List Leads Returns a list of leads from Zoho CRM. Input: - Limit (optional) - Sort field (optional) Output: - Array of leads Get Lead by ID Returns full details for a single lead. Input: - Lead ID (required) Output: - All lead fields Create Lead Creates a new lead record in Zoho CRM. Input: - First Name, Last Name (required) - Email (optional) - Phone (optional) - Company (optional) - Job Title (optional) - Lead Source (optional) Output: - Lead ID - Creation status Update Lead Updates fields on an existing lead. Input: - Lead ID (required) - Fields to update Output: - Update status Delete Lead Deletes a lead from Zoho CRM. Input: - Lead ID (required) Output: - Deletion status Contact actions Search Contacts Searches contacts by name, email, or field value. Input: - Search criteria Output: - Array of matching contacts List Contacts Returns a list of contacts from Zoho CRM. Input: - Limit (optional) Output: - Array of contacts Get Contact by ID Returns full details for a single contact. Input: - Contact ID (required) Output: - All contact fields Create Contact Creates a new contact record in Zoho CRM. Input: - Last Name (required) - First Name (optional) - Email (optional) - Phone (optional) - Account Name (optional) - Job Title (optional) Output: - Contact ID - Creation status Update Contact Updates fields on an existing contact. Input: - Contact ID (required) - Fields to update Output: - Update status Delete Contact Deletes a contact from Zoho CRM. Input: - Contact ID (required) Output: - Deletion status Account actions Search Accounts Searches accounts by name or field value. Input: - Search criteria Output: - Array of matching accounts List Accounts Returns a list of accounts. Input: - Limit (optional) Output: - Array of accounts Get Account by ID Returns full details for a single account. Input: - Account ID (required) Output: - All account fields Create Account Creates a new account (company) record. Input: - Account Name (required) - Website (optional) - Industry (optional) - Phone (optional) - Billing City, Country (optional) Output: - Account ID Update Account Updates an existing account record. Input: - Account ID (required) - Fields to update Output: - Update status Delete Account Deletes an account from Zoho CRM. Input: - Account ID (required) Output: - Deletion status Deal actions Search Deals Searches deals by name or field value. Input: - Search criteria Output: - Array of matching deals List Deals Returns a list of deals. Input: - Limit (optional) Output: - Array of deals Get Deal by ID Returns full details for a single deal. Input: - Deal ID (required) Output: - All deal fields Create Deal Creates a new deal (opportunity) in Zoho CRM. Input: - Deal Name (required) - Stage (required) - Amount (optional) - Close Date (optional) - Contact ID or Account ID (optional) Output: - Deal ID Update Deal Updates fields on an existing deal. Input: - Deal ID (required) - Fields to update Output: - Update status Delete Deal Deletes a deal from Zoho CRM. Input: - Deal ID (required) Output: - Deletion status Link Deal and Contact Creates a relationship between a deal and a contact. Input: - Deal ID (required) - Contact ID (required) Output: - Link status Unlink Deal and Contact Removes the relationship between a deal and a contact. Input: - Deal ID (required) - Contact ID (required) Output: - Unlink status Campaign actions Get Campaigns Returns a list of campaigns from Zoho CRM. Input: None Output: - Array of campaigns with ID and name Link Record to Campaign Associates a lead or contact with a campaign. Input: - Record ID (required) - Record type (lead or contact) - Campaign ID (required) Output: - Link status Remove Record from Campaign Removes a lead or contact from a campaign. Input: - Record ID (required) - Record type - Campaign ID (required) Output: - Removal status Troubleshooting Create Lead fails with "duplicate record". Zoho CRM checks for duplicates by email. Use Search Leads first to find existing records. Update if found; create if not. The OAuth connection fails or shows "access denied". Your Zoho account may need additional API permissions. Ask your Zoho admin to review the API access settings. Reconnect with an account that has full API access. Field updates are not appearing in Zoho CRM. Some fields have validation rules in Zoho CRM (e.g., a Stage field limited to specific values). Check that the value you are writing matches the accepted values in your Zoho CRM configuration. I cannot see all my custom fields in the input options. Zoho CRM custom field names are case-sensitive and use internal API names. Use the Get Lead by ID or Get Contact by ID action on a test record to see the exact field names Zoho uses.

Last updated on Apr 06, 2026

Connecting TexAu to AI Clients via MCP

Connecting TexAu to AI Clients via MCP This article explains how to set up the TexAu Model Context Protocol (MCP) server, authorize AI clients to call TexAu tools on your behalf, and run automated lead enrichment workflows directly from your chat interface. 🎥 Video Walkthrough Watch this step-by-step video to see how to set up the TexAu MCP server and connect it to your AI clients: Watch the MCP API Setup Video on YouTube What the TexAu MCP Server is used for The Model Context Protocol (MCP) is an open standard that allows AI models to connect directly to external tools. Authorizing Claude, Cursor, Windsurf, Claude Code, or any other MCP client allows the AI to trigger TexAu's 249+ API endpoints directly inside your chat interface. With no secrets or keys to manually copy into configuration files, you can use the remote MCP server to: - Enrich local spreadsheets and files using simple conversational prompts - Run search, web scraping, and lead verification waterfalls on autopilot - Automatically push enriched contacts to CRMs like HubSpot or Salesforce from your chat window - Build multi-step data pipelines entirely through conversation 💳 Pricing & 🔒 Data Privacy Policies To keep operations lean and secure for developers, TexAu enforces the following policies for all API and MCP traffic: - Pay-as-you-go Billing (No Monthly Subscription): The API and MCP servers have no monthly subscription fees. You only pay for the credits you consume. You can configure Auto-Reload to keep your pipelines running. - Direct Request Pipeline (No Data Storage): To ensure maximum data privacy and GDPR/CCPA compliance, TexAu does not store any of your request data on its servers. Input parameters and output results are processed in real-time and returned directly to your AI client. Before you begin To connect the MCP server, you need: - An active TexAu API account and team workspace - An active TexAu API Key (see Getting Started with the TexAu V3 API) - An MCP-compatible AI client installed (such as Claude Desktop, Cursor, Windsurf, Zed, or Claude Code) Step 1: Copy your MCP Server URL Before copying the MCP Server URL, make sure you have generated an API key. Warning: MCP connections bill against an API key on your TexAu API account. If you do not have an active API key first, the MCP Setup page will prompt you: "You need an active API key first. MCP connections bill against an API key on your account. Create one now and we'll bring you back here." 1. Log in to your TexAu API dashboard. 2. If you haven't created an API key yet, go to API Keys in the left sidebar and click Create New Key. 3. Once an API key exists, navigate to the MCP Setup tab in the left sidebar. 4. Under MCP server URL, copy the unique remote URL (typically https://mcp.texau.com/mcp). Step 2: Configure the connection in your AI client The remote HTTP MCP server URL works across all major MCP-compatible tools (such as Claude Desktop, Cursor, Windsurf, Zed, and Claude Code). While configuring Cursor or Windsurf involves editing their respective JSON configurations, this guide uses Claude Desktop as the primary setup example: 1. Open the Claude Desktop application. 2. Click the three-line menu (or gear icon) in the top corner and select Settings (or Customize). 3. Navigate to the Connectors tab. 4. Click Add custom connector. 5. In the configuration fields: - Name: Enter TexAu Enrich (or your preferred display name). - MCP Server URL: Paste the URL you copied in Step 1 (https://mcp.texau.com/mcp). 6. Click Connect. Step 3: Authorize the AI client (OAuth Flow) TexAu uses a secure OAuth flow to connect SaaS tools, meaning there are no secrets or credentials to copy or store inside your AI client. 1. Once you click Connect in your client, Claude will open TexAu in your default browser. 2. Sign in to your TexAu API account (or stay signed in if you already are). 3. You will see a consent screen showing which client is connecting and which TexAu API account/workspace it will bill. 4. Click Allow on the consent screen. 5. You will be redirected back to your AI client, and the TexAu tools will be immediately available. Note: You can revoke access at any time from the Connected Apps tab in your TexAu dashboard. Step 4: Verify the connection in chat 1. Open a new chat in Claude (or your preferred AI client). 2. Type the following prompt to test the integration: “Enrich the LinkedIn profile for linkedin.com/in/satyanadella” 3. Claude will query the TexAu MCP server, execute the profile enrichment tool, and display the verified lead details (such as email, job title, and company) directly in the chat. Step 5: Run bulk lead enrichment on local files Once connected, you can upload lead lists and have your AI client process them using TexAu tools: 1. In your chat bar, type the enrichment prompt, for example: "Use the TexAu Profile Enrichment tool to enrich my Excel file using the LinkedIn URLs inside." 2. Click the + (plus) icon in the chat bar and select Upload from computer. 3. Choose your local Excel or CSV spreadsheet and click Open. 4. Press Enter to submit the file. 5. When prompted by the AI client for tool execution permission, click Always Allow. 6. The AI client will read the file, extract the LinkedIn URLs, run them through TexAu's backend, and display the enriched profiles in a tabular format on the right side of the screen. You can download the completed file directly. Troubleshooting Claude shows a "Not Connected" error. Ensure that your TexAu API key is still active, open Claude's connector settings, and try clicking the Connect button again to re-authorize the link in your browser. Enrichment runs are failing or returning empty data. Go to the Usage and Credits tab in your TexAu API dashboard to check your remaining balance. If your balance is empty, your requests will be rejected. You can enable Auto-Reload in the Buy Credits tab to automatically top up your TexAu API account whenever credits fall below a set limit. Tool execution permissions are prompting too frequently. When you authorize a tool run, check the Always Allow option so that Claude can execute multiple enrichment calls in sequence without prompting you for each row.

Last updated on Jun 03, 2026