Actions46
- Calendar Actions
- ClientProfile Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Status Actions
- Task Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node integrates with the Scoro API, allowing users to interact with various Scoro resources such as triggers, tasks, projects, and more. Specifically, the "Trigger" resource with the "Get" operation enables retrieving details of a specific trigger by its ID or from a selectable list. This is useful for workflows that need to fetch and process trigger configurations or metadata from Scoro.
Practical examples include:
- Automatically fetching trigger details to conditionally branch workflow logic.
- Using trigger data to synchronize or audit automation setups in Scoro.
- Integrating trigger information into reports or notifications.
Properties
| Name | Meaning |
|---|---|
| Trigger | Select a trigger either from a searchable list of available triggers or by entering its numeric ID manually. |
The "Trigger" property supports two modes:
- From List: Search and select a trigger from existing triggers retrieved via the API.
- By ID: Enter a numeric trigger ID directly (must be numeric).
Output
The node outputs JSON data representing the details of the requested trigger. The structure typically includes all relevant fields returned by the Scoro API for a trigger entity, such as its ID, name, conditions, actions, and other configuration details.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Scoro API.
- Needs the base URL and company account ID configured in the credentials.
- The node uses the Scoro API endpoints to fetch trigger data.
- No additional external dependencies beyond the Scoro API and n8n's credential system.
Troubleshooting
- Error: Operation not supported — This occurs if an unsupported operation-resource combination is selected. Ensure "Get" operation is chosen with the "Trigger" resource.
- Invalid Trigger ID — If entering the ID manually, it must be numeric; otherwise, validation will fail.
- Authentication errors — Verify that the API key and other credential details are correct and have sufficient permissions.
- Empty or no results when selecting from list — Check network connectivity and API access rights; also ensure there are triggers configured in the Scoro account.
Links and References
- Scoro API Documentation
- n8n documentation on Creating Custom Nodes