Digitalsac Izing ProInstall

Overview

This node integrates with the Digitalsac API to perform various operations related to customer service automation and scheduling. Specifically, for the operation "Gerar Link do Calendário (.ics)" (Generate Calendar Link), it generates a calendar link (.ics file) for a given appointment ID. This can be useful in scenarios where you want to provide users or customers with a downloadable calendar event link for their scheduled appointments, enabling easy import into calendar applications like Google Calendar, Outlook, or Apple Calendar.

Practical examples include:

• Sending a calendar invite link to a client after booking an appointment.
• Automating calendar event generation within a workflow that manages schedules.
• Integrating appointment reminders with calendar apps by providing .ics links.

Properties

Output

The node outputs JSON data containing the response from the Digitalsac API for the requested operation. For the "Gerar Link do Calendário (.ics)" operation, the output JSON will typically include the generated calendar link or relevant metadata about the .ics file.

No binary data output is indicated for this operation; the response is handled as JSON.

Example output structure (conceptual):

{
  "calendarLink": "https://example.com/path/to/generated-calendar.ics",
  "scheduleId": 123,
  "status": "success"
}

Dependencies

• Requires an active connection to the Digitalsac API.
• Needs an API authentication token credential configured in n8n to authorize requests.
• The base URL and token for the Digitalsac API must be set up in the node credentials.
• The node uses HTTP requests to communicate with the Digitalsac API endpoints.

Troubleshooting

• Invalid JSON format errors: Some operations require JSON input parameters. If the JSON is malformed, the node throws an error like "Formato de JSON inválido para Dados (JSON)". Ensure all JSON inputs are correctly formatted.
• Missing required parameters: For this operation, ensure the "ID do Agendamento" property is provided and valid.
• API authentication errors: If the API token is missing or invalid, requests will fail. Verify the API key credential configuration.
• Network or API errors: The node captures HTTP errors and returns them in the output JSON under an error field. Check the error message for details.
• Empty or incorrect appointment ID: If the appointment ID does not exist or is incorrect, the API may return an error or empty result.

Links and References

• Digitalsac API Documentation (Assumed official API docs, replace with actual if available)
• iCalendar Format Specification (.ics)
• n8n HTTP Request Node Documentation (for understanding how HTTP requests work in n8n)

If you need summaries for other operations or resources, please provide their names or additional input properties.