- Automatically ingest Wrike tasks into Gradial workflows
- Filter by space, folder, status, or custom fields to control what gets executed
- 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:- Your Wrike domain (e.g.,
https://app.wrike.com) - A Wrike service account — a dedicated user that Gradial acts through
- Must have access to the spaces, folders, and projects you want to sync
- Should be set as the first assignee on any task you want Gradial to process
- A Personal Access Token (PAT) generated by the service account
- A designated custom team field for task routing (e.g., “Gradial Team”) — must be a short-text field
Authentication options
Connect Wrike to Gradial
Go to Integrations in the Gradial sidebar, select Wrike, and click Add Integration.- Enter your Wrike domain
- Enter the service account email in the Assignee field
- Enter the custom team field label exactly as it appears in Wrike (e.g.,
Gradial Team) - Generate a PAT: log in as the service account → profile settings → Apps & Integrations → Access Tokens → Create new token
- Paste the token into Personal Access Token
- Optionally add filters to limit which tasks Gradial ingests (see below)
- Click Save
Configure routes
Once connected, create routes to define which Wrike tasks sync into which Gradial workspaces. Wrike supports filtering by space, folder, and status. Configure Routes →How task execution works
Once integrated, the typical flow is:- A team member creates a task in a configured Wrike folder with a clear title and any attached reference files
- The task is assigned to the Gradial service account and set to
In Progress - Gradial ingests the task and executes the request
- Previews, links, and comments are written back to the Wrike task
- Task status updates automatically as execution progresses
Troubleshooting
Contact your Gradial onboarding lead or email [email protected] if issues persist.