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 to manage various CRM-related resources, including workspaces. Specifically, for the Workspace - Create operation, it allows users to create a new workspace within their Magnet Customer account.
Typical use cases include automating the creation of workspaces as part of onboarding processes, organizing projects or teams dynamically based on external triggers, or integrating workspace management into broader workflows.
For example, when a new client signs up in another system, this node can automatically create a corresponding workspace in Magnet Customer to start tracking related activities and data.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "API Token", "OAuth2". |
| Name | The name of the workspace to be created. |
| Life Cycle | (Hidden) The life cycle stage of the contact; preset internally (not user-editable). |
| Source | (Hidden) The source identifier for the contact; preset internally (not user-editable). |
Note: The properties Life Cycle and Source appear multiple times as hidden fields with different default values but are not exposed for user input in this operation.
Output
The node outputs JSON data representing the newly created workspace object returned by the Magnet Customer API. This typically includes details such as the workspace ID, name, creation timestamps, and other metadata defined by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Magnet Customer API.
- Supports two authentication methods:
- An API key credential.
- OAuth2 authentication.
- The user must configure appropriate credentials in n8n for either method before using the node.
Troubleshooting
- Authentication errors: Ensure that the API token or OAuth2 credentials are correctly configured and have sufficient permissions to create workspaces.
- Validation errors: If the workspace name is missing or invalid, the API may reject the request. Always provide a valid non-empty string for the workspace name.
- API connectivity issues: Network problems or incorrect API endpoint configurations can cause failures. Verify network access and API availability.
- Unexpected errors: Enable "Continue On Fail" in the node settings to handle errors gracefully and inspect error messages returned in the output for debugging.