CompanyCam icon

CompanyCam

Node for connecting CompanyCam

Overview

The node connects to the CompanyCam API, specifically providing functionality to list all tags associated with a CompanyCam account. This operation is useful for users who want to retrieve and manage tags used in their projects or photos within CompanyCam. For example, a user might use this node to fetch all tags to display them in a dashboard, filter photos by tags, or synchronize tags with another system.

Properties

Name Meaning
Resource The type of data to interact with; here it should be set to "Tag" to access tag features.
Operation The action to perform on the resource; here it should be "List All Tags" to retrieve tags.

Note: The provided properties JSON contains only notices indicating incomplete parts and does not define specific input parameters for this operation. Typically, listing tags may support pagination or filtering options, but these are not present in the given source.

Output

The output will contain a JSON array of tag objects retrieved from the CompanyCam API. Each tag object typically includes details such as tag ID, name, color, and possibly metadata related to its usage in projects or photos.

If the node supports binary data output (not indicated here), it would represent files or images, but for the "List All Tags" operation, the output is purely JSON data representing tags.

Dependencies

  • Requires an active connection to the CompanyCam API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The base URL for API requests is https://api.companycam.com/v2.
  • No additional external dependencies are indicated.

Troubleshooting

  • Common Issues:
    • Authentication errors if the API key is missing, invalid, or expired.
    • Network connectivity problems preventing access to the CompanyCam API.
    • API rate limits being exceeded, causing request failures.
  • Error Messages:
    • Unauthorized or 401 errors: Check that the API key credential is correctly set up.
    • 404 or resource not found: Verify that the resource and operation names are correct.
    • Timeout or network errors: Ensure stable internet connection and API availability.

Links and References

Discussion