Actions120
- Authentication Actions
- Bloqueios Actions
- Get Motivos
- Get Bloqueio Faturamento
- Get Bloqueio Conta
- Get Bloqueio Carteira
- Get Bloqueio Compra Pedido
- Get Bloqueio Cotacao Compra
- Get Bloqueio Data Minima Vencimento
- Get Bloqueio Estoque Negativo
- Get Bloqueio Financiamento Pedido
- Get Bloqueio Frete Pago
- Get Bloqueio Limite Credito
- Get Bloqueio Limite Individual
- Get Bloqueio Manutencao Preventiva
- Get Bloqueio Margem
- Get Bloqueio Mes Reajuste
- Get Bloqueio Parcela Minima
- Get Bloqueio Saldo Atrasado
- Desaprovar Bloqueio
- Liberar Bloqueio
- Liberar Bloqueio Limite Credito
- Liberar Bloqueio Limite Individual
- Classificacao Actions
- Cliente Actions
- Instituição Financeira Actions
- Linha de Crédito Actions
- Máquina Actions
- Mecânico Actions
- Motorista Actions
- Negócio Actions
- Nota Fiscal Actions
- Oficina Actions
- Orçamento Actions
- Orçamento Balcão Actions
- Ordem de Serviço Actions
- Criar Ordem de Serviço Completa
- Consultar por ID
- Consultar por Código Externo
- Listar Agendamentos
- Listar Agendamentos por ID
- Listar Status do Lock
- Listar Ordens de Serviço
- Incluir Ordem de Serviço
- Listar Ordens de Serviço Geral
- Incluir Apontamento
- Incluir Despesa
- Incluir Peça
- Incluir Serviço
- Editar Peça
- Editar Serviço
- Editar Veículo
- Incluir Observação
- Ordem Serviço Tipo Actions
- Pedido Actions
- Política de Prazo Actions
- Política de Preço Actions
- Produto Actions
- Prospect Actions
- Saída Actions
- Serviço Actions
- Status Financiamento Actions
- Título Actions
- Veículo Cliente Actions
- Veículo Próprio Actions
- Vendas Actions
- Vendedor Actions
Mecânico → Get All
AI-generatedOverview
This node integrates with the Nuvem Solution API to perform various operations related to mechanics ("Mecânico" resource). Specifically, the "Get All" operation retrieves a list of mechanics filtered optionally by mechanic ID, company ID, and branch ID. This is useful for workflows that need to fetch mechanic data from an external ERP or workshop management system.
Typical use cases include:
- Listing all mechanics available in a company or branch.
- Filtering mechanics by specific IDs to get detailed information.
- Integrating mechanic data into other business processes such as scheduling, service orders, or reporting.
Example: A user wants to retrieve all mechanics working in a particular branch to assign tasks or generate reports.
Properties
| Name | Meaning |
|---|---|
| Mecanico ID | ID of the mechanic to filter by (optional; if 0 or omitted, no filtering by mechanic) |
| Empresa ID | ID of the company to filter by (optional; if 0 or omitted, no filtering by company) |
| Filial ID | ID of the branch to filter by (optional; if 0 or omitted, no filtering by branch) |
These properties allow users to narrow down the list of mechanics returned by specifying one or more filters.
Output
The output is a JSON array containing mechanic objects retrieved from the Nuvem Solution API endpoint /erp/oficina/mecanicos. Each object represents a mechanic and includes all relevant details as provided by the API.
The exact structure of each mechanic object depends on the API response but typically includes fields like mechanic ID, name, company affiliation, branch, contact info, and other metadata.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Nuvem Solution API.
- The node uses OAuth-like token authentication internally, obtaining and caching an access token.
- The base URL for the API and credentials (software key, secret, user ID, user key) must be configured in the node's credentials.
- Network connectivity to the Nuvem Solution API endpoint is required.
Troubleshooting
- Authentication errors: If the node fails to authenticate, verify that the API credentials (software key, secret, user ID, user key) are correct and have sufficient permissions.
- Empty results: If no mechanics are returned, check that the filter parameters (mechanic ID, company ID, branch ID) are correct and correspond to existing records.
- API errors: The node throws errors if the operation or resource is unsupported or if the API returns an error. Review the error message for details.
- Rate limits or network issues: Ensure stable internet connection and that the API usage limits are not exceeded.
Links and References
- Nuvem Solution API Documentation (generic link, replace with actual docs if available)
- n8n documentation on Creating Custom Nodes
- General REST API integration best practices
This summary is based solely on static analysis of the provided source code and property definitions.