Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
This node interacts with the Gladly API to retrieve information about a specific task. The "Get Task" operation allows users to fetch detailed data for a single task by providing its unique identifier. This is useful in scenarios where you need to access or process details of a particular task within an automated workflow, such as tracking task status, updating records, or integrating task data into other systems.
Practical examples include:
- Fetching task details to display in a dashboard.
- Using task information to trigger conditional logic in workflows.
- Synchronizing task data with external project management tools.
Properties
| Name | Meaning |
|---|---|
| Task Id | The unique identifier of the task to retrieve. This is required to specify which task's details should be fetched. |
Output
The node outputs JSON data representing the details of the requested task. The structure typically includes all relevant fields returned by the Gladly API for a task, such as task ID, status, description, assigned user, timestamps, and any other metadata associated with the task.
If the API supports binary data related to tasks (e.g., attachments), the node would handle this accordingly, but based on the provided code and properties, the output focuses on JSON task details only.
Dependencies
- Requires an active connection to the Gladly API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder; in real use, it should point to the actual Gladly API endpoint).
Troubleshooting
- Missing or invalid Task Id: Ensure that the "Task Id" property is provided and correctly formatted. An empty or incorrect ID will result in errors or no data returned.
- Authentication errors: Verify that the API key or token credential is properly configured and has sufficient permissions to access task data.
- API endpoint issues: Confirm that the base URL points to the correct Gladly API server. The current base URL appears to be a placeholder and may need updating.
- Network connectivity: Check network settings and firewall rules to allow outbound requests to the Gladly API.
Common error messages might include:
- Unauthorized or 401 errors indicating missing or invalid credentials.
- 404 Not Found if the specified task ID does not exist.
- Timeout or network errors if the API server is unreachable.
Resolving these usually involves verifying credentials, checking the task ID, and ensuring network connectivity.
Links and References
- Gladly API Documentation (replace with actual URL when available)
- n8n Documentation on HTTP Request Nodes and Credential Setup
- General REST API best practices for authentication and error handling