Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
The node interacts with the "Company" resource in the Hudu API, specifically performing the "Jump" operation. This operation allows users to jump or link a company record within Hudu to an external integration system by specifying the integration type and identifiers. It is useful for synchronizing or referencing company data across multiple platforms such as Autotask, Office 365, Ninja, Datto, and many others.
Practical scenarios include:
- Linking a company in Hudu to its corresponding record in an external PSA or RMM tool.
- Automating workflows that require cross-referencing company information between Hudu and third-party integrations.
- Enabling seamless navigation or data exchange between Hudu and integrated systems.
Properties
| Name | Meaning |
|---|---|
| Integration Slug | The integration type to use. Options include: Office 365, Autotask, Cw Manage, Bms, Syncro, Domotz, Quickpass, Cloudradial, Auvik, Liongard, Ninja, Dattormm, Atera, Nsight, Halo, Pulseway Rmm, Repairshopr, Datto, Watchman, Mapbox, Openai, Superops, Unifi, Ncentral, Meraki, Addigy, Cloudflare, Level. |
| Additional Fields | Optional additional identifiers for the integration: |
| - Integration ID | The ID of the company in the external integration system. |
| - Integration Identifier | An alternative identifier used if Integration ID is not set. |
Output
The output is a JSON array where each item corresponds to the result of the "Jump" operation for each input item. Each JSON object contains the response data returned from the Hudu API after attempting to perform the jump/link action on the specified company resource.
If the operation fails for any item and "Continue On Fail" is enabled, the output will contain an error message object for that item instead.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for the Hudu API must be set in the node credentials.
- No other external dependencies are required.
Troubleshooting
Common Issues:
- Invalid or missing API key credential can cause authentication failures.
- Incorrect integration slug or unsupported integration type may lead to errors.
- Missing required fields like Integration ID or Integration Identifier when needed.
- Network connectivity issues to the Hudu API endpoint.
Error Messages:
"The resource \"companies\" is not known!"— indicates the resource parameter was incorrect or misspelled.- API errors returned from Hudu will be passed through; check the error message for details.
- If "Continue On Fail" is disabled, the node execution will stop on the first error encountered.
Resolutions:
- Verify API credentials and base URL configuration.
- Ensure the integration slug matches one of the supported options.
- Provide either Integration ID or Integration Identifier as required.
- Check network access and firewall settings.
Links and References
- Hudu API Documentation (for detailed API endpoints and integration info)
- n8n Documentation on Creating Custom Nodes
- General info on PSA and RMM Integrations