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 creates a "Recipient Collection" within the Proactive Conversations resource. A recipient collection is essentially a group of recipients defined by their contact details and time constraints, which can be used to send proactive messages or notifications. This is useful in scenarios such as sending delivery reminders, appointment notifications, or any batch communication where timing and recipient grouping matter.
For example, you might create a recipient collection named "Delivery reminders" that includes customers who should receive notifications about their upcoming deliveries within a specific time window.
Properties
| Name | Meaning |
|---|---|
| Name | The name assigned to the recipient collection (e.g., "Delivery reminders"). |
| Start After | The timestamp after which the recipient collection should start processing recipients. |
| End Before | The timestamp before which the recipient collection should stop processing recipients. |
| Recipients | A JSON array defining the recipients in the collection. Each recipient includes details like customer name, email address, and timezone. |
Output
The node outputs JSON data representing the created recipient collection. This typically includes confirmation details such as the collection's ID, name, processing time window, and the list of recipients added. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly API endpoint at
https://petstore3.swagger.io/api/v3(likely a placeholder URL). - Proper configuration of the API authentication credentials in n8n is necessary for successful requests.
Troubleshooting
- Invalid timestamps: Ensure that the "Start After" and "End Before" properties are valid ISO 8601 date-time strings. Incorrect formats may cause API errors.
- Malformed recipients JSON: The "Recipients" property must be a valid JSON array. Parsing errors will prevent the request from being sent.
- Authentication errors: Missing or invalid API credentials will result in authorization failures.
- API endpoint issues: If the base URL is not correctly set or the API is unreachable, the node will fail to create the recipient collection.
Links and References
- Gladly API documentation (for Proactive Conversations and Recipient Collections) — consult the official Gladly developer portal.
- n8n documentation on creating custom nodes and using API credentials.