Digitalsac Izing ProInstall

Overview

This node integrates with the Digitalsac API, providing a wide range of operations to interact with services such as validating WhatsApp numbers, CPF, dates, managing tickets, sending messages (including media and buttons), handling tags, kanbans, wallets, and scheduling appointments.

The "Listar Serviços" (List Services) operation specifically retrieves a list of available services from the Digitalsac platform. It optionally allows filtering these services by a user ID.

This node is beneficial in scenarios where you want to automate workflows involving customer service management, appointment scheduling, or communication via WhatsApp through the Digitalsac system. For example, you can use it to fetch all services offered by a particular user or globally, then use that data downstream for scheduling or reporting.

Properties

Output

• The output is a JSON array where each item corresponds to the response from the Digitalsac API for the requested operation.
• For the "Listar Serviços" operation, the json field contains the list of services retrieved from the API.
• The structure of each service object depends on the Digitalsac API response but typically includes service identifiers, names, descriptions, and possibly associated user information.
• This node does not output binary data for this operation.

Dependencies

• Requires an API key credential for authenticating with the Digitalsac API.
• The node uses the base URL and token from the configured credentials to make HTTP requests.
• No additional environment variables are required beyond the API credential setup in n8n.

Troubleshooting

• Invalid JSON Format Errors: Several operations expect JSON input in certain parameters (e.g., "Dados (JSON)"). If the JSON is malformed, the node throws an error like "Formato de JSON inválido para Dados (JSON)". To fix this, ensure the JSON syntax is correct before running the node.
• Missing Required Parameters: For some operations (including message sending), the "Parâmetro" field (UUID of the connection) is mandatory. Omitting it results in errors instructing to fill this field.
• Binary Data Requirements: Operations sending media require binary input connected to the node. If missing, errors indicate that a binary file is required.
• API Request Failures: If the API returns an error, the node outputs the error message inside the json.error field. Check the API credentials, network connectivity, and parameter correctness.
• Filtering by User ID: When filtering services by user ID, ensure the ID is valid and exists in the Digitalsac system; otherwise, the result may be empty.

Links and References

• Digitalsac API Documentation (Assumed official API docs, replace with actual if available)
• n8n Documentation: Creating Custom Nodes
• General REST API usage in n8n: HTTP Request Node

If you need details about other operations or resources, feel free to ask!