Flowyteam icon

Flowyteam

Custom node for Flowyteam API
Join our community

Actions101

Overview

The node interacts with the Flowyteam API to manage various resources, including Task Categories. Specifically, for the Task Category resource with the Get Many operation, it retrieves multiple task category records from the Flowyteam system. This operation supports pagination, searching, sorting, and can return either simplified or raw API response data.

This node is beneficial in scenarios where you need to list or process multiple task categories, such as generating reports, syncing task categories with other systems, or displaying them in dashboards.

Example use cases:

  • Fetching a paginated list of task categories filtered by a search term.
  • Retrieving all task categories sorted by name or ID in ascending or descending order.
  • Getting simplified data for easier processing or raw data for detailed inspection.

Properties

Name Meaning
Limit Max number of results to return (minimum 1).
Page Page number for pagination (starting at 1).
Search Search term to filter task categories by matching text.
Simplify Whether to return simplified response data or the full raw API response.
Sort Direction Direction to sort the results: "Ascending" or "Descending".
Sort Field Field to sort by: "ID" or "Category Name".

Output

The output is an array of JSON objects representing task categories retrieved from the Flowyteam API.

  • If Simplify is enabled (true), the output contains a simplified version of each task category, likely including key fields such as ID and category name.
  • If Simplify is disabled (false), the output includes the full raw API response for each task category, which may contain additional metadata and nested information.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Flowyteam API via an API key credential configured in n8n.
  • The node depends on the Flowyteam API endpoints for task category management.
  • Proper network access and valid authentication credentials are necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Requesting pages beyond available data may return empty results.
    • Using unsupported sort fields or directions might result in API errors.
    • Network connectivity problems can cause timeouts or failures.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • Validation errors may occur if input parameters like limit or page are out of range; ensure they meet minimum requirements.
    • API rate limits could be hit if too many requests are made in a short period; consider adding delays or reducing request frequency.

Links and References

Discussion