Actions54
- Blueprint Actions
- Process Actions
- Task Actions
- Form Field Actions
- Comment Actions
- User Actions
- Guest Actions
- Group Actions
- Search Actions
- ID Finder Actions
Overview
This node interacts with the Tallyfy workflow automation platform, specifically focusing on managing "Process" resources. The "Get Many" operation retrieves multiple process instances (runs) from an organization’s Tallyfy account. It supports filtering, sorting, and limiting the number of results returned.
Typical use cases include:
- Fetching a list of active or completed processes to monitor workflow progress.
- Retrieving processes filtered by tags or search queries for reporting or auditing.
- Sorting processes by creation or update dates to analyze recent activity.
For example, a user might want to get all active processes tagged with "urgent" sorted by newest created date, or limit the output to 20 processes for a dashboard display.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching processes or only up to a specified limit. |
| Limit | Maximum number of process results to return when not returning all (minimum 1, maximum 100). |
| Filters | Collection of filters to refine the process list: |
| - Search | Text query to search within processes. |
| - Status | Filter processes by status: Active, Completed, Archived, or Draft. |
| - Tags | Comma-separated list of tags to filter processes by. |
| - Sort By | How to sort the results: Created Date (Newest/Oldest), Updated Date (Newest/Oldest), Name (A-Z/Z-A). |
Output
The node outputs an array of JSON objects representing the retrieved processes. Each object corresponds to a single process instance with its full details as provided by the Tallyfy API.
The structure includes fields such as process ID, name, status, tags, creation and update timestamps, and other metadata related to the process instance.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Tallyfy API.
- The node uses the base URL
https://go.tallyfy.com/apior a custom base URL if configured in credentials. - Requires the organization ID to scope API requests to the correct Tallyfy organization.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect organization ID may result in empty responses or errors.
- Exceeding the maximum allowed limit (over 100) will be rejected by the API.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid API keys or expired tokens; verify and update credentials.
- "Not Found" errors may mean the organization ID is incorrect or the resource does not exist.
- Rate limiting errors suggest too many requests in a short time; implement retries with backoff.
To resolve, ensure valid credentials, correct organization ID, and respect API limits.