Actions5
Overview
This node interacts with Medullar Spaces, which are collaborative or organizational units within the Medullar AI-powered discovery and insight platform. Specifically, the "Rename Space" operation allows users to rename an existing Space by specifying its current identifier and a new name.
Common scenarios for this node include:
- Organizing and managing multiple Spaces by updating their names to reflect changes in projects, teams, or purposes.
- Automating renaming workflows when Spaces need to be rebranded or standardized across an organization.
- Integrating with other systems where Space names must be synchronized or updated dynamically.
For example, a user might use this node to rename a Space from "Project Alpha" to "Project Beta" after a project pivot, ensuring all collaborators see the updated name.
Properties
| Name | Meaning |
|---|---|
| Space Name or ID | Select one of your existing Spaces to rename. You can choose from a dropdown list of your Spaces or specify a Space ID using an expression. |
| New Space Name | The new name you want to assign to the selected Space. |
Output
The output is a JSON array containing the updated Space object returned from the Medullar API after the rename operation. This typically includes details such as the Space's unique identifier, the new name, and possibly other metadata about the Space.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Medullar API via an API key credential configured in n8n.
- The node depends on the Medullar API endpoints for Spaces, specifically the PATCH method on
/spaces/{spaceId}/. - The node uses internal helper functions to fetch user information and perform authenticated API requests.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Space ID will cause the API request to fail.
- Insufficient permissions or an invalid API key may result in authorization errors.
- Network connectivity problems can prevent successful communication with the Medullar API.
Error messages:
- Errors thrown during the rename operation will propagate as node execution errors with messages indicating the failure reason.
- If the node is set to continue on failure, error details will be included in the output JSON under an
errorfield.
Resolutions:
- Verify that the Space ID is correct and corresponds to a Space accessible by the authenticated user.
- Ensure the API key credential is valid and has necessary permissions.
- Check network connectivity and retry if transient issues occur.
Links and References
- Medullar API Documentation (hypothetical link)
- n8n Expressions Documentation – for using expressions to specify Space IDs dynamically