Overview
The Response Settings Tab defines how LeadExec interprets responses from your client's system after sending leads via webhook. These settings determine successful deliveries, extract pricing information, and handle specialized response requirements.
Response Configuration Settings
Setting | Purpose | Example Values |
Result Search | Identifies successful delivery | "status": "success", "accepted": true |
Regular Expression | Enables pattern matching for complex responses — enable for regex-formatted responses |
|
Price Search | Extracts pricing from responses | "price":, "amount": |
Ping During Sort | Required for Ping/Post deliveries — enable only for Ping/Post methods |
|
Ping Reference Search | Captures ping reference tokens | "referenceId":, "token": |
Redirect URL Search | Extracts redirect URLs for customer journey | "redirectUrl":, "nextStep": |
Step-by-Step Configuration
Access the Response Settings Tab in your Webhook Delivery Method
Configure Result Search:
Input the exact success indicator from your client's API docs
Example: "result": "OK" or "status": 200
Enable Regular Expression if needed:
Check the box only if the client uses regex patterns in responses
Example: Pattern matching for variable success messages
Set Price Search Parameter:
Specify the field name containing price/amount data
Example: "bidAmount": or "price":
Enable Ping During Sort (if applicable):
Check only for Ping/Post delivery methods
Leave unchecked for standard webhooks
Configure Ping Reference Search:
Specify the field containing reference tokens
Example: "transactionId": or "pingRef":
Set Redirect URL Search (if needed):
Specify field containing redirect URLs
Example: "redirectUrl": or "nextPage":
Best Practices
API Documentation Alignment:
Match settings exactly with client's response format documentation
Request sample responses for accurate configuration
Testing Protocol:
Test with sample responses before production use
Validate price extraction and success detection
Regex Considerations:
Use simple string matching when possible
Reserve regex for complex pattern requirements
Validation Checks:
Verify all search patterns work with actual client responses
Confirm price formatting matches your system requirements
Troubleshooting
Success responses not recognized:
Verify that the Result Search matches your client's success format
Prices not captured:
Check Price Search parameter matches response field
Next article: Retry Settings Tab >