Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Actions68

Overview

The node integrates with the Magnet Customer API to perform various operations on different resources, including tasks. Specifically, for the Task resource and the Get Many operation, it retrieves multiple task records from the Magnet Customer system.

This node is useful when you want to fetch a list of tasks for further processing or automation within your workflows. For example, you might use it to:

  • Retrieve all open tasks assigned to a team.
  • Fetch tasks for reporting or analytics.
  • Synchronize tasks between Magnet Customer and another system.

Properties

Name Meaning
Authentication Method of authentication to use: either "API Token" or "OAuth2".
Page The page number of results to retrieve (pagination).
Limit Maximum number of task results to return; minimum value is 15.
Source Hidden property set to "n8n", indicating the source of the contact/task data.
Life Cycle Hidden property indicating the life cycle stage of the contact (e.g., lead, prospect).

Note: The properties Source and Life Cycle are hidden and preset internally, likely used for filtering or tagging contacts/tasks in the API requests.

Output

The node outputs an array of JSON objects representing the retrieved tasks. Each object corresponds to a single task record as returned by the Magnet Customer API.

  • The output JSON contains all fields provided by the API for each task.
  • No binary data output is indicated for this operation.

Example output structure (simplified):

[
  {
    "_id": "task_id_123",
    "name": "Follow up with client",
    "status": "open",
    "assignedTo": "staff_id_456",
    "dueDate": "2024-07-01T12:00:00Z",
    ...
  },
  ...
]

Dependencies

  • Requires connection to the Magnet Customer API.
  • Supports two authentication methods:
    • An API token credential.
    • OAuth2 credential.
  • The user must configure appropriate credentials in n8n before using the node.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Requesting pages or limits outside allowed ranges may result in empty responses or errors.
    • Network connectivity issues can prevent API calls.

  • Error messages:

    • Errors thrown by the API (e.g., unauthorized, rate limit exceeded) will be surfaced.
    • If "Continue On Fail" is enabled, errors for individual items will be included in the output with an error field.

  • Resolutions:

    • Verify that the API token or OAuth2 credentials are valid and have necessary permissions.
    • Adjust pagination parameters (Page, Limit) to valid values.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion