Skip to main content
What you can do:
  • Automatically ingest Wrike tasks into Gradial workflows
  • Filter by space, folder, status, or custom fields to control what gets executed
  • Route webhook events by folder/project ancestry or a single-select custom field
  • Attach source documents directly to Wrike tasks for context
  • Write previews, links, and status updates back to Wrike
  • Standardize execution pipelines across teams

Prerequisites

What you’ll need:
  • A Wrike service account — a dedicated user that Gradial acts through
    • Must have access to the spaces, folders, and projects you want to sync
    • Must be able to read the task context and attachments and make the comments or updates you request
  • A Permanent access token generated by the service account
  • For field-based webhook routing, an existing single-select custom field with the values you want to map to Gradial workspaces
A custom routing field is optional when you route by a folder or project. The current field picker supports single-select values rather than a free-text team-field label.

Authentication options


Connect Wrike to Gradial

Go to Settings → Integrations, select Wrike, and add an integration. The wizard has Connection, Routing, and Route summary steps.
  1. Log in to Wrike as the dedicated service account and open Wrike API settings.
  2. Create or open an app and generate its permanent access token. See Wrike’s permanent token instructions.
  3. On Connection, enter an integration name and paste the token into Permanent access token.
  4. Click Validate Connection and continue to Routing.
  5. Add the routes and destination workspaces/environments described below, review Route summary, and save.
Keep the token secure. Provider access and the identity used for assignment triggers come from the token’s account; the wizard does not require a separately typed assignee email or team-field name.

Configure routes

Select scheduled or webhook ingestion for the integration. Scheduled routes query matching tasks periodically; webhook routes react to supported events. Filters narrow the work eligible for a route, while mention and assignment triggers determine when webhook work starts.

Route by folder, project, or space

Set the route’s External project to the correct Wrike container ID, then choose the Gradial workspace and environment. Folder/project routing follows ancestry, so a task nested below the selected container can reach that route. Use distinct, specific scopes when teams work in different parts of the hierarchy.

Route by a custom field

In webhook mode, use Route by custom field when teams share folders or move tasks between workflow folders:
  1. Choose an available single-select field, such as Gradial Team, from the field picker.
  2. Choose the field value for this destination, such as Web.
  3. Select the Gradial workspace and environment, then review the displayed field and value labels in the route summary.
A field-filtered route can be configured without an external project. Keep field/value destinations unambiguous; conflicting destinations or incomplete selections prevent saving. A task that does not match the field filter does not qualify for that route merely because its folder matches. If the saved route has advanced conditions the picker cannot edit, those conditions remain applied. Contact your Gradial team to change them rather than replacing them with a simpler field selection. Configure Routes →

How task execution works

For assignment-triggered webhook intake, the typical flow is:
  1. A team member creates a task in a configured Wrike folder with a clear title and any attached reference files
  2. The task matches the route’s filters and the connected service account is added as a responsible user
  3. Gradial handles the assignment event, routes the task, and executes the request when the route’s trigger is enabled
  4. Previews, links, and comments are written back to the Wrike task
  5. A later recognized Gradial mention can request follow-up work on the linked Task
The webhook assignment check accepts the connected account anywhere in the task’s responsible-user list; it does not require the account to be the first assignee. A specific status such as In Progress is required only if your route’s filters require it. A filter match or status change alone is not a webhook execution trigger.

Troubleshooting

Contact your Gradial onboarding lead or email [email protected] if issues persist.