Wrike icon

Wrike

Wrike API

Actions3

Overview

This n8n node interacts with the Wrike API to retrieve tasks based on various criteria. It supports fetching all tasks, tasks within a specific folder or space, task history, or tasks by their IDs. This node is useful for automating workflows that require access to task data from Wrike, such as reporting, synchronization with other tools, or triggering actions based on task updates.

Practical examples:

  • Retrieve all tasks in a specific project folder for weekly reporting.
  • Fetch details of specific tasks by their IDs for integration with another system.
  • Get the history of changes for a particular task to audit modifications.

Properties

Name Meaning
Task Option Determines how tasks are fetched:
- All Tasks: Get all tasks
- Folder: Get tasks in a specified folder
- History: Get the history of a specific task
- IDs: Get tasks by their IDs
- Space: Get tasks in a specified space
ID(s) Comma-separated list of task IDs. Used when "Task Option" is set to "IDs", "History", or for direct task retrieval. Example: FF545646,GGF56464
Folder ID The ID of the folder whose tasks you want to retrieve. Used when "Task Option" is set to "Folder". Example: FF545646
Space ID The ID of the space whose tasks you want to retrieve. Used when "Task Option" is set to "Space". Example: FF545646

Output

The output is a JSON array containing the response(s) from the Wrike API. The structure of each item depends on the selected "Task Option":

  • All Tasks / Folder / Space: Array of task objects, each representing a Wrike task with its properties (such as id, title, status, etc.).
  • IDs: Array of task objects matching the provided IDs.
  • History: Array of history records for the specified task(s).

Example output (for "IDs" option):

[
  {
    "kind": "tasks",
    "data": [
      {
        "id": "FF545646",
        "title": "Sample Task",
        "status": "Active"
        // ...other task fields
      }
    ]
  }
]

Dependencies

  • Wrike API: Requires a valid Wrike account and API access.
  • API Key/Credentials: You must configure the wrikeApi credential in n8n for authentication.

Troubleshooting

  • Invalid or missing credentials: If the wrikeApi credential is not set up correctly, requests will fail with authentication errors. Ensure your API token is valid and has sufficient permissions.
  • Incorrect IDs: Providing invalid or non-existent task, folder, or space IDs will result in empty responses or errors from the Wrike API.
  • Rate limits: Excessive requests may trigger Wrike API rate limiting. If you receive rate limit errors, reduce the frequency of your requests.

Common error messages:

  • "401 Unauthorized": Check your API credentials.
  • "404 Not Found": Verify the IDs (task, folder, or space) you have entered.
  • "400 Bad Request": Ensure required fields are filled and formatted correctly (e.g., comma-separated IDs).

Links and References

Discussion