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 to retrieve multiple tasks ("Get Many" operation on the "Task" resource). It allows users to fetch a list of tasks from their Tallyfy organization, applying optional filters such as search queries, status, tags, and sorting preferences. Users can choose to return all matching tasks or limit the number of results.
Common scenarios include:
- Retrieving active tasks assigned to a user for monitoring workload.
- Fetching completed or archived tasks for reporting or auditing purposes.
- Searching tasks by tags or keywords to quickly find relevant work items.
- Sorting tasks by creation or update date to prioritize recent activities.
Practical example:
A project manager wants to get all active tasks tagged with "urgent" sorted by newest created date to review what needs immediate attention.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching tasks or only up to a specified limit. |
| Limit | Maximum number of tasks to return if not returning all (minimum 1, maximum 100). |
| Filters | Collection of filters to narrow down the task list: |
| - Search | Text query to search within tasks. |
| - Status | Filter tasks by their status. Options: Active, Completed, Archived, Draft. |
| - Tags | Comma-separated list of tags to filter tasks by. |
| - Sort By | How to sort the returned tasks. Options: Created Date (Newest/Oldest), Updated Date (Newest/Oldest), Name (A-Z/Z-A). |
Output
The output is an array of JSON objects representing tasks retrieved from Tallyfy. Each object contains the full task data as returned by the Tallyfy API, including properties like task ID, title, status, tags, deadlines, assignees, and other metadata.
If "Return All" is enabled, the node will paginate through all available pages to collect all matching tasks before returning them.
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 provided in credentials. - Requires the organization ID to scope requests to the correct Tallyfy organization.
- Network access to Tallyfy's API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect organization ID may result in empty responses or errors.
- Exceeding rate limits imposed by Tallyfy API could lead to request failures.
- Providing invalid filter values (e.g., unsupported status) might cause errors or no results.
Error messages:
- Authentication errors typically indicate problems with the API key or token; verify credentials.
- "Not Found" errors may mean the organization ID or resource IDs are incorrect.
- Validation errors can occur if input parameters do not meet expected formats or constraints.
Resolutions:
- Double-check API credentials and organization ID configuration.
- Ensure filter values conform to allowed options.
- Use "Return All" cautiously to avoid large data loads that may time out.
- Enable "Continue On Fail" in n8n to handle partial failures gracefully.
Links and References
- Tallyfy API Documentation
- Tallyfy Official Website
- n8n documentation on HTTP Request Node (for understanding underlying HTTP calls)