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 node interacts with the Gladly API to update existing tasks. Specifically, for the "Tasks" resource and the "Update Task" operation, it allows users to modify details of a task identified by its unique ID. This is useful in workflows where task management automation is needed, such as updating task statuses, descriptions, or other attributes based on external triggers or data changes.
Practical examples include:
- Automatically updating a customer support task status when an email is received.
- Modifying task details in response to changes in a CRM system.
- Synchronizing task information between Gladly and other project management tools.
Properties
| Name | Meaning |
|---|---|
| Task Id | Id of the task that is to be updated |
Output
The node outputs JSON data representing the updated task object returned from the Gladly API. This typically includes all relevant fields of the task after the update has been applied, such as task ID, status, description, timestamps, and any other task-related metadata.
If the node supports binary data output (not evident from the provided code), it would represent attachments or files related to the task, but no such indication is present here.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder; should be replaced with the actual Gladly API endpoint). - Uses an OpenAPI specification (
openapi.json) bundled with the node to define available operations and properties.
Troubleshooting
Common issues:
- Invalid or missing Task Id will cause the update operation to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Using the placeholder base URL instead of the real Gladly API endpoint will lead to connection failures.
Error messages:
- Authentication errors: Check that the API key credential is correctly configured and valid.
- Not found errors: Verify that the Task Id exists in the Gladly system.
- Validation errors: Ensure that all required fields for the update are provided and correctly formatted.
Links and References
- Gladly API documentation (replace with actual URL when available)
- n8n OpenAPI Node integration guide: https://docs.n8n.io/integrations/creating-nodes/openapi/
- General n8n documentation: https://docs.n8n.io/