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 operation "Create Task And Customer" under the "Tasks" resource allows users to create a new task in the system and associate it with a customer simultaneously. It is useful for workflows where tasks need to be generated dynamically based on customer information, such as follow-up calls, support tickets, or reminders.
Practical examples include:
- Automatically creating a callback task for a customer after a support interaction.
- Scheduling a task to send promotional offers to a specific customer.
- Assigning a task to an agent to review a customer's recent order or inquiry.
Properties
| Name | Meaning |
|---|---|
| Id | Specifies the unique identifier of the task to be created. |
| Assignee | Inbox and agent assigned to handle the task. This includes selecting an inbox ID and an agent ID. |
| Body | Text description of what the task entails. Supports constrained HTML rich content formatting. |
| Due At | The due date and time for the task completion. Must be set to a future timestamp (ISO 8601 format). |
| Customer | JSON object specifying the customer details the task belongs to. Exactly one of the customer identifiers must be provided (e.g., email address or mobile phone). |
Output
The node outputs JSON data representing the newly created task along with its associated customer information. The output structure typically includes fields such as task ID, assignee details, task body, due date, and customer contact info.
If binary data were involved (not indicated here), it would represent attachments or related files, but this operation focuses on JSON task and customer data only.
Dependencies
- Requires access to the Gladly API endpoint (or equivalent service) to create tasks and customers.
- 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/v3in the bundled code, which is likely a placeholder; in production, this should point to the actual Gladly API endpoint.
Troubleshooting
- Invalid Due Date: If the "Due At" property is set to a past date/time, the API may reject the request. Ensure the due date is always in the future.
- Missing Required Fields: The operation requires "Assignee", "Body", "Due At", and "Customer" properties. Omitting any will cause errors.
- Customer Identification: Exactly one customer identifier must be provided (e.g., email or phone). Providing none or multiple may result in validation errors.
- Authentication Errors: If the API key or token is missing or invalid, the node will fail to authenticate. Verify credential configuration.
- API Endpoint Misconfiguration: The default base URL points to a Swagger petstore example. Replace it with the correct API URL to avoid connection failures.
Links and References
- Gladly API Documentation (replace with actual link)
- n8n Node Development Guide
- ISO 8601 Date Format Reference