Nestr Trigger
Overview
This node acts as a trigger for workflows based on various events occurring within a specified workspace in the Nestr collaboration platform. It listens for changes such as creation, deletion, or updates of circles, posts, projects, and roles. When one of these events happens, the node activates the workflow, allowing users to automate responses like notifications, data synchronization, or analytics.
Common scenarios include:
- Automatically notifying team members when a new project is created.
- Logging updates to roles or circles for audit purposes.
- Triggering follow-up tasks when posts are updated or deleted.
For example, a user could set this node to trigger whenever a "Project Created" event occurs in their workspace, then automatically send a welcome message or create related tasks in another system.
Properties
| Name | Meaning |
|---|---|
| Workspace ID | The unique identifier of the workspace to monitor for events. |
| Event | The specific event type to listen for. Options include: |
| - Circle Created: Triggers when a new circle is created | |
| - Circle Deleted: Triggers when a circle is deleted | |
| - Circle Updated: Triggers when a circle is updated | |
| - Post Created: Triggers when a new post is created | |
| - Post Deleted: Triggers when a post is deleted | |
| - Post Updated: Triggers when a post is updated | |
| - Project Created: Triggers when a new project is created | |
| - Project Deleted: Triggers when a project is deleted | |
| - Project Updated: Triggers when a project is updated | |
| - Role Created: Triggers when a new role is created | |
| - Role Deleted: Triggers when a role is deleted | |
| - Role Updated: Triggers when a role is updated | |
| Circle ID | (Optional) Filter events to a specific circle by its ID. |
| Circle Role ID | (Optional) Filter events to a specific circle role by its ID. |
Output
The node outputs JSON data representing the event payload received from Nestr. This data contains detailed information about the triggered event, such as the entity affected (circle, post, project, or role), the type of event (create, update, delete), and associated metadata.
The output is structured as an array of JSON objects, each corresponding to an event instance. There is no binary data output.
Example output structure (simplified):
[
{
"id": "event-id",
"event": "project.create",
"workspaceId": "workspace-id",
"data": {
// event-specific details, e.g., project info
},
"timestamp": "2024-06-01T12:00:00Z"
}
]
Dependencies
- Requires an API authentication token credential to connect securely to the Nestr platform.
- Needs the Nestr base URL environment variable (
NESTR_BASE_URL) if not using the defaulthttps://app.nestr.io. - The node uses webhook infrastructure to receive event notifications from Nestr.
Troubleshooting
- Webhook Creation Failure: If the node fails to create the webhook subscription, it will throw an error indicating failure to create the webhook. Ensure that the provided workspace ID and event type are valid and that the API credentials have sufficient permissions.
- Event Not Triggering: Verify that the workspace ID matches the intended workspace and that the event filter (including optional circle or circle role IDs) is correctly set.
- Webhook Already Exists: The node checks for existing webhooks before creating new ones. If you experience duplicate triggers, check your Nestr webhook subscriptions and remove duplicates manually.
- Network or Authentication Issues: Confirm that the API key or OAuth2 token is valid and that the n8n instance can reach the Nestr API endpoint.
Links and References
- Nestr Help Documentation
- Nestr API Webhooks documentation (referenced internally via
/api/webhooksendpoints)