Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Overview

This node integrates with the Magnet Customer API to manage pipelines among other resources. Specifically, the "Pipeline - Create" operation allows users to create a new sales or project pipeline by specifying its title. This is useful in CRM or project management workflows where automating pipeline creation based on triggers or data inputs can streamline sales processes or task tracking.

Practical examples include:

  • Automatically creating a new sales pipeline when a new product line is launched.
  • Generating project pipelines dynamically from form submissions or external systems.

Properties

Name Meaning
Authentication Method of authentication to use: either "API Token" or "OAuth2".
Title The title/name of the pipeline to be created (required string).
Life Cycle Hidden property indicating the life cycle stage of the contact (e.g., customer, lead).
Source Hidden property indicating the source of the contact, defaulting to "n8n".

Note: The "Life Cycle" and "Source" properties are hidden and preset internally for different resource contexts but are not user-configurable in this operation.

Output

The node outputs JSON data representing the newly created pipeline object as returned by the Magnet Customer API. This typically includes fields such as the pipeline's unique ID, title, creation timestamps, and any other metadata provided 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: API token or OAuth2 credentials.
  • The node expects proper configuration of these credentials within n8n.
  • No additional environment variables are explicitly required beyond standard credential setup.

Troubleshooting

  • Common Issues:

    • Authentication failures due to invalid or expired API tokens or OAuth2 tokens.
    • Missing required "Title" property causing validation errors.
    • Network connectivity issues preventing API calls.
  • Error Messages:

    • Errors returned from the API will be surfaced with their message in the output JSON under an error field if "Continue On Fail" is enabled.
    • Typical error messages may include authorization errors ("Unauthorized"), validation errors ("Title is required"), or server errors.
  • Resolutions:

    • Verify that the API token or OAuth2 credentials are correctly configured and valid.
    • Ensure the "Title" field is provided and non-empty.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion