Home Copilot Copilot Tips for Better Workflows

Copilot Tips for Better Workflows

Last updated on Apr 06, 2026

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.