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 allows you to create a new conversation item in the Gladly platform. A conversation item represents an event or interaction related to a customer within a conversation timeline, such as an email, chat message, or other customer activity.
Common scenarios where this node is useful include:
- Logging customer interactions from external systems into Gladly to maintain a unified customer timeline.
- Automatically creating conversation items based on events like support tickets, marketing emails, or phone calls.
- Enriching customer service workflows by adding contextual information about customer activities.
For example, you could use this node to add a welcome email event to a customer's conversation timeline when they sign up, or to log a recent phone call interaction.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier for the conversation item. Must be URL safe and under 50 characters. If not provided, an ID will be automatically generated. |
| Customer | Specifies the customer the conversation item belongs to. Exactly one of the following must be provided: an email address or a mobile phone number. The value is a JSON object containing these details. |
| Content | Details of the event or interaction to add to the conversation timeline. This is a JSON object describing the type of activity (e.g., CUSTOMER_ACTIVITY), title, body text, activity type (like EMAIL), source name, links, timestamps, and display options. |
Output
The node outputs JSON data representing the created conversation item as returned by the Gladly API. This typically includes all the properties sent in the request along with any additional metadata assigned by the server, such as creation timestamps or status.
There is no binary output.
Dependencies
- Requires access to the Gladly API endpoint.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the API is set to
https://petstore3.swagger.io/api/v3in the bundled code but should be replaced with the actual Gladly API endpoint in production.
Troubleshooting
- Invalid or missing customer information: Ensure that exactly one of email address or mobile phone is provided in the customer JSON object.
- ID conflicts or invalid IDs: The ID must be URL safe and less than 50 characters; otherwise, the API may reject the request.
- Malformed JSON in content or customer fields: Since these fields expect JSON strings parsed before sending, ensure valid JSON syntax.
- Authentication errors: Verify that the API key or token credential is correctly set up in n8n.
- API endpoint misconfiguration: Confirm the base URL points to the correct Gladly API environment.
Links and References
- Gladly API Documentation (for conversation items): Gladly Developer Portal
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- JSON Schema Reference: https://json-schema.org/