Actions5
Overview
This node integrates with the Medullar platform, specifically managing "Spaces" — collaborative or organizational units within Medullar. The Delete Space operation allows users to remove a selected Space from their Medullar account.
Typical use cases include:
- Automating cleanup of unused or obsolete Spaces.
- Managing workspace lifecycle in response to project completion.
- Integrating with other workflows that require dynamic creation and deletion of collaboration spaces.
For example, after archiving data related to a project, you might use this node to delete the associated Space automatically.
Properties
| Name | Meaning |
|---|---|
| Space Name or ID | Select one of your existing Spaces to delete. You can choose from a dynamically loaded list of your Spaces or specify an ID using an expression. |
Output
The output is a JSON array where each item corresponds to the result of the delete operation for each input item processed. The structure typically contains confirmation details returned by the Medullar API upon successful deletion of a Space. The exact fields depend on the API response but generally confirm the deletion status.
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 uses internal helper functions to fetch user information and perform authenticated API requests.
- The
spaceIdmust correspond to a valid Space accessible by the authenticated user.
Troubleshooting
Common issues:
- Attempting to delete a Space that does not exist or to which the user lacks permission will likely cause an error.
- Providing an invalid or empty Space ID will prevent the operation from succeeding.
- Network or authentication failures may interrupt the API request.
Error messages:
- Errors thrown during deletion are propagated as node operation errors with messages indicating failure reasons (e.g., "Ask Space failed" pattern is used elsewhere; similar patterns apply here).
- If the node is set to continue on fail, errors for individual items are returned in the output JSON under an
errorfield.
Resolution tips:
- Verify the Space ID or select a valid Space from the dropdown.
- Ensure the API key credential is correctly configured and has sufficient permissions.
- Check network connectivity and Medullar service status.
Links and References
- Medullar API Documentation (hypothetical link)
- n8n Expressions Documentation – for using expressions to specify Space IDs dynamically