Actions15
- Assistant Actions
- Assistant Event Actions
- Chat Actions
- Conversation Actions
- Voice Actions
Overview
This node interacts with the Telnyx AI API to retrieve details about a specific assistant event. The "Get" operation under the "Assistant Event" resource fetches information about a scheduled event associated with a particular assistant. This is useful in scenarios where you want to monitor, audit, or manage events triggered or scheduled for an AI assistant, such as checking the status or details of a reminder, notification, or any automated task linked to the assistant.
Practical examples include:
- Retrieving details of a calendar event created by an AI assistant.
- Fetching information about a scheduled notification or alert managed by the assistant.
- Auditing past or upcoming assistant-triggered events for reporting or debugging.
Properties
| Name | Meaning |
|---|---|
| Assistant | The assistant for which to get events. You can select from a list of assistants or provide an ID directly. |
| Event ID | The unique identifier of the event to retrieve. You can select from a list of scheduled events or provide an ID directly. |
Output
The node outputs JSON data representing the details of the requested assistant event. This typically includes all relevant metadata and properties of the event such as its ID, timestamps, status, and any other event-specific information returned by the Telnyx AI API.
If the event contains binary data (not indicated here), it would be included in the binary output field; however, this node primarily deals with JSON event data.
Dependencies
- Requires an active Telnyx AI API key credential configured in n8n.
- The node makes HTTP requests to the Telnyx AI API endpoint
https://api.telnyx.com. - Proper permissions on the API key to access assistant events are necessary.
Troubleshooting
Common issues:
- Invalid or missing assistant or event IDs will cause the API request to fail.
- Network connectivity problems may prevent reaching the Telnyx API.
- Insufficient API permissions can result in authorization errors.
Error messages:
- "Event not found" — Verify that the provided Event ID exists and belongs to the specified assistant.
- "Unauthorized" or "Invalid API key" — Check that the API key credential is correctly set up and has required scopes.
- "Bad Request" — Ensure that the input parameters (assistant and event IDs) are valid and properly formatted.
Resolving these usually involves verifying input values, checking API credentials, and ensuring network connectivity.