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 blueprint records when using the "Blueprint" resource with the "Get Many" operation. It fetches a list of blueprints (process templates) from the user's Tallyfy organization, supporting filtering, sorting, and pagination options.
Common scenarios where this node is beneficial include:
- Retrieving all or a subset of process templates for reporting or analysis.
- Filtering blueprints by status or tags to focus on relevant workflows.
- Sorting blueprints by creation or update dates or alphabetically by name.
- Integrating blueprint data into other automation workflows or dashboards.
Practical example:
- A user wants to get all active blueprints sorted by newest creation date to display in a dashboard.
- Another use case is fetching a limited number of archived blueprints tagged with specific keywords for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching blueprints or only up to a specified limit. |
| Limit | Maximum number of blueprints to return if not returning all (minimum 1, maximum 100). |
| Filters | Collection of filters to refine the blueprint search: |
| - Search | Text query to search within blueprints. |
| - Status | Filter blueprints by their status. Options: Active, Completed, Archived, Draft. |
| - Tags | Comma-separated list of tags to filter blueprints by. |
| - Sort By | How to sort the results. Options: Created Date (Newest), Created Date (Oldest), Updated Date (Newest), Updated Date (Oldest), Name (A-Z), Name (Z-A). |
Output
The output is an array of JSON objects representing blueprints retrieved from Tallyfy. Each object contains blueprint details as returned by the Tallyfy API under the /checklists endpoint. The exact fields depend on the API response but typically include blueprint ID, title, type, status, tags, creation and update timestamps, and other metadata.
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.
- The node makes HTTP GET requests to the Tallyfy API endpoints related to blueprints.
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 the Tallyfy API could cause request failures.
- Providing invalid filter values (e.g., unsupported status or malformed tags) might lead to no results or errors.
Error messages:
- Authentication errors: Check that the API key credential is correctly configured and valid.
- 404 Not Found: Verify the organization ID and resource paths.
- Validation errors: Ensure filter parameters conform to expected formats and allowed values.
- Network errors: Confirm network connectivity and that the Tallyfy API is reachable.
Links and References
- Tallyfy API Documentation (general reference for API endpoints)
- Tallyfy Workflow Automation Platform