Test Agent Runner¶
A simple webhook-based testing interface that accepts customer queries and forwards them to the SalesTrackingAgent workflow for processing. This workflow serves as a development and testing entry point for validating agent functionality.
Purpose¶
No business context provided yet — add a context.md to enrich this documentation.
How It Works¶
- Receive Request: A webhook listens for POST requests containing customer interaction data
- Extract Data: The workflow extracts phone number, query text, and communication channel from the request body
- Forward to Agent: The extracted data is passed to the SalesTrackingAgent workflow for processing
- Return Response: The agent's response is returned to the original caller
Workflow Diagram¶
graph TD
A[Webhook<br/>POST /sifa-v4-test] --> B[Extract Body<br/>Parse phoneNumber, query, channel]
B --> C[Call SalesTrackingAgent<br/>Execute workflow xtOmBg6ht3gq931x]
C --> D[Return Response]
Trigger¶
Webhook: POST /sifa-v4-test
The workflow is triggered by HTTP POST requests to the webhook endpoint. It expects JSON data in the request body containing customer interaction details.
Nodes Used¶
| Node Type | Node Name | Purpose |
|---|---|---|
| Webhook | Webhook | Receives incoming POST requests and triggers the workflow |
| Set | Extract Body | Extracts and structures data from the webhook request body |
| Execute Workflow | Call SalesTrackingAgent | Invokes the main SalesTrackingAgent workflow with the extracted data |
External Services & Credentials Required¶
- Internal Workflow Dependency: Requires access to workflow
xtOmBg6ht3gq931x(V4 - WIP - Francis - SalesTrackingAgent) - No external API credentials required for this workflow itself
Environment Variables¶
No environment variables are used in this workflow.
Data Flow¶
Input (Webhook Body)¶
1 2 3 4 5 | |
Processing¶
- Extracts the three fields from the request body
- Passes them as inputs to the SalesTrackingAgent workflow
Output¶
Returns the response from the SalesTrackingAgent workflow (format depends on that workflow's implementation).
Error Handling¶
This workflow uses basic n8n error handling: - Invalid JSON in the webhook body will cause the Extract Body node to fail - If the target SalesTrackingAgent workflow is unavailable or fails, the Execute Workflow node will error - No custom error handling or retry logic is implemented
Known Limitations¶
- Depends entirely on the availability and functionality of the SalesTrackingAgent workflow
- No input validation on the webhook data
- No authentication or rate limiting on the webhook endpoint
- Errors from the child workflow are passed through without additional context
Related Workflows¶
- V4 - WIP - Francis - SalesTrackingAgent (
xtOmBg6ht3gq931x): The main agent workflow that this testing interface calls
Setup Instructions¶
- Import Workflow: Import this workflow into your n8n instance
- Verify Dependencies: Ensure the SalesTrackingAgent workflow (
xtOmBg6ht3gq931x) exists and is accessible - Activate Workflow: Enable the workflow to make the webhook endpoint available
- Test Connection: Send a test POST request to
/sifa-v4-testwith sample data:1 2 3 4 5 6 7
curl -X POST https://your-n8n-instance/webhook/sifa-v4-test \ -H "Content-Type: application/json" \ -d '{ "phoneNumber": "+1234567890", "query": "Test query", "channel": "web" }' - Monitor Execution: Check the execution history to verify the workflow runs successfully and the SalesTrackingAgent responds appropriately