Scoro icon

Scoro

Interact with the Scoro API
Join our community

Actions50

Overview

This node integrates with the Scoro API, allowing users to interact with various Scoro resources such as triggers, tasks, projects, and more. Specifically, for the Trigger resource with the Get operation, the node retrieves detailed information about a single trigger by its ID or from a selectable list.

Common scenarios include:

  • Fetching configuration details of a specific automation trigger in Scoro.
  • Using trigger data to conditionally branch workflows based on trigger properties.
  • Auditing or logging trigger settings within broader workflow automations.

Practical example:

  • A user wants to retrieve the details of a particular trigger that initiates project updates, then use this data to customize notifications or further processing steps in n8n.

Properties

Name Meaning
Trigger Select the trigger to get details for. Options:
- From List: Search and select from existing triggers.
- By ID: Enter the numeric ID of the trigger directly.

Output

The node outputs JSON data representing the full details of the requested trigger. This typically includes all properties returned by the Scoro API for a trigger object, such as its ID, name, conditions, actions, status, and related metadata.

No binary data output is involved.

Dependencies

  • Requires an active connection to the Scoro API.
  • Needs an API key credential configured in n8n with appropriate permissions to access trigger data.
  • The base URL and company account ID are also required from the credentials to form API requests.

Troubleshooting

  • Error: Operation 'get' for resource 'trigger' is not supported.
    This indicates the node was called with an unsupported operation-resource combination. Verify that "Get" operation is selected for the "Trigger" resource.

  • Invalid Trigger ID format error:
    When entering the trigger ID manually, it must be numeric. Non-numeric input will cause validation errors.

  • Authentication failures:
    Ensure the API key and other credential details are correct and have sufficient permissions.

  • Empty or no results:
    If the trigger ID does not exist or the list search returns no matches, verify the trigger exists in Scoro and the credentials point to the correct company account.

Links and References

Discussion