Overview
The "Fenergo APAC" node is designed to interact with a wide range of Fenergo Nebula APIs across various domains and operations. It acts as a comprehensive connector for the Fenergo platform, enabling users to perform numerous actions such as managing entity associations, audits, authorizations, bulk loads, business metrics, collaterals, configurations, credit assessments, screenings, document management, entity data, event ingress, external data, financial analysis, identity self-service, 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 workflows involving regulatory compliance, client onboarding, risk assessment, document handling, and other financial services processes managed by Fenergo's platform. For example, it can be used to verify entity associations, create or update credit assessments, manage document uploads, or retrieve audit logs programmatically within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Domain | The specific Fenergo Nebula API domain to interact with. Options include various command and query APIs like Association Command v2.0, Audit Query v3.0, Authorization Command v1.0, BulkLoad Command v1.0, Business Metrics Command v1.0, Collateral Command v1.0, Configuration Exchange Command v1.0, ConfigBaseline Command v1.0, Covenants & Conditions Command API v1.0, CreditAssessment Command v1.0, CreditScreening Command v1.0, Adapter Receptor v1.0, Dashboards Command v1.0.0, Data Migration Command v1.0/2.0, Data Protection Command v1.0, Deals Command v1.0, Digital IDV Command v1.0, Document Management Command v1.0/2.0, EntityData Command v1.0/2.0/3.0, Event Ingress v1.0, Event Notifications Polling/Webhooks, External Authentication Command v1.0, External Data BFF/Command/Outreach, Financial Analysis Command API v1.0, Identity Self-Service Management Command v1.0, Journey Command v1.0, Journey Logic Engine v1.0/2.0, Localisation Command v1.0, Lookup Command v1.0, Narrative Command v1.0, New Request v1.0, Outreach Command v1.0, Policy Command v1.0, Policy Logic Engine v1.0/2.0/3.0, Portal API v1.0.0.0, Product Command v1.0, Reporting Query v1.0.0, Reports Command v1.0/2.0, Review Command v1.0, Risk Command v1.0, Screening Mock Adapter v1.0, Screening Command v1.0/2.0, Supergraph, etc. |
| Endpoint | The operation to execute within the selected domain. The available operations depend on the chosen domain and include actions like CreateAssociation, VerifyAssociation, DeleteAssociation, UpdateEntity, GetAuditEventsForMultipleResources, CreateJob, CreateDealDraft, CreateUser, GetJourneyInstanceById, CreateLocalisation, CreateLookup, CreateBusinessNarrative, SaveConfiguration, CreateEntity, EvaluateRequirementSets, CreateRiskModel, Screen, CreateBatch, etc. |
| Various other parameters | Depending on the selected domain and endpoint, additional input properties are required, such as IDs (entityId, journeyId, taskId, etc.), JSON request bodies, and other relevant identifiers or data structures needed to perform the operation. These are dynamically shown based on the selected domain and endpoint. |
Output
The node outputs the response from the invoked Fenergo Nebula API call. The output is typically a JSON object containing the result of the requested operation, which may include details about entities, associations, audit events, documents, journeys, policies, reports, or other domain-specific data.
If the operation involves file uploads or downloads, the node may handle binary data accordingly, but this depends on the specific API and operation.
Dependencies
- Requires valid credentials for accessing the Fenergo Nebula APIs, configured in n8n as an API key or OAuth credential.
- Network access to the Fenergo Nebula API endpoints.
- Proper configuration of the node's Domain and Endpoint parameters to match the desired API and operation.
- The node internally manages authentication tokens and handles token refresh as needed.
Troubleshooting
- Invalid Credentials: Ensure that the API key or authentication credentials are correctly set up in n8n.
- Incorrect Domain or Endpoint: Selecting an unsupported combination of domain and endpoint will cause errors. Verify that the chosen operation is valid for the selected domain.
- Missing Required Parameters: Some operations require mandatory fields like IDs or JSON request bodies. Make sure all required inputs are provided.
- API Rate Limits or Timeouts: Network issues or API rate limits might cause failures. Check network connectivity and API usage quotas.
- Unexpected API Errors: Review the error messages returned by the API for clues. Common issues include invalid data formats or unauthorized access.
- Large Payloads: Operations involving large data sets or files may require increased timeout settings or chunked processing.
Links and References
This summary provides an overview of the node's capabilities, input properties, output structure, dependencies, and common troubleshooting tips based on static analysis of the provided property definitions and bundled source code.