Actions5
Overview
This node interacts with the OpenRegister API to fetch detailed information about companies. Specifically, the "Get Company Financials" operation retrieves financial data for a specified company by its unique ID. This is useful for scenarios where users need to analyze or integrate company financial metrics into workflows, such as credit risk assessment, investment analysis, or business intelligence reporting.
For example, a user might input a company ID to obtain its latest financial statements and then use that data to trigger alerts if certain financial thresholds are met.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company whose financial data you want to retrieve. |
Output
The output JSON contains the financial information of the specified company as returned by the OpenRegister API endpoint /v1/company/{companyId}/financials. The exact structure depends on the API response but typically includes fields such as revenue, profit, assets, liabilities, and other financial metrics.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential to authenticate requests against the OpenRegister API.
- The base URL for the API is configured via credentials.
- Network access to the OpenRegister API endpoints is necessary.
Troubleshooting
- Invalid Company ID: If the provided company ID does not exist or is malformed, the API may return an error or empty result. Verify the company ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up in n8n.
- Network Issues: Connectivity problems can lead to request timeouts or failures. Check network settings and API availability.
- Unexpected Response Structure: If the API changes its response format, downstream processing might fail. Review the API documentation and update workflows accordingly.
Links and References
- OpenRegister API Documentation (for detailed API usage and response formats)