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 interacts with the Gladly API to find export jobs based on their status and update time. It is useful for retrieving a list of export jobs filtered by their current state (e.g., completed, pending) and the time window during which they were last updated. Typical use cases include monitoring export job progress, auditing completed exports, or troubleshooting failed export jobs.
For example, you could use this node to:
- Retrieve all export jobs that have completed in the last 24 hours.
- Find export jobs that are currently in progress to track ongoing data exports.
- Identify failed export jobs within a specific date range for error handling or retries.
Properties
| Name | Meaning |
|---|---|
| Status | The export job status to filter on. Options: PENDING, IN PROGRESS, COMPLETED, FAILED. |
| Start At | The start datetime (ISO 8601 format) to filter export jobs by their last update time (updatedAt). Cannot be more than 14 days ago. Default is 14 days ago. |
| End At | The end datetime (ISO 8601 format) to filter export jobs by their last update time (updatedAt). Cannot be before Start At or in the future. Default is now. |
Output
The node outputs JSON data representing the list of export jobs matching the specified filters. Each item in the output typically contains details about an export job such as its ID, status, timestamps, and other metadata provided by the Gladly API.
No binary data output is indicated by the source code or properties.
Dependencies
- Requires access to the Gladly API endpoint.
- Needs an API key credential or similar authentication token configured in n8n to authorize requests to the Gladly API.
- The base URL for API requests is set to
"https://petstore3.swagger.io/api/v3"in the bundled code, which appears to be a placeholder; in production, this should be replaced with the actual Gladly API base URL.
Troubleshooting
- Invalid Date Range: If
Start Atis set more than 14 days ago orEnd Atis beforeStart At, the API may reject the request or return no results. Ensure dates are valid and in ISO 8601 format. - Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key or token is correctly configured.
- No Results Returned: If no export jobs match the filters, the output will be empty. Try broadening the date range or changing the status filter.
- API Endpoint Issues: The default base URL in the code is a placeholder. Make sure the node configuration points to the correct Gladly API endpoint.
Links and References
- Gladly API Documentation (replace with actual URL)
- ISO 8601 Date Format
- n8n Node Development Guide