Webhooks let you automate what happens after enrichment completes —sending data to your CRM, notifying your team, triggering actions in automation platforms, or pushing results to any custom tool you use.
What are webhooks?
A webhook is an automatic notification sent to an external URL (a web address you control or a service you use) when an event happens in TexAu.
Rather than logging into TexAu to check on results, webhooks bring the results to you —in your CRM, your team chat, your analytics dashboard, or anywhere else you need them.
Common webhook use cases
Here are real-world examples of what our customers do with webhooks:
Push enrichment results to your CRM
You have a workflow that enriches leads with scores and personalized messages. When enrichment finishes, a webhook automatically pushes the results back to your CRM.
Result: Your sales team opens their CRM and sees fresh enrichment data immediately. No manual data entry. No waiting.
Notify your team
When enrichment completes, a webhook sends a message to your team messaging tool with a summary: "50 leads enriched. 35 marked as high-quality. Check TexAu for details."
Result: Your team gets instant visibility into enrichment progress without logging into TexAu.
Trigger downstream automation
Enriched leads need to go through a nurture sequence. A webhook sends results to an automation platform, which then automatically creates tasks, sends welcome emails, and logs data in your warehouse.
Result: Everything flows automatically. Lead enrichment triggers your entire downstream workflow.
Route leads based on conditions
You configure a webhook that routes leads based on enrichment results: high-quality leads go to sales, lower-quality leads go to nurture, and the rest are held for review.
Result: Automatic lead routing based on enrichment data. No manual sorting required.
Keep dashboards up to date
A webhook syncs enriched data to your analytics dashboard every time enrichment completes. Your dashboard always shows the latest information.
Result: Real-time visibility into enrichment results without manual refreshes.
How webhooks work
Here is what happens when a webhook fires:
This table scrolls sideways on small screens.
| Step | What happens |
|---|---|
| 1. Event occurs | Something happens in TexAu (enrichment completes, row is added, etc.) |
| 2. Payload is built | TexAu gathers the relevant data about the event (lead name, enrichment results, timestamps, etc.) |
| 3. Webhook fires | TexAu sends a request to your webhook URL |
| 4. Destination receives data | Your webhook destination receives the data |
| 5. Action is performed | Based on the data, your destination performs an action |
| 6. Confirmation is returned | The destination confirms it received and processed the data |
| 7. Status is logged | TexAu logs whether delivery succeeded or failed |
If delivery fails (your server is down, the URL is wrong, etc.), TexAu automatically retries. More on this in the Delivery and retry logic section below.
Setting up your first webhook
Let us walk through creating a webhook step by step.
Step 1: Identify your trigger event
First, decide what should trigger your webhook:
- Every time a row is enriched?
- When a batch of rows finishes enriching?
- When a workflow completes?
- When an error occurs?
- When a specific condition is met?
Step 2: Prepare your destination URL
Your webhook needs a destination —a URL that will receive the data. This could be:
- An automation platform —These services provide a unique webhook URL that you can copy and paste. Find the webhook URL in the platform's settings.
- A custom integration —You need a web server that can receive POST requests. The URL might look like:
https://api.yourcompany.com/webhooks/texau-enrichment - A CRM endpoint —Your CRM may provide an endpoint for receiving data. Check your CRM's documentation.
Step 3: Create the webhook in TexAu
- Navigate to your table and open the table settings
- Click Webhooks in the settings panel
- Click + Add Webhook
Step 4: Configure basic settings
Fill in the webhook details:
This table scrolls sideways on small screens.
| Field | Description |
|---|---|
| Name | Give your webhook a descriptive name (for example, "Send Enriched Leads to CRM" or "Team Notification on Completion") |
| Event Trigger | Choose what event triggers the webhook (row enriched, batch completed, workflow finished, error occurred, or custom condition) |
| Destination URL | Paste the webhook URL from your destination service |
| HTTP Method | Usually POST (this is the standard for webhooks) |
Step 5: Configure the payload
The "payload" is the data TexAu sends to your webhook. You can choose from preset templates:
This table scrolls sideways on small screens.
| Payload option | What it sends |
|---|---|
| All Data | Everything about the enriched row (all columns, values, metadata) |
| Enriched Fields Only | Only the columns that were enriched |
| Summary | A high-level summary (row ID, status, timestamp) |
| Custom | A custom payload with only the fields you select |
For most use cases, All Data or Enriched Fields Only is the best choice.
If you are using an automation platform, the platform usually handles payload formatting automatically —you might not need to customize this.
Step 6: Configure authentication (optional but recommended)
For security, you can add authentication to your webhook. This makes sure that only TexAu can trigger your endpoint.
This table scrolls sideways on small screens.
| Authentication method | How it works |
|---|---|
| Security Signature | TexAu includes a cryptographic signature in each webhook request. Your destination verifies this signature to confirm the request came from TexAu. |
| API Key | You provide an API key that TexAu includes in each webhook request header. Your destination checks for this key. |
| Basic Auth | You provide a username and password that TexAu includes in each request. |
Security best practice: Always enable authentication. It prevents unauthorized requests from reaching your endpoint.
Step 7: Test your webhook
Before going live, test it:
- Click Test Webhook
- TexAu sends a test request to your webhook URL
- Check that your destination received the data and processed it correctly
- TexAu will show you whether the test succeeded or failed
If the test fails:
- Verify your webhook URL is correct
- Check that your destination service is running and accessible
- Review authentication settings if you have enabled them
- Check your destination's logs to see what error occurred
Step 8: Activate the webhook
Once testing succeeds, click Enable or Activate. Your webhook is now live and will fire whenever the trigger event occurs.
Webhook security
Security matters when using webhooks. Here is what you need to know.
Verify authenticity with security signatures
TexAu can include a security signature in each webhook request. This proves the request came from TexAu and was not tampered with.
How it works:
- TexAu includes a signature in the request header
- Your endpoint receives the signature
- Your code verifies the signature using a shared secret
- If the signature is valid, you process the request
- If invalid, you reject the request
If you are not sure how to implement signature verification, contact TexAu support for guidance and code samples.
Use HTTPS for webhook URLs
Always use HTTPS (not HTTP) for webhook URLs. This encrypts the data in transit and prevents eavesdropping.
If your webhook destination does not support HTTPS, reconsider whether it is secure enough for your use case.
Be careful with sensitive data
Be mindful of what data you include in webhooks. If you are sending personally identifiable information (PII) like email addresses or phone numbers, make sure:
- Your webhook URL uses HTTPS
- Your destination securely stores and handles the data
- You are not logging sensitive data in plain text
Delivery and retry logic
TexAu is designed to deliver webhooks reliably, not just fire them once and forget.
Automatic retries
If your webhook destination is unavailable or returns an error, TexAu retries automatically with an increasing backoff schedule:
This table scrolls sideways on small screens.
| Attempt | Timing |
|---|---|
| 1 | Immediately after the event |
| 2 | 1 minute later |
| 3 | 5 minutes later |
| 4 | 15 minutes later |
| 5 | 1 hour later |
| 6 (Final) | 24 hours later |
If all retries fail, TexAu stops trying and marks the webhook as failed. You can view failed webhooks in your dashboard and retry manually if needed.
Delivery status tracking
For each webhook delivery, TexAu tracks the status:
This table scrolls sideways on small screens.
| Status | Meaning |
|---|---|
| Pending | Webhook is queued, waiting to be sent |
| Processing | Webhook is being sent |
| Completed | Webhook was delivered and confirmed |
| Retrying | Delivery failed but TexAu is retrying |
| Failed | All retry attempts failed; delivery could not be completed |
Webhook event types
Different events can trigger webhooks. Here are the main ones:
This table scrolls sideways on small screens.
| Event type | When it triggers | Best for |
|---|---|---|
| Row Enriched | A single row finishes being enriched | Real-time processing, per-record updates |
| Batch Completed | A group of rows finishes enriching | Bulk operations, batch CRM updates |
| Workflow Finished | An entire workflow run completes | High-level notifications, summary reports |
| Workflow Error | Something goes wrong during enrichment | Error monitoring, alerting your team |
| Custom Conditions | A specific condition you define is met (for example, "lead score > 8") | Conditional routing, targeted automation |
Custom conditions may be available depending on your plan.
Viewing webhook delivery history
To see what webhooks have been triggered and their status:
- Navigate to your table and open the table settings
- Click Webhooks and then Delivery History
- You will see a list of all webhook deliveries with status, timestamps, and details
Click on a delivery to see:
- Exact payload sent
- Response from the destination
- Any error messages
- Retry attempts and their outcomes
This helps you debug issues and verify that your integration is working correctly.
Plan limits
Webhooks are available on most TexAu plans, but there are some differences:
This table scrolls sideways on small screens.
| Feature | Standard plans | Higher-tier plans |
|---|---|---|
| Webhooks per table | Limited | Unlimited |
| Delivery history retention | 7 days | 30 days |
| Custom conditions | Not available | Available |
| Delivery priority | Standard | Priority |
Not sure what your plan includes? Check Settings > Plan Details or contact support.
Troubleshooting failed webhooks
Webhook is not triggering at all
Problem: You created a webhook and an event occurred, but nothing was delivered.
Solutions:
- Verify the webhook is enabled (check the toggle switch)
- Confirm the trigger event is correctly configured
- Verify the destination URL is correct (typos are common)
- Check that the destination service is up and running
- Review the webhook logs for error messages
Webhook triggers but destination is not receiving data
Problem: TexAu says the webhook was delivered, but your destination did not receive it.
Solutions:
- Check your destination's incoming request logs
- Confirm authentication credentials are correct on both sides
- Check firewall rules —is your server blocking requests from external services?
- Verify the destination URL is publicly accessible from the internet
Authentication failures
Problem: Webhook shows "authentication failed" errors.
Solutions:
- Double-check your API key or credentials in TexAu
- Verify the authentication method matches your destination's requirements
- Check that credentials have not expired or been revoked
- Review your destination's documentation for the correct authentication format
Retries keep failing
Problem: TexAu retries your webhook multiple times but keeps failing.
Solutions:
- Check if your destination server is down or experiencing issues
- Review server logs for error messages
- Verify the webhook payload format matches what your destination expects
- Check if there is a rate limit on your destination (you may be hitting it)
- Test manually by sending a request to your webhook URL from another tool
Payload format is wrong
Problem: Your destination received data but in an unexpected format.
Solutions:
- Review the webhook payload configuration in TexAu
- Make sure you chose the right payload template
- Check if you need to customize the payload for your destination
- Review your destination's documentation for the expected format
Best practices
Always use HTTPS
Never use HTTP for webhook URLs. Always use HTTPS to encrypt data in transit.
Enable authentication
Whether using security signatures or API keys, always require some form of authentication on your webhook endpoint.
Test before going live
Always test webhooks with your actual destination before enabling them in production. Use the Test Webhook button to verify everything works end to end.
Monitor delivery status
Periodically check your webhook delivery history to make sure everything is working. Do not assume it is working —verify it.
Handle duplicate deliveries gracefully
Webhooks might occasionally be delivered more than once (if retries occur after a successful delivery). Design your endpoint to handle duplicates gracefully so the same data is not processed twice.
Respond quickly
Your webhook endpoint should respond within 30 seconds. If processing takes longer, acknowledge receipt immediately and queue the work for background processing.
Log incoming webhooks
Log all incoming webhooks on your end so you can debug issues later and maintain an audit trail.
Return appropriate status codes
When your endpoint receives a webhook, respond with:
- 200-299: Success —TexAu will mark the delivery as completed
- 400-499: Client error —TexAu will not retry (the request itself is the problem)
- 500-599: Server error —TexAu will retry according to the backoff schedule
Next steps
- Connecting Integrations —Connect external tools to TexAu for syncing and enrichment
- Managing Integrations —Monitor and maintain your connected integrations
- Getting Started —New to TexAu? Start here for a full walkthrough