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.