Send and Wait for Response
AI-generatedOverview
The Velatir node is designed for AI compliance and approval workflows. In the 'Send and Wait for Response' operation, it sends data (arguments) along with specified tool calls and waits for a response within a defined timeout period. This is useful in scenarios where you need to track and manage asynchronous interactions or approvals, such as customer onboarding or compliance checks, by grouping related traces with a session ID and categorizing the direction of the trace (inlet, response, or signal).
Use Case Examples
- Sending a request to multiple tools like Gmail and HubSpot and waiting for their responses to proceed with a workflow.
- Tracking an approval process by sending data and waiting for a response within a specified timeout, grouping all related traces under a session ID.
Properties
| Name | Meaning |
|---|---|
| Tool Calls | Comma-separated list of tool names being called, indicating which external tools or services are involved in the operation. |
| Arguments | JSON object containing the data to be assessed or sent in the request. |
| Session ID | ID to group related traces together, defaults to the n8n execution ID if not provided. |
| Direction | Direction of the trace, indicating whether the data is an incoming request (inlet), outgoing response (response), or an internal signal/event (signal). |
| Title | Custom title for the trace to provide context or description. |
| Additional Fields | Collection of optional additional fields including metadata (JSON) and timeout in minutes to specify the maximum time to wait for a response. |
Output
JSON
traceId- Unique identifier for the trace created or processed.status- Status of the send and wait operation, e.g., success, timeout, or error.responseData- Data received in response to the sent request, if any.
Dependencies
- API authentication token or credentials for the external tools specified in Tool Calls
Troubleshooting
- Ensure the Tool Calls property is correctly formatted as a comma-separated list of valid tool names to avoid errors.
- Verify that the JSON in Arguments is well-formed to prevent parsing errors.
- If the operation times out, consider increasing the Timeout (Minutes) value or check the external tools' responsiveness.
- Check that the Session ID is unique or correctly set to group related traces properly.