Overview
This node acts as a comprehensive connector to the Fenergo API ecosystem, enabling users to interact with a wide range of Fenergo services and domains. It supports numerous domains such as Association Commands, Audit Queries, Authorization Commands, Bulk Load Commands, Business Metrics, Collateral Management, Configuration Exchange, Credit Assessment, Credit Screening, Document Management, Entity Data, Event Ingress, External Authentication, Financial Analysis, Identity Self-Service, Journey Management, Localisation, Lookup, Narrative, New Request, Outreach, Policy, Portal Tenant, Product, Reporting, Review, Risk, Screening, and more.
The node dynamically routes requests based on the selected domain and operation, allowing users to perform actions like creating, updating, deleting, querying, and managing various entities and configurations within the Fenergo platform.
Common scenarios:
- Automating entity association verification and management.
- Retrieving audit logs and reports for compliance.
- Managing user roles, access layers, and authorization.
- Handling bulk data migration and configuration exchange.
- Performing credit assessments and screenings.
- Managing documents, narratives, and product lifecycles.
- Executing journey workflows and logic engine evaluations.
- Integrating external data providers and adapters.
Practical examples:
- Verifying all associations in a client onboarding journey.
- Creating a new deal draft and uploading related documents.
- Fetching audit events for specific resources to monitor changes.
- Updating access layer configurations for user permissions.
- Running credit screening checks via integrated providers.
- Generating financial analysis reports for regulatory compliance.
Properties
| Name | Meaning |
|---|---|
| Domain | The Fenergo API domain to interact with. Options include a wide variety of Fenergo service 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, etc. |
| Endpoint | The specific operation or action to execute within the selected domain. The available operations depend on the chosen domain and cover CRUD operations, queries, batch processes, and specialized commands relevant to that domain. |
| Various other input properties | Depending on the selected Domain and Endpoint, additional required or optional parameters are presented, such as IDs (entityId, journeyId, taskId), JSON request bodies, pagination tokens, filters, and other domain-specific inputs. These inputs allow detailed control over the API calls made by the node. |
Note: The full list of properties is extensive and dynamically changes based on the selected Domain and Endpoint. Each property includes descriptions and display options to guide the user.
Output
The node outputs the response from the invoked Fenergo API call. The output is structured as JSON data representing the result of the requested operation. This can include:
- Entity details (e.g., associations, deals, products).
- Audit event records.
- Configuration and policy data.
- Reports and metrics.
- Status messages and operation results.
If the API returns binary data (e.g., files or signed URLs for uploads/downloads), the node will provide this accordingly, typically as part of the JSON response or as binary attachments.
Dependencies
- Requires an API key credential for authentication with the Fenergo APIs.
- Network connectivity to Fenergo endpoints.
- Proper configuration of credentials in n8n to enable token generation and API access.
- The node internally manages OAuth token retrieval and caching for API authentication.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly configured with valid client ID, secret, and tenant information.
- Timeouts or network issues: Verify network access to Fenergo endpoints and check proxy/firewall settings.
- Invalid input parameters: Confirm that required fields for the selected Domain and Endpoint are provided and correctly formatted.
- API errors: Review error messages returned by the Fenergo API for guidance; these may indicate permission issues, invalid data, or service unavailability.
- Token expiration: The node automatically refreshes tokens, but if persistent authentication failures occur, recheck credential validity.
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.