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, specifically allowing users to create triggers within their Scoro account. A trigger in Scoro typically automates actions based on certain events or conditions, helping streamline workflows and notifications.
Common scenarios for this node include:
- Automatically creating a trigger that sends notifications when a project status changes.
- Setting up automated reminders or alerts based on time entries or task updates.
- Integrating Scoro triggers into broader automation workflows managed by n8n.
For example, a user might configure this node to create a trigger that activates whenever a new invoice is generated, enabling downstream processes like sending emails or updating other systems.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body used to define the trigger to create. |
The "Request" property expects a JSON structure that matches the Scoro API's requirements for creating a trigger. This allows flexible and detailed configuration of the trigger parameters.
Output
The node outputs JSON data representing the response from the Scoro API after creating the trigger. This typically includes details about the newly created trigger such as its ID, status, and configuration.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Scoro API.
- The base URL and company account ID are also required and configured via credentials.
- Proper network access to the Scoro API endpoint is necessary.
Troubleshooting
- Unsupported Operation Error: If the node throws an error stating the operation is not supported, verify that the resource is set to "Trigger" and the operation to "Create".
- Invalid JSON in Request: Since the "Request" property expects valid JSON, malformed JSON will cause errors. Ensure the JSON is correctly formatted.
- Authentication Failures: Errors related to authentication usually indicate missing or incorrect API credentials. Verify the API key and other credential details.
- API Endpoint Issues: Network or base URL misconfiguration can lead to connection errors. Confirm the base URL is correct and accessible.
Links and References
- Scoro API Documentation (for details on trigger creation and request body structure)
- n8n Documentation (for general guidance on using custom nodes and credentials)