Actions14
Overview
This node integrates with an external appointment management API to perform various operations related to appointments, clients, and financial accounts. Specifically for the Agendamento (Appointment) - Get By ID operation, it retrieves detailed information about a single appointment by its unique identifier.
Common scenarios where this node is beneficial include:
- Fetching appointment details to display or process in workflows.
- Integrating appointment data into other systems or automations.
- Validating or auditing appointment information before further actions.
Practical example:
- A workflow that triggers when a new appointment is created elsewhere and uses this node to fetch full appointment details by ID to send confirmation emails or update calendars.
Properties
| Name | Meaning |
|---|---|
| Appointment ID | The unique numeric identifier of the appointment to retrieve. |
Output
The node outputs a JSON object representing the appointment data retrieved from the API. This typically includes fields such as:
id: Appointment unique identifier.title: Title of the appointment.description: Optional description text.startTime: Start date and time of the appointment.endTime: End date and time of the appointment.status: Current status (e.g., agendado, confirmado, concluido, cancelado).priority: Priority level (normal, alta, baixa).clientId: Optional associated client ID.consultationPrice: Optional price of the consultation.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external appointment management API.
- The node expects the API base URL and API key to be configured in the credentials.
- Network access to the API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Appointment ID parameter will cause errors.
- Incorrect or expired API key will result in authentication failures.
- Network connectivity problems can prevent successful API calls.
- Requesting an appointment ID that does not exist returns an error or empty response.
Error messages:
"Unknown operation: appointment.get": Indicates the operation name was not recognized; ensure "Get By ID" is selected.- HTTP 401 Unauthorized: Check API key validity and permissions.
- HTTP 404 Not Found: The specified appointment ID does not exist.
- Network timeout or connection errors: Verify network and API availability.
To resolve errors, verify input parameters, check API credentials, and ensure the API service is reachable.
Links and References
- No direct links provided in the source code.
- Refer to the external appointment API documentation for detailed field definitions and API usage.
- n8n documentation on creating custom nodes may help understand node configuration and usage.