Actions8
Overview
This node integrates with the TRBO API to manage links associated with user profiles. Specifically, the "Update Link" operation allows users to modify an existing link's properties such as its alias, URL, and visibility settings. This is useful in scenarios where you need to keep your profile links up-to-date or change their accessibility without creating new links.
Practical examples include:
- Updating a promotional URL when a campaign changes.
- Changing the alias of a link to improve readability or branding.
- Adjusting link visibility (public, hidden, unsearchable) based on privacy requirements.
Properties
| Name | Meaning |
|---|---|
| Link ID | The unique identifier of the link to update. |
| Alias | A custom name or label for the link. |
| URL | The destination URL that the link points to. |
| Public | Whether the link is publicly accessible (true or false). |
| Hidden | Whether the link is hidden from certain views or listings (true or false). |
| Unsearchable | Whether the link should be excluded from search results (true or false). |
Output
The node outputs JSON data representing the updated link object returned by the TRBO API after a successful update operation. This typically includes the link's ID, alias, URL, metadata (such as public, hidden, unsearchable flags), and possibly timestamps or other related information.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the TRBO API.
- The node sends HTTP requests to the base URL:
https://trbo.link/api. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Link ID will result in errors indicating the link could not be found.
- Omitting required fields or providing empty strings for mandatory parameters may cause the API to reject the request.
- Network connectivity issues can prevent communication with the TRBO API.
Error Messages:
- 404 Not Found: The specified Link ID does not exist. Verify the Link ID is correct.
- 401 Unauthorized: Authentication failed. Check that the API key credential is valid and properly configured.
- 400 Bad Request: Invalid input data, such as malformed URL or unsupported characters in alias. Review input values.
Resolution Tips:
- Double-check the Link ID and ensure it exists in your TRBO profile.
- Confirm that the API key credential is active and has the necessary permissions.
- Validate all input fields before executing the node.
Links and References
- TRBO API Documentation (for detailed API endpoints and payload structures)
- n8n Documentation on HTTP Request Node (conceptual reference for API interactions)