Test Agent Runner¶
A webhook-based workflow that serves as a testing interface for the SalesTrackingAgent system, accepting HTTP POST requests with customer queries and routing them to the main sales tracking workflow for processing.
Purpose¶
No business context provided yet — add a context.md to enrich this documentation.
This workflow appears to be designed as a testing or development interface that allows external systems to submit customer queries to a sales tracking agent. It acts as a simple HTTP API endpoint that accepts customer information and forwards it to another workflow for processing.
How It Works¶
- Receive Request: The workflow starts when an HTTP POST request is made to the
/sifa-testendpoint - Extract Data: The incoming request body is parsed to extract three key pieces of information: phone number, customer query, and communication channel
- Forward to Agent: The extracted data is passed to the SalesTrackingAgent workflow for processing
- Return Response: The response from the SalesTrackingAgent is returned to the original caller
Workflow Diagram¶
graph TD
A[Webhook<br/>POST /sifa-test] --> B[Extract Body<br/>Parse Request Data]
B --> C[Call SalesTrackingAgent<br/>Execute Workflow]
style A fill:#e1f5fe
style B fill:#f3e5f5
style C fill:#e8f5e8
Trigger¶
Webhook Trigger
- Method: POST
- Path: /sifa-test
- Webhook ID: sifa-test-id
- Response Mode: Returns the output from the last node
The workflow is triggered by HTTP POST requests to the designated endpoint.
Nodes Used¶
| Node Type | Node Name | Purpose |
|---|---|---|
| Webhook | Webhook | Receives HTTP POST requests and triggers the workflow |
| Set | Extract Body | Extracts and structures data from the incoming request |
| Execute Workflow | Call SalesTrackingAgent | Calls another n8n workflow to process the extracted data |
External Services & Credentials Required¶
n8n Workflow Access
- Access to workflow ID aygyT37fIK22WZ9a (SalesTrackingAgent)
- Proper workflow execution permissions within the same n8n instance
No external API credentials are required for this workflow as it only orchestrates data between internal n8n workflows.
Environment Variables¶
No environment variables are used in this workflow. All configuration is handled through node parameters.
Data Flow¶
Input (HTTP POST Request Body):
1 2 3 4 5 | |
Processing: - Phone number, query, and channel are extracted from the request body - Data is passed to the SalesTrackingAgent workflow with the same field structure
Output: - Returns whatever the SalesTrackingAgent workflow produces - Response format depends on the called workflow's implementation
Error Handling¶
This workflow does not implement explicit error handling. Errors would be handled by: - n8n's default error handling mechanisms - Any error handling implemented in the called SalesTrackingAgent workflow - Standard HTTP error responses for malformed requests
Known Limitations¶
- No input validation on the incoming request data
- No authentication or authorization mechanisms
- Depends entirely on the availability and proper functioning of the SalesTrackingAgent workflow
- No retry logic if the called workflow fails
Related Workflows¶
- SalesTrackingAgent (ID:
aygyT37fIK22WZ9a): The main workflow that this test runner calls to process customer queries
Setup Instructions¶
-
Import the Workflow
- Import the workflow JSON into your n8n instance
- Ensure the workflow is activated
-
Verify Dependencies
- Confirm that workflow
aygyT37fIK22WZ9a(SalesTrackingAgent) exists and is accessible - Check that the caller policy allows execution from the same owner
- Confirm that workflow
-
Configure Webhook
- The webhook will be automatically available at
/webhook/sifa-test - Note the full webhook URL for testing purposes
- The webhook will be automatically available at
-
Test the Workflow
- Send a POST request to the webhook endpoint with the required JSON structure
- Verify that the request is properly forwarded to the SalesTrackingAgent workflow
-
Monitor Execution
- Check the execution history to ensure proper data flow
- Verify that responses are being returned correctly
Example Test Request:
1 2 3 4 5 6 7 | |