Actions42
- Condomínio Actions
- Plano de Contas Actions
- Conta Bancária Actions
- Movimentação Bancária Actions
- Unidade Actions
- Morador Actions
- Boleto Actions
- Recebimento Actions
- Fornecedor Actions
- Inadimplência Actions
- Segunda Via Actions
- Responsáveis Legais Actions
Overview
This node integrates with the Superlogica API, specifically allowing users to interact with various resources related to condominium management. For the "Fornecedor" (Supplier) resource, the "Obter Fornecedor" (Get Supplier) operation retrieves detailed information about a specific supplier by its ID. This is useful in scenarios where you need to fetch supplier data for reporting, updating records, or integrating supplier details into other workflows.
Practical examples include:
- Automatically retrieving supplier details when processing invoices.
- Synchronizing supplier information between Superlogica and another system.
- Validating supplier data before performing further operations.
Properties
| Name | Meaning |
|---|---|
| ID do Fornecedor | The unique identifier of the supplier to retrieve. This is a required string input. |
Output
The output is a JSON object containing the detailed data of the requested supplier as returned by the Superlogica API. The structure depends on the API response but typically includes fields such as supplier name, contact information, address, and other relevant supplier attributes.
No binary data output is indicated for this operation.
Example output snippet (conceptual):
{
"id": "123",
"name": "Supplier Name",
"contact": {
"email": "supplier@example.com",
"phone": "123456789"
},
"address": {
"street": "Rua Exemplo",
"city": "São Paulo",
"state": "SP",
"zip": "01234-567"
}
}
Dependencies
- Requires an API key credential for Superlogica API authentication.
- The node uses the Superlogica API endpoint, defaulting to
https://api.superlogica.net/v2/condorif not specified in credentials. - Proper configuration of the API token and access token is necessary within n8n credentials.
Troubleshooting
- Missing Credentials: If credentials are not provided or invalid, the node will throw an error indicating that credentials are missing.
- Invalid Supplier ID: Providing an incorrect or non-existent supplier ID may result in an error or empty response from the API.
- API Connectivity Issues: Network problems or incorrect API URLs can cause request failures.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning the error message in the output JSON.
To resolve common errors:
- Verify that the API credentials are correctly set up and valid.
- Ensure the supplier ID exists in the Superlogica system.
- Check network connectivity and API endpoint correctness.
Links and References
- Superlogica API Documentation (for detailed API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes