Tracker icon

Tracker

Ping Tracker endpoint
Join our community

Actions4

Overview

The Tracker node allows you to interact with a "Tracker" API endpoint by performing various HTTP operations. In the context of the By Name resource and the Get operation, this node is used to retrieve information about a specific entity identified by its name. This is useful in scenarios where you need to fetch details for a particular item or record from the Tracker system using its unique name.

Practical Example:
You might use this node in an n8n workflow to look up user profiles, device statuses, or other resources managed by the Tracker API, simply by specifying their name.

Properties

Name Meaning
Name The unique identifier (name) of the resource you want to retrieve. Used as /get/<name> in the API request.

Output

  • The output will be a JSON object containing the data returned by the Tracker API for the specified name.
  • The structure of the output depends on the API's response for the /get/<name> endpoint.
  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to the Tracker API.
  • Credentials: You must configure trackerApi credentials in n8n, including the domain property (used as the base URL).
  • n8n Configuration: Ensure that the credential named trackerApi is set up with the correct domain and any required authentication details.

Troubleshooting

  • Missing Credentials:
    Error: "No credentials found for 'trackerApi'."
    Resolution: Set up the required credentials in n8n under the name trackerApi.

  • Invalid Domain:
    Error: "Cannot reach Tracker API endpoint."
    Resolution: Check that the domain field in your credentials is correct and reachable.

  • Resource Not Found:
    Error: "404 Not Found" or similar message from the API.
    Resolution: Verify that the value provided in the Name property matches an existing resource in the Tracker system.

Links and References

Discussion