Actions68
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Workspace Actions
Overview
This node integrates with the Magnet Customer API, enabling users to manage various CRM-related resources such as customers, deals, tasks, organizations, and workspaces. Specifically, for the Workspace - Update operation, it allows updating details of an existing workspace by specifying its ID and new properties.
Common scenarios where this node is beneficial include automating updates to workspace information in a CRM system when triggered by external events or workflows, such as renaming a workspace, correcting details, or syncing data from other systems.
Practical example: Automatically update a workspace's name based on changes in an external project management tool, ensuring consistent naming conventions across platforms.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use with the API. Options: "API Token", "OAuth2". |
| Workspace ID | The unique identifier of the workspace to update. This is required to specify which workspace to modify. |
| Name | The new name to assign to the workspace. Optional; if provided, updates the workspace's name. |
Note: There are several hidden properties related to "Life Cycle" and "Source" in the provided JSON, but they appear duplicated and are not relevant to the Workspace resource or Update operation specifically.
Output
The node outputs JSON data representing the updated workspace object returned from the Magnet Customer API after the update operation completes successfully. This typically includes fields such as workspace ID, name, and other metadata reflecting the current state of the workspace.
No binary data output is indicated for this operation.
Dependencies
- Requires access to the Magnet Customer API.
- Requires user to provide valid authentication credentials, either via an API token or OAuth2.
- The node depends on n8n's credential system to securely store and use these credentials.
- No additional environment variables or external services beyond the Magnet Customer API are needed.
Troubleshooting
Common issues:
- Invalid or missing Workspace ID will cause the update to fail because the API cannot identify which workspace to update.
- Incorrect authentication credentials (expired token, invalid OAuth2 setup) will result in authorization errors.
- Providing invalid or unsupported property values (e.g., empty name string) may cause the API to reject the request.
Error messages:
"error": "Workspace not found"— Check that the Workspace ID is correct and exists."error": "Unauthorized"or"Authentication failed"— Verify API token or OAuth2 credentials."error": "Invalid input"— Ensure all required fields are correctly formatted and valid.
Resolution tips:
- Double-check the Workspace ID parameter.
- Re-authenticate or refresh credentials if authorization errors occur.
- Validate input data before sending the update request.
Links and References
- Magnet Customer API Documentation (hypothetical link as actual URL is not provided)
- n8n documentation on Creating Custom Nodes
- OAuth2 and API Token authentication best practices in n8n: Authentication Credentials