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
The "Get Tasks" operation in the "Tasks" resource allows users to retrieve a list of tasks associated with a specific customer from the Gladly API. This node is useful for scenarios where you want to monitor, display, or process tasks related to customer service or support workflows. For example, a customer support dashboard could use this node to fetch all open tasks assigned to a particular customer to prioritize follow-ups.
Properties
| Name | Meaning |
|---|---|
| Customer Id | The unique identifier of the customer whose tasks you want to retrieve. (Required) |
| Status | Filter tasks by their status. Options: OPEN to get active tasks, CLOSED for completed tasks. Defaults to OPEN. |
Output
The node outputs JSON data representing the list of tasks fetched from the API. Each task object typically includes details such as task ID, status, description, and any other metadata provided by the Gladly API. There is no indication that binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Gladly API.
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder). - The node expects the Gladly API to be accessible and properly configured with necessary permissions.
Troubleshooting
- Missing or invalid Customer Id: Since the Customer Id is required, omitting it or providing an incorrect value will likely cause the API call to fail or return no results.
- API authentication errors: If the API key credential is missing or invalid, the node will not be able to authenticate and will throw an error.
- Status filter issues: Providing an unsupported status value may result in no tasks being returned or an error.
- Network or API endpoint issues: Ensure the API base URL is correct and reachable; otherwise, requests will fail.
Links and References
- Gladly API Documentation (for detailed API endpoints and task object schema)
- n8n documentation on creating custom nodes