Actions7
Overview
This node integrates with the eKyte platform to create and retrieve various types of data such as tasks, projects, tickets, boards, workspaces, notes, and notifications. Specifically, the Get Notifications operation fetches notifications for a specified user email from eKyte.
Typical use cases include:
- Automatically retrieving new notifications for a user to trigger workflows based on updates or alerts.
- Monitoring eKyte notifications in real-time or at scheduled intervals to keep teams informed.
- Integrating eKyte notifications into other systems like messaging platforms or dashboards.
Example: A workflow that periodically checks for new notifications for a user and sends an alert email or posts a message to a team chat when new notifications arrive.
Properties
| Name | Meaning |
|---|---|
| The user email address associated with the eKyte account for which to get notifications. |
Output
The output is an array of JSON objects, each representing a notification retrieved from eKyte for the specified user. Each item contains the full notification data as returned by the eKyte API.
No binary data is produced by this operation.
Example output structure (simplified):
[
{
"json": {
"id": "notification_id",
"title": "Notification title",
"message": "Notification message content",
"date": "2024-06-01T12:00:00Z",
...
}
},
...
]
Dependencies
- Requires an API key credential and company ID configured in n8n to authenticate requests to the eKyte API.
- The node makes HTTP GET requests to the eKyte API endpoint
https://api.ekyte.com/n8n/polling/notifications. - The user must provide a valid user email for the eKyte operations.
Troubleshooting
Minimum Interval Enforcement: The node enforces a minimum interval of 15 minutes between calls to the same operation to avoid excessive API requests. If you try to run the operation again before 15 minutes have passed, it will throw an error indicating how many seconds remain until the next allowed call.
Common Errors:
- "Intervalo mínimo de 15 minutos não respeitado para a operação...": Wait for the specified cooldown period before retrying.
- API authentication errors: Ensure the API key and company ID credentials are correctly set up.
- Network or request failures: Check network connectivity and API availability.
To resolve errors related to credentials, verify that the API key and company ID are valid and have sufficient permissions.
Links and References
- eKyte Official Website
- eKyte API documentation (not publicly linked in code; consult your eKyte account or support for details)