Gestor Clientes Max icon

Gestor Clientes Max

Integração completa com API de agenda para gerenciar clientes e agendamentos
Join our community

Actions14

Overview

This node provides a complete integration with the Gestor Clientes Max API, enabling management of clients, appointments, and financial accounts. Specifically for the Finanças (Financial) resource with the Get By ID operation, it retrieves detailed information about a specific financial account by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching details of a particular financial account to display or process in workflows.
  • Integrating financial account data into other systems or reports.
  • Automating financial tracking and reconciliation tasks by retrieving up-to-date account info.

Practical example:

  • A user wants to automatically fetch the status and details of a specific payable or receivable account by its ID to trigger notifications or update dashboards.

Properties

Name Meaning
Financial Account ID The unique numeric identifier of the financial account to retrieve.

Output

The node outputs a JSON object representing the financial account retrieved from the API. This includes all relevant fields such as type (receivable/payable), description, amount, due date, category, status, associated client or appointment IDs, payment method, and any notes.

No binary data output is produced by this operation.

Example output structure (fields may vary):

{
  "id": 123,
  "type": "receivable",
  "description": "Consulting fee",
  "amount": "150.00",
  "dueDate": "2024-06-30",
  "category": "Services",
  "status": "pending",
  "clientId": 456,
  "appointmentId": 789,
  "paymentMethod": "pix",
  "notes": "Payment expected by end of month"
}

Dependencies

  • Requires an API key credential for authenticating with the Gestor Clientes Max API.
  • The node uses HTTP requests to the API base URL configured in the credentials.
  • Proper network connectivity to the Gestor Clientes Max API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Financial Account ID will cause the API request to fail.
    • Incorrect or expired API key credential will result in authentication errors.
    • Network issues or incorrect API base URL configuration can cause connection failures.

  • Error messages:

    • "Unknown operation: financial.get": Indicates an unsupported operation was requested; verify the operation name.
    • HTTP 401 Unauthorized: Check that the API key credential is valid and has proper permissions.
    • HTTP 404 Not Found: The specified Financial Account ID does not exist; verify the ID.
    • JSON parsing errors: Ensure the API response is valid JSON and the API is reachable.

  • Resolution tips:

    • Double-check the Financial Account ID input.
    • Verify API key validity and permissions.
    • Confirm API base URL and network access.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion