Actions45
- Evento Actions
- Criar Evento De Acesso Concedido
- Criar Evento De Aguardando Pagamento
- Criar Evento De Boleto Impresso
- Criar Evento De Carrinho Abandonado
- Criar Evento De Nota Nps
- Criar Evento De Pacote Aguardando Retirada
- Criar Evento De Pacote Saiu Para Entrega
- Criar Evento De Pedido Cancelado
- Criar Evento De Pedido Despachado
- Criar Evento De Pedido Entregue
- Criar Evento De Pedido Estornado
- Criar Evento De Pedido Pago
- Criar Evento De Pedido Processando
- Criar Evento De Pesquisa Nps
- Criar Evento De Progresso De Envio
- Criar Evento De Redefinicao De Senha
- Gerenciamento Da Conta Actions
- Grupo De Variável Customizada Actions
- Integração Actions
- Lead Actions
- Lista De Lead Actions
- Variável Customizada Actions
Overview
This node is designed to fetch details of a specific integration by its ID. It allows users to retrieve information about an existing integration within a system, optionally including related data such as setup fields, available events, or checklists. This functionality is useful in scenarios where you need to programmatically access integration configurations or metadata for further processing, auditing, or display.
Practical examples include:
- Retrieving the configuration details of a particular integration before updating it.
- Fetching available event types associated with an integration to dynamically build UI elements.
- Accessing checklist items related to an integration for validation or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the existing integration to fetch. |
| Parâmetros Adicionais | Optional relationships to include in the request; options are: Setup Fields, Eventos Disponíveis (Available Events), Checklist. |
Output
The node outputs JSON data representing the fetched integration's details. This includes the core properties of the integration identified by the provided ID. If additional parameters are selected, the output will also contain related data such as setup fields, available events, or checklist items linked to the integration.
No binary data output is indicated.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external service managing integrations.
- The node depends on an external API endpoint that supports fetching integration details by ID and optionally including related entities.
Troubleshooting
- Missing or invalid ID: Ensure the "ID" property is correctly set and corresponds to an existing integration. Errors may occur if the ID is empty or does not exist.
- Unauthorized errors: Verify that the API authentication credentials are properly configured and have sufficient permissions to read integration data.
- Invalid additional parameters: When selecting optional relationships, ensure they are supported by the external API; unsupported options might cause request failures.
- Network issues: Connectivity problems can prevent successful API calls; check network settings and endpoint availability.
Links and References
- Refer to the external service's API documentation for detailed information on integration endpoints and supported query parameters.
- n8n documentation on configuring API credentials and using HTTP Request nodes for custom integrations.