Aident logoAident logo centerAident Loadout
PricingDocs
ENStart Now
AppsWrike ToolsWrike Fetch All Tasks
Wrike Tools

Wrike Fetch All Tasks

Fetches tasks from a Wrike account, allowing filtering by status, due date, and subfolder inclusion, with customizable response fields and pagination.

Write actionRisk level 2 of 5OAuth connection
Use Wrike Fetch All Tasks

Pricing and limits

Aident logo

Product

Aident LoadoutOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • fieldsarray
    A list of field names to include for each task in the response. Author-related fields: 'responsibleIds' (assigned users), 'sharedIds' (users task is shared with), 'authorIds' (task creators), 'followerIds' (task followers). Other common fields: 'description', 'briefDescription',…
  • statusstring
    Filter tasks by their status. Only tasks matching the specified status will be returned (e.g., Active, Completed).
  • due_dateobject
    Filter tasks by due date. Use 'equal' for an exact date match (yyyy-MM-dd), or 'start' and/or 'end' to define a date range (yyyy-MM-dd). If 'equal' is provided, 'start' and 'end' are ignored.
  • metadataobject
    Filter tasks by a single metadata key-value pair. Provide a dict with exactly one entry, e.g. {"department": "marketing"}. The Wrike API does not support filtering on multiple metadata pairs in a single request.
  • page_sizeinteger
    The number of tasks to return per page. Use with nextPageToken from the response to paginate; serialize requests across pages to avoid rate limit errors.
  • descendantsboolean
    If true, tasks from all subfolders and subprojects are included. If false, only tasks from the specified folder/project are returned.
  • resolve_user_namesboolean
    If true, automatically adds all user-related fields (authorIds, responsibleIds, sharedIds, followerIds) to the request and resolves user IDs to include user names and details directly in each task.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.