Webhooks

Trigger TexAu from External Tools with Incoming Webhooks

Trigger TexAu from External Tools with Incoming Webhooks This article explains how to generate an incoming webhook URL so that Zapier, Make, your own application, or any other tool can send data into TexAu. What incoming webhooks do An incoming webhook gives you a unique URL. External tools send HTTP POST requests to this URL to push data into a TexAu table. Each request adds rows or updates existing ones, depending on how you configure the mapping. Before you begin You need a table in TexAu to receive the incoming data. The table can be empty. Column structure can be configured before or after you create the webhook. Create an incoming webhook 1. Go to the table where you want incoming data to be added. 2. Click the Actions button at the top right. 3. Select Webhooks. 4. Choose Incoming Webhook from the popup. 5. Paste a sample JSON payload so TexAu can detect the structure of the incoming data. 6. Map each JSON field to the correct table column. 7. Click Create Webhook. 8. Copy the generated webhook URL. 9. Paste this URL into the external tool that will send data to TexAu. 10. If you make any updates later, such as changing field mappings or columns, click Save Changes again. Configure field mapping Field mapping tells TexAu which fields in the incoming payload correspond to which columns in your table. Send a test payload 1. From your external tool, send a test POST request to the webhook URL with a sample JSON body. Use a tool like Postman or your application's test mode. 2. Return to the incoming webhook configuration screen. TexAu displays the fields it detected in the payload. Map each field to a column 1. For each detected field, click the Target column dropdown. 2. Select the table column that should receive this value. 3. If a field should create a new column, select Add as new column. Authenticate incoming requests (optional) To ensure only authorized tools can send data to your webhook: 1. In the webhook settings, click Authentication. 2. Enable Require signature or Require API key header. 3. Copy the secret or API key and configure your external tool to include it in each request. 4. TexAu rejects requests that do not include valid authentication. Test the connection 1. Click Test incoming webhook. 2. Check that the test payload appears in your table as a new row. 3. Verify the field values are in the correct columns. Activate the webhook Use the toggle to activate or deactivate the webhook when needed. Example: Connect Zapier to TexAu 1. Generate the incoming webhook URL in TexAu. 2. In Zapier, create a new Zap. 3. Add a Webhooks by Zapier action as the final step. 4. Select POST as the method. 5. Paste the TexAu webhook URL in the URL field. 6. Map the Zapier data fields to the JSON keys TexAu expects. 7. Test the Zap. TexAu receives the payload and adds the data as a new row. Troubleshooting POST requests to the webhook URL return a 404 error. The webhook was not activated. Go to the webhook settings and click Activate. Data is arriving but rows are not appearing in the table. Check the field mapping. At least one field must be mapped to a column. Fields not mapped are ignored. The webhook returns a 401 error. Your external tool is not sending the required authentication header. Review the Authentication settings and copy the correct key into your external tool. Fields arrive in the wrong columns. Open the field mapping and verify each payload key points to the correct target column. The table receives duplicate rows. Your external tool is sending the payload more than once. Check the retry settings in the external tool. Outgoing webhooks often retry if the first request does not return 200 fast enough. TexAu responds to all valid requests, including duplicates.

Set Up an Outgoing Webhook

Set Up an Outgoing Webhook This article explains how to create and configure a webhook that sends data from TexAu to an external URL. Before you begin You need: - A TexAu account - The destination URL where you want data sent - Any authentication credentials the destination requires Create a webhook 1. Click Settings in the left sidebar. 2. Click Webhooks. 3. Click New webhook. Configure the webhook Name the webhook Enter a name in the Webhook name field. Use a name that identifies what this webhook sends or where it sends it (e.g., "New contacts to HubSpot" or "Verified emails to Slack"). Set the destination URL Paste the URL in the Destination URL field. TexAu sends a POST request to this URL each time the webhook fires. Choose the trigger event Select when the webhook fires: - Enrichment run completed - fires when a table enrichment run finishes. Sends a summary of the completed run. - Row added - fires each time a new row is added to a table. - Row enrichment completed - fires each time a single row finishes all column enrichments. - Column value updated - fires when a specific column in a table changes to a new value. Click Select event and choose the event type. Select the table (required for row and column events) If the trigger is row-based or column-based, select which table the webhook listens to: 1. Click Select table. 2. Choose the table from your workspace. Add authentication headers To authenticate the requests TexAu sends to your destination: 1. Click Add header. 2. In the first field, enter the header name (e.g., Authorization). 3. In the second field, enter the value (e.g., Bearer your_token). Test the webhook Before saving: 1. Click Send test event. 2. TexAu sends a sample POST request to the destination URL with mock data. 3. Check your destination tool to confirm the request arrived. If you are unsure whether the request arrived, use a tool like webhook.site to inspect incoming requests. Save the webhook Click Save webhook. The webhook is now active and listed on the Webhooks settings page. View webhook history To see past webhook delivery attempts: 1. On the Webhooks settings page, click the webhook name. 2. Click the Delivery history tab. 3. Each attempt shows the timestamp, HTTP status code, and the payload that was sent. Click any attempt to view the full request body and response. Pause or delete a webhook To pause a webhook without deleting it: 1. Find the webhook on the settings page. 2. Toggle off the Active switch. To delete a webhook: 1. Find the webhook. 2. Click the three-dot menu next to it. 3. Click Delete. 4. Confirm the deletion. Troubleshooting The webhook fires but the destination shows no request. Check that the destination URL is publicly accessible. Local URLs (localhost, 127.0.0.1) do not work with outgoing webhooks. Use a service like ngrok to expose a local server, or test with webhook.site. The destination returns a 401 error. The authentication header is missing or wrong. Verify the header name and value against the destination API's documentation. The webhook fires too many times. If you use "Row enrichment completed" on a large table, the webhook fires once per row. For summaries, use "Enrichment run completed" to receive one event per full run. The webhook is listed as active but is not firing. Check that the trigger event matches what is actually happening in your table. If the event is "Row added" but you are only running enrichments on existing rows, the webhook will not fire.

Use Webhooks Inside the Table View

Use Webhooks Inside the Table View This article explains how to configure and trigger webhooks directly from a table in TexAu, without going through the Settings menu. What table-level webhooks do The table view gives you quick access to your outgoing and incoming webhooks for that specific table. You can configure a webhook once and trigger it every time an enrichment run completes. Open the webhook panel 1. Open the table. 2. Click the Webhooks icon in the top toolbar. It resembles two connected arrows. The webhook panel opens on the right side of the screen. Set up an outgoing webhook from the table 1. Click the Outgoing tab. 2. Click Add outgoing webhook. 3. Paste the destination URL in the URL field. 4. Select when to send data: - Row completed - sends one request for each row as soon as it finishes enrichment. - Batch completed - sends all completed rows in one request after the full run finishes. 5. Under Payload, select which columns to include in each outgoing payload. 6. Click Save. Add authentication headers 1. Click Headers in the outgoing webhook section. 2. Click Add header. 3. Enter the header name (e.g., Authorization) and value (e.g., Bearer yourtoken). 4. Click Save. Set up an incoming webhook from the table 1. Click the Incoming tab. 2. Click Generate URL. 3. Copy the URL that appears. Use this URL in a Zapier Zap, Make scenario, or your own app to push rows into this table. 4. Map the incoming payload fields to columns in the table. See the article Trigger TexAu from External Tools with Incoming Webhooks for detailed steps. Trigger a webhook manually You can send a webhook for a specific row without waiting for a full enrichment run. 1. Right-click the row you want to send. 2. Select Send to webhook. 3. Select the outgoing webhook to use. 4. Click Send. The row data is posted immediately to the webhook URL. View recent webhook activity 1. Open the webhook panel from the table toolbar. 2. Click Activity at the top of the panel. You see a list of recent deliveries with: - Delivery time - HTTP status code - Payload size - Destination URL Click any entry to see the full payload sent and the response received. Troubleshooting The Webhooks icon is not visible in the toolbar. Your plan does not include webhook access, or the table template does not have webhooks enabled. Check your plan under Settings > Billing. The webhook was sent but nothing arrived at the destination. Click the delivery in Activity and check the response code. A 5xx response means the destination server had a problem. A 4xx response means the URL or authentication is incorrect. Each row is sending a duplicate webhook. Check whether both a table-level webhook and a global outgoing webhook are configured for the same event. Remove one. The incoming webhook is not adding rows. Confirm that the payload uses the correct JSON structure. Check the field mapping and ensure at least one field maps to a column. Requests that have no matching mappings are ignored. I cannot find the outgoing webhook I configured. Table-level webhooks appear only in the table where they were created. Go back to the correct table and open the Webhooks panel.