Actions52
- Project Actions
- Project Photo Actions
- Project Collaborator Actions
- Project Document Actions
- Project User Actions
- Project Label Actions
- Project Checklist Actions
- User Actions
- Photo Actions
- Tag Actions
- Group Actions
- Other Actions
Overview
The node connects to the CompanyCam API, enabling interaction with various resources related to project management and documentation within CompanyCam. Specifically, for the "Project Document" resource with the "List Project Documents" operation, it retrieves a list of documents associated with projects. This is useful for automating workflows that require access to project-related files, such as generating reports, syncing documents to other platforms, or triggering actions based on document updates.
Practical examples include:
- Automatically fetching all documents from a specific project to back them up.
- Integrating project documents into a content management system.
- Monitoring new document uploads to trigger notifications or further processing.
Properties
| Name | Meaning |
|---|---|
| Sorry, we haven't built this part yet. | Notice indicating that this part of the node's functionality is not yet implemented. |
| This node was funded by a company only for specific functionality. We added all of the functions to show what is possible with the CompanyCam API. If you want extra functionality, feel free to reach out to us or submit a PR on the GitHub repo. | Informational notice about the funding and development status of the node, encouraging contributions for additional features. |
| liam@mcgarrigle.co | Contact email provided in the notice. |
Note: The provided properties are notices rather than actionable input parameters for the "List Project Documents" operation, indicating that this part of the node might be incomplete or under development.
Output
The node outputs JSON data representing the list of project documents retrieved from the CompanyCam API. Each item in the output typically contains metadata about a project document, such as its ID, name, URL, creation date, and possibly other relevant attributes depending on the API response.
If binary data (e.g., actual document files) were supported, it would be included in a binary field; however, based on the current code and notices, this functionality appears not to be implemented yet.
Dependencies
- Requires an API key credential for authenticating requests to the CompanyCam API.
- The base URL for API requests is
https://api.companycam.com/v2. - No additional external dependencies are indicated in the provided source code.
Troubleshooting
- Incomplete Functionality: The notices suggest that the "List Project Documents" operation may not be fully implemented. Users might encounter errors or empty results when attempting to use this operation.
- Authentication Errors: Ensure that a valid API key credential is configured in n8n for the CompanyCam node to authenticate successfully.
- API Rate Limits or Permissions: If the API returns errors related to permissions or rate limits, verify that the API key has appropriate access rights and that usage limits have not been exceeded.
Links and References
- CompanyCam API Documentation (general reference for available endpoints and data structures)
- n8n Community Forums for support and discussions about custom nodes and integrations
- GitHub repository for the node (not provided but suggested by the notice for submitting pull requests)