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.
For example, you might use this node to:
- Retrieve the configuration details of a payment gateway integration.
- Access the list of events that an integration can handle.
- Fetch checklist items associated with an integration setup.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the existing integration to fetch. |
| Parâmetros Adicionais | Optional relationships to include in the request. Possible values: Setup Fields, Eventos Disponíveis (Available Events), Checklist. |
Output
The node outputs JSON data representing the 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 access the external service managing integrations.
- The node depends on an external API endpoint that provides integration details by ID.
Troubleshooting
- Common Issue: Providing an invalid or non-existent integration ID will likely result in an error or empty response. Ensure the ID is correct and exists in the target system.
- Error Messages: Errors related to authentication failure may occur if the API key or credentials are missing or invalid. Verify that the required API authentication is properly set up in n8n.
- Resolution: Double-check input parameters, especially the integration ID and any optional parameters. Confirm network connectivity and API availability.
Links and References
- Refer to the external service's API documentation for detailed information on integration objects and their related entities.
- n8n documentation on how to configure API credentials and use HTTP Request nodes may be helpful for setting up authentication.