Actions50
- Status Actions
- Task Actions
- Calendar Actions
- ClientProfile Actions
- Comment Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node integrates with the Scoro API, allowing users to perform various operations on different Scoro resources. Specifically, for the Trigger - Create operation, it enables creating a new trigger in Scoro by sending a custom JSON request body. This is useful when automating workflows that depend on event triggers within Scoro, such as notifications or task automation based on specific conditions.
Practical examples include:
- Creating a trigger that fires when a new project is created.
- Setting up a trigger to notify a team when an invoice status changes.
- Automating follow-up actions when a client profile is updated.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body used to create a trigger in Scoro. It should contain all necessary fields as per Scoro's API specification for trigger creation. |
Output
The node outputs the response from the Scoro API after attempting to create the trigger. The output is structured as JSON data containing details of the newly created trigger or error information if the creation failed.
If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is JSON.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential and company account ID configured in n8n credentials for authentication.
- The base URL for the Scoro API must be set in the credentials.
- No additional external dependencies beyond the Scoro API and proper credential setup.
Troubleshooting
- Unsupported Operation Error: If you select an operation-resource combination not supported (e.g., "create" for a resource without implementation), the node throws an error indicating the operation is unsupported.
- Invalid JSON in Request Property: The
Requestproperty expects valid JSON. Providing malformed JSON will cause parsing errors. - Authentication Failures: Ensure the API key and company account ID are correctly configured; otherwise, API calls will fail.
- API Errors: If the Scoro API returns an error (e.g., missing required fields in the request), the node will output the error details. Review the request JSON structure against Scoro's API documentation.