Overview
This node acts as a trigger for workflows based on events occurring in the Runn platform. It monitors specified Runn resources (such as People, Projects, Clients, Assignments, Actuals, Contracts, Users, and Teams) and triggers when selected event types happen to those resources. The supported event types are creation, update, and deletion of resources.
Common scenarios where this node is useful include:
- Automatically starting workflows when new projects or people are added to Runn.
- Triggering notifications or data syncs when assignments or actuals are updated.
- Reacting to deletions of key resources like contracts or projects to maintain data integrity elsewhere.
For example, you could use this node to start a workflow that sends a welcome email whenever a new person is created in Runn, or to update an external CRM system when project details change.
The node works by polling the Runn API at a user-defined interval, checking for changes since the last poll, and emitting matching events into the workflow.
Properties
| Name | Meaning |
|---|---|
| Resources | Select one or more Runn resource types to monitor. Options: People, Projects, Clients, Assignments, Actuals, Contracts, Users, Teams. |
| Events | Select one or more event types to trigger on. Options: Created (new resource), Updated (resource changed), Deleted (resource removed). Deletion events are only supported for some resources and require a LIVE account. |
| Polling Interval | How often (in minutes) the node polls the Runn API for new or updated events. Minimum value is 0.1 minutes. Default is 60 minutes. |
Output
The node outputs JSON objects representing the detected events. Each output item includes:
trigger_resource_type: The type of resource involved (e.g., "people", "projects").trigger_event_type: The event type that triggered the workflow ("created", "updated", or "deleted").trigger_link: A URL linking to the resource in the Runn web app.- Additional fields from the resource or activity log data, such as IDs, timestamps (
createdAt,updatedAt), and other relevant properties depending on the resource.
No binary data is output by this node.
Dependencies
- Requires an active connection to the Runn API via an API authentication credential.
- The node uses polling to detect changes, so it depends on network connectivity and valid API credentials.
- Deletion event detection requires a LIVE Runn account and access to the activity log endpoint.
Troubleshooting
- No events triggering: Ensure that at least one resource and one event type are selected. Also verify that the API credentials are valid and have sufficient permissions.
- Polling interval too short: Setting a very low polling interval may cause rate limiting or performance issues with the Runn API.
- Deletion events not firing: Deletion triggers only work for certain resources and require a LIVE account. If deletions are not detected, confirm these conditions.
- Errors about missing parameters: The node throws errors if no resources or events are selected.
- Network or authentication errors: Check API key validity and network connectivity.
Links and References
- Runn Platform
- Runn API documentation (not linked here; consult your Runn account or developer portal)
- n8n documentation on creating trigger nodes: https://docs.n8n.io/integrations/creating-nodes/trigger-nodes/