Actions6
Overview
This node integrates with the UK Companies House API to retrieve various types of company information. It supports searching companies by name or fetching detailed data about a specific company using its registration number. Common use cases include verifying company details, obtaining filing histories, listing company officers, and identifying persons with significant control.
Practical examples:
- Searching for companies matching a partial or full name.
- Retrieving a company's official registered office address.
- Fetching the list of current directors or secretaries.
- Accessing detailed filing history filtered by category or type.
- Listing individuals or entities with significant control over a company.
This node is beneficial for business intelligence, compliance checks, due diligence, and data enrichment workflows.
Properties
| Name | Meaning |
|---|---|
| Company Name or Number | Company name (for search operation) or company registration number (for other operations). |
Note: The node also supports an "Operation" property with these options (not listed here as per user request to focus on Default resource and operation):
- Get Company Profile
- Get Filing History
- Get Officers
- Get Persons with Significant Control
- Get Registered Office Address
- Search Companies
Since the user requested only the Default Resource and Operation, and the provided input properties JSON includes only "companyInput", this table reflects that.
Output
The node outputs JSON data corresponding to the selected operation:
- For search operation: JSON contains search results for companies matching the input name.
- For getProfile: Detailed company profile information.
- For getOfficers: List of company officers; optionally filtered to active officers only.
- For getFilingHistory: Company filing history, which can be further filtered locally by filing type code and description.
- For getAddress: Official registered office address of the company.
- For getPsc: List of persons with significant control over the company.
If the operation is "getFilingHistory", the node applies additional local filters on the returned items array based on filing type and description, modifying the output accordingly.
The output JSON structure directly reflects the API response from Companies House, wrapped inside an object under the json key.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the UK Companies House API.
- The node uses HTTP GET requests to the Companies House REST API endpoints.
- Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an invalid company number or name may result in empty or error responses.
- Using unsupported operations or malformed inputs will throw errors.
Error messages:
"Unknown operation: <operation>": Indicates an unsupported operation was specified. Verify the operation parameter.- HTTP errors from the API (e.g., 404 Not Found, 401 Unauthorized) will be surfaced as node errors.
Resolution tips:
- Ensure the API key credential is correctly set up and has access rights.
- Double-check the company number or name input for correctness.
- Use the "continue on fail" option to handle errors gracefully within workflows.