Overview
The "Fenergo NAR" node is designed to interact with a wide range of Fenergo Nebula APIs, providing extensive capabilities for managing financial, compliance, and entity data workflows. It supports numerous domains and operations related to associations, audits, authorizations, bulk loads, business metrics, collaterals, configurations, credit assessments, screenings, document management, entity data, journeys, localization, lookups, narratives, outreach, policies, reporting, reviews, risk, screening, and more.
This node is beneficial in scenarios where organizations need to automate and integrate complex regulatory, compliance, and financial processes involving entities, products, deals, documents, and associated metadata. For example, it can be used to verify entity associations, manage credit assessments, handle document uploads and assignments, perform risk evaluations, or retrieve audit logs.
Practical examples include:
- Verifying all associations in a client onboarding journey.
- Creating and updating credit screening requests.
- Managing document requirements and uploading files for compliance.
- Retrieving detailed audit events for specific entities or journeys.
- Executing policy logic engine evaluations for compliance checks.
Properties
| Name | Meaning |
|---|---|
| Domain | The API domain from which to consume the APIs. Options include various Fenergo Nebula API domains such as Association Command v2.0, Audit Query v3.0, Credit Assessment Command v1.0, Document Management Command v2.0, EntityData Command v3.0, Journey Command v1.0, Policy Logic Engine v3.0, Product Command v1.0, Screening Command v2.0, Supergraph, and many others. |
| Endpoint | The specific operation to execute within the selected domain. The available operations depend on the chosen domain and cover actions like Create, Update, Delete, Get, Verify, Search, Submit, Sign, Archive, Evaluate, and more. |
| Various other properties | Depending on the selected Domain and Endpoint, additional input parameters are required, such as IDs (entityId, journeyId, taskId, etc.), JSON request bodies, and other identifiers relevant to the operation. These inputs allow precise control over the API calls made by the node. |
Note: The node dynamically adjusts the visible input properties based on the selected Domain and Endpoint, ensuring users provide only relevant information.
Output
The node outputs the JSON response returned by the invoked Fenergo Nebula API operation. The structure of this output varies widely depending on the Domain and Endpoint selected, reflecting the diverse data models of the underlying APIs. The output typically includes details about entities, associations, audit events, credit assessments, documents, journeys, policies, risks, screenings, and other domain-specific data.
If the operation involves file uploads or downloads, the node may also handle binary data representing files or signed URLs for file access.
Dependencies
- Requires an API key credential for authentication with the Fenergo Nebula platform.
- Network connectivity to Fenergo Nebula API endpoints.
- Proper configuration of credentials in n8n to securely store and use API keys.
- The node relies on multiple internal modules corresponding to each domain's API implementation.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly configured and has the necessary permissions.
- Invalid input parameters: Verify that all required fields for the selected Domain and Endpoint are provided and correctly formatted.
- API endpoint errors: Check the error messages returned by the API for details; these might indicate issues like resource not found, invalid request body, or permission denied.
- Timeouts or network issues: Confirm network connectivity and API availability.
- Unsupported combinations: Selecting incompatible Domain and Endpoint pairs may result in errors; always choose valid combinations as per the node's property options.
Links and References
This summary provides an overview of the node's capabilities, input properties, output structure, dependencies, and troubleshooting tips based on static analysis of the provided source code and property definitions.