Copilot

Build a Workflow with Copilot

Build a Workflow with Copilot This article explains how to use Copilot to build an enrichment workflow from a plain-language description. Before you begin - You need a TexAu account. - If your workflow uses a specific integration (Apollo, HubSpot, etc.), connect it at Settings > Integrations before starting. Copilot can suggest actions, but it cannot connect integrations for you. Step 1: Open Copilot 1. Click Copilot in the left sidebar. 2. The chat panel opens on the right side of the screen. Step 2: Describe your goal Type what you want to accomplish. Be specific about: - The input data you have (LinkedIn URLs, email addresses, company domains, a CSV file) - The output data you want (mobile numbers, job titles, company funding info, HubSpot contact records) Example prompts that work well "I have a list of LinkedIn profile URLs. Find the work email and mobile number for each person." "I have company domains. I want to enrich each with: company name, employee count, industry, and headquarters location." "Build a table that searches LinkedIn for Software Engineers at Series A startups in the US with between 50 and 200 employees." "I want to verify a list of emails and push the valid ones to a HubSpot list." What makes a prompt effective - State the input type explicitly. Copilot responds differently to "LinkedIn URLs" vs "email addresses." - Name the output fields you want. "Find the CEO name, LinkedIn URL, and email" gives Copilot a clear target. - Mention the integration if you know which one you want to use. "Using Apollo" or "Using BetterEnrich" directs Copilot to specific actions. Step 3: Review Copilot's plan After you send your message, Copilot describes the table structure it will create. The response includes: - The table name it will use - The columns it will add and their types - The actions it will attach to each column - The input mappings it plans to configure Read the plan carefully before confirming. Step 4: Confirm or refine If the plan looks correct, click Confirm or type "yes" to proceed. If the plan is not right, describe what you want to change: - "Use FullEnrich instead of BetterEnrich for the email column." - "Add a column that also captures the company LinkedIn URL." - "Skip the email verification step." Copilot adjusts the plan and shows you the updated version. Step 5: Run enrichment After Copilot creates the table and columns: 1. Click the table in the main area. 2. Add or import your input data if the table is empty. 3. Click Run enrichment in the top toolbar. 4. Select the rows you want to enrich. 5. Click Run. Copilot does not start the enrichment run. You control when enrichment executes. Edit Copilot-generated columns Columns created by Copilot behave identically to columns you build manually. You can: - Click a column header to open its configuration panel - Change the action - Adjust input mappings - Add or remove output fields - Set conditions You do not need to use Copilot to make changes to columns it created. Troubleshooting Copilot creates columns but does not map the inputs correctly. Open each column's configuration panel and verify the input mappings. Adjust them to point to the correct source columns. Copilot uses an integration I do not have connected. Connect the integration at Settings > Integrations, then ask Copilot to rebuild the table or add the column again. Copilot generates too many columns. Ask Copilot to simplify: "Remove the company description column and keep only the email, phone, and job title." The table Copilot creates is blank after enrichment. Check that your input data is in the correct format for the actions being used. For example, LinkedIn URL columns must contain valid linkedin.com/in/ URLs, not people's names or company names.

Configure an Incoming Webhook in Copilot

Configure an Incoming Webhook in Copilot This article explains how to set up an incoming webhook inside TexAu Copilot so that external tools can send data directly into a Copilot workflow. What an incoming webhook does in Copilot An incoming webhook gives you a unique URL. When an external tool sends a POST request to that URL, Copilot receives the payload and can act on it. For example, it can add rows to a table, trigger an enrichment run, or start a workflow. Use this when you want to connect Zapier, Make, your own app, or any other tool to a Copilot workflow. Before you begin You need a Copilot workflow set up. If you do not have one yet, see Build a Workflow with Copilot. Generate the webhook URL 1. Open the Copilot workflow you want to connect to. 2. Click the Webhooks icon in the Copilot toolbar, or type "Set up an incoming webhook" in the chat. 3. The incoming webhook configuration form opens. 4. Click Generate webhook URL. 5. Copy the URL that appears. You will paste this into your external tool. Configure the payload mapping After generating the URL, you need to tell TexAu what fields to expect in the incoming payload and where to put them. Send a test payload 1. Go to your external tool (Zapier, Make, a REST client, etc.). 2. Send a POST request to the webhook URL with a sample JSON body. For example: { "firstName": "Jane", "lastName": "Smith", "linkedinUrl": "https://linkedin.com/in/janesmith", "company": "Acme Corp" } 3. Return to the Copilot incoming webhook form. The sample payload appears automatically. Map fields to columns 1. In the Field mapping section, each key from the payload appears as a row. 2. For each field, select which table column should receive the value. 3. If you want a field to create a new column, select Create new column from the dropdown. 4. Click Save mapping. Authenticate inbound requests (optional) To verify that requests to your webhook come from a trusted source: 1. In the webhook form, click Show authentication options. 2. Enable Signature verification. 3. Copy the secret key. 4. Configure your external tool to sign requests with this key. TexAu rejects requests that do not include a valid signature. Test the webhook 1. Click Test webhook in the configuration form. 2. TexAu sends a test signal and confirms the connection is working. 3. A success message appears when the webhook is active. Troubleshooting The webhook URL returns a 404 error. The webhook was not saved. Complete the configuration and click Save before testing. Payloads are arriving but rows are not being created. Check the field mapping. At least one field must be mapped to a column for rows to appear. If no fields are mapped, the payload is received but ignored. The signature verification is failing. The secret key in your external tool does not match the key in TexAu. Copy the key again from the webhook form and update it in your external tool. The webhook receives data but the wrong column is being populated. Open the field mapping section and verify each payload key maps to the correct column.

Configure an Outgoing Webhook in Copilot

Configure an Outgoing Webhook in Copilot This article explains how to set up an outgoing webhook in TexAu Copilot so that enrichment results are automatically sent to an external URL when a workflow completes or when a condition is met. What an outgoing webhook does in Copilot An outgoing webhook sends a POST request to a URL you specify whenever a trigger fires. The request body contains the row data from your TexAu workflow. Use this to push enrichment results to a CRM, a Slack channel, a database, or any service that accepts HTTP requests. Before you begin You need: - A Copilot workflow with enrichment columns set up - The destination URL where you want TexAu to send data - Any authentication headers the destination requires (API key, bearer token) Open the outgoing webhook form 1. Open your Copilot workflow. 2. Click the Webhooks icon in the Copilot toolbar, or type "Set up an outgoing webhook" in the chat. 3. Click Outgoing to switch to the outgoing configuration tab. Configure the destination URL 1. Paste your destination URL in the Webhook URL field. 2. Select the HTTP method. For most webhook receivers, use POST. Add authentication headers If the destination requires authentication: 1. Click Add header. 2. Enter the header name (e.g., Authorization or X-API-Key). 3. Enter the value (e.g., Bearer your_token or your_api_key). Set the trigger Choose when TexAu fires the webhook: - Row enrichment complete: fires once for each row after all columns in that row finish running - All rows complete: fires once after the entire enrichment run finishes - Column result meets condition: fires when a specific column value satisfies a condition you define (e.g., "email is not empty" or "status equals verified") Click Select trigger and choose from the list. Configure the payload By default, TexAu sends all column values for the row in the payload. To customize what is sent: 1. Click Customize payload. 2. Toggle off any fields you do not want to include. 3. Rename field keys if the destination expects specific field names. The payload is sent as JSON. Each key in the payload corresponds to a column in your table. Enable retries If the destination URL returns a non-200 response, TexAu can retry the request: 1. Toggle on Retry on failure. 2. Set the number of retry attempts (maximum 3). 3. TexAu retries with exponential backoff. Test the webhook 1. Click Send test request. 2. TexAu sends a request with sample data to the destination URL. 3. A confirmation appears showing the HTTP status code returned. If the destination is a tool with logs (like webhook.site or a Zapier catch hook), check those logs to verify the payload structure. Save and activate Click Save webhook to activate it. TexAu begins firing the webhook on the next enrichment run. Troubleshooting The test request returns a timeout. The destination URL is not responding. Verify the URL is correct and the destination service is online. The test request returns a 401 or 403 error. The authentication header is missing or incorrect. Check the header name and value with the destination service's documentation. Rows complete but the webhook does not fire. Check that the trigger is set to the correct event. If the trigger is Column result meets condition, verify the condition matches values that actually appear in your data. The destination receives the webhook but the data fields are missing. Open the payload configuration and verify the fields you need are toggled on. Also check that the columns producing those values are not empty for the rows being sent.

Copilot Tips for Better Workflows

Copilot Tips for Better Workflows This article gives you practical techniques to get better results from TexAu Copilot. Write a goal, not a list of steps Copilot responds better when you describe an outcome than when you list columns. Less effective: "Add a column using BetterEnrich to find email. Add another column to verify the email." More effective: "I have a list of LinkedIn profile URLs. Find verified work emails for each person." Give Copilot the context it needs to pick the right actions in the right order. Include the data you already have Tell Copilot what columns exist in the table. This helps it map inputs correctly. Example: "The table already has First Name, Last Name, Company Name, and LinkedIn URL. Find the work email using whichever data gives the best coverage." If Copilot does not know what is available, it may ask you to add columns that already exist. Ask for waterfall enrichment explicitly Waterfall enrichment runs multiple providers in sequence and uses the first successful result. Ask for it directly. Example: "Use waterfall enrichment to find the email. Try BetterEnrich first, then FullEnrich, then Findymail." Copilot will set up a parent column and one provider column per provider, in the order you specified. Review the plan before confirming Copilot displays its proposed column structure before building anything. Read through each column: - Check the action names. Do they match what you need? - Check the input mapping. Are inputs pointing to the right columns? - Check the output column names. Rename them if the defaults are unclear. Click Edit plan to change anything before Copilot builds. Iterate in small steps If your workflow is complex, build it in stages. Start with one task: "Find the LinkedIn URL for each person using their name and company." Run it and verify the results. Then continue: "Now find the work email using the LinkedIn URL you just added." This makes it easier to catch problems. If something fails, you know which step broke. Rename columns after Copilot builds Copilot generates column names based on the action it selects. These names are often long or technical. Rename them so the table is readable. 1. Double-click the column header. 2. Type the new name. 3. Press Enter. This does not affect how the enrichment runs. Switch to manual configuration for advanced control Copilot is fast for setting up standard workflows. Switch to manual configuration when you need: - Custom HTTP requests with non-standard authentication - Formulas that combine multiple column values before passing them to an action - Pagination or offset control in a data source column - Conditional waterfall logic (e.g., "only try provider B if provider A returns empty") To manually configure a column that Copilot built: click the column header, click the settings icon, and modify the configuration directly. Save your workflow as a template After building a workflow with Copilot, save it so you can reuse it on other tables. 1. Click Templates in the top toolbar. 2. Click Save as template. 3. Give the template a name. 4. Click Save. You can load this template on any new table from the Templates menu. What Copilot cannot do - Run an enrichment. You start runs manually. - Connect integrations. Do that in Settings > Integrations before using Copilot. - Access data outside TexAu. Copilot works only with columns and actions available in your workspace. - Guarantee a specific number of credits. Credit cost depends on the actions selected and the number of rows. Troubleshooting Copilot suggests an action that requires an integration I have not connected. Connect the integration first under Settings > Integrations, then return to Copilot and describe your goal again. Copilot builds the wrong column type. Click Edit plan before confirming. Change the action on the column in question. If the plan is already built, delete the column and add the correct one manually. The column Copilot built has no output fields mapped. This happens when Copilot could not determine which output fields to use. Open the column settings, go to Outputs, and map the fields you need. Copilot is not responding to my message. Refresh the page and try your message again. If the issue continues, clear your browser cache. Copilot context resets when you reload, so rephrase your goal from the start.

Introduction to TexAu Copilot

Introduction to TexAu Copilot This article explains what TexAu Copilot is, what it does, and when to use it. What Copilot is Copilot is a conversational AI assistant built into TexAu. You describe what you want to do in plain language, and Copilot builds the table structure, selects the right actions, and configures the columns for you. Copilot is on the left sidebar. Click Copilot to open the chat interface. What Copilot can do - Build a new enrichment table from a description - Add columns to an existing table based on your instructions - Suggest which actions to use for a given goal - Explain what a column or action does when you ask - Configure incoming and outgoing webhooks from the chat - Answer questions about your data When to use Copilot vs building manually Use Copilot when: - You are not sure which action or data source to use for your goal - You want to set up a multi-column enrichment workflow quickly - You want to describe a use case and have the structure built for you Build manually when: - You have a precise column configuration you need to control exactly - You need to adjust input mappings, output field names, or conditions at a granular level - You are modifying an existing column you built yourself You can start with Copilot and then edit the columns it generates manually. The two approaches work together. Open Copilot 1. Click Copilot in the left sidebar. 2. The Copilot chat panel opens. 3. Type your request in the message input at the bottom and press Enter or click the send button. Example requests These are examples of what you can type to Copilot: - "Build me a table that finds email addresses from LinkedIn URLs" - "Add a column that verifies emails in my current table" - "I have a list of company domains. I want to find the CEO's name and LinkedIn URL for each one." - "Set up a webhook that sends new rows to my CRM when enrichment completes" Copilot responds with the table structure it plans to create and asks you to confirm before making any changes. What happens after you confirm After you approve Copilot's plan: 1. Copilot creates or updates the table with the columns it described. 2. Each column is fully configured with input mappings and output fields. 3. You can run enrichment immediately or review the configuration first. What Copilot cannot do - Copilot cannot run enrichment directly from the chat. Click Run enrichment in the table toolbar to execute. - Copilot does not access your data after the table is set up. It builds structure, not results. - Copilot cannot connect integrations. If an action requires an API key, connect the integration first at Settings > Integrations. Troubleshooting Copilot does not respond after I type my message. Check your internet connection. Refresh the page and try again. Copilot builds a table that is not what I described. Rephrase your request with more specifics. Include the type of input data you have (LinkedIn URLs, email addresses, company domains) and the output you want (mobile number, job title, company size). Copilot tries to use an action I do not have access to. The suggested action may require an integration that is not connected or a plan upgrade. Check Settings > Integrations to connect the required provider, or go to Settings > Billing to review your plan.