Overview
This node acts as a webhook trigger for CompanyCam events. It listens for various event notifications sent by the CompanyCam API and triggers workflows in n8n when those events occur. This is useful for automating processes based on real-time updates from CompanyCam, such as new photos being added, projects being created or updated, comments being added, tasks completed, and more.
Practical examples include:
- Automatically notifying a team chat when a new photo is added to a project.
- Triggering follow-up tasks when a ToDo list is completed.
- Syncing project updates with other project management tools.
- Archiving documents or comments as they are created.
Properties
| Name | Meaning |
|---|---|
| Events | Select one or multiple CompanyCam event types to listen for. Options include: |
- All (*) |
|
- Photo Added (photo.created) |
|
- Photo Deleted (photo.deleted) |
|
- Project Created (project.created) |
|
- Project Updated (project.updated) |
|
- Project Label Created (project.label_added) |
|
- Project Deleted (project.deleted) |
|
- Comment Added (comment.created) |
|
- Photo Tag Added (photo.tag_added) |
|
- ToDo List Created (todo_list.created) |
|
- ToDo List Completed (todo_list.completed) |
|
- ToDo List Deleted (todo_list.deleted) |
|
- Task Completed (task.completed) |
|
- Document Added (document.created) |
|
| Filters | Optional filters to narrow down events, currently supports filtering by Project ID (string). |
Output
The node outputs JSON data representing the payload received from the CompanyCam webhook for the triggered event(s). The structure of this JSON depends on the specific event type but generally includes details about the entity involved (e.g., photo, project, comment) and metadata related to the event.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication credential for CompanyCam to register and validate the webhook.
- Needs to be configured with a publicly accessible webhook URL so that CompanyCam can send event notifications.
- No additional external dependencies beyond the CompanyCam API and n8n's webhook infrastructure.
Troubleshooting
- Webhook not triggering: Ensure the webhook URL is correctly set up and publicly accessible. Verify that the CompanyCam API credentials are valid and that the webhook is registered properly in CompanyCam.
- No data received: Confirm that the selected events match those being generated in CompanyCam. If filtering by Project ID, ensure the correct ID is used.
- Duplicate or missing events: Check CompanyCam webhook delivery logs for errors or retries. Network issues may cause missed or repeated webhook calls.
- Error messages related to credentials: Make sure the API key or token provided has sufficient permissions to access webhook features.