Wrike

How to integrate Wrike with Webflow

Wrike helps teams manage client intake, project workflows, and task assignments. Connecting Wrike with Webflow automates form submissions into project tasks, syncs project data with your website, and routes client requests to the right team members without manual data entry.

Connect Wrike and Webflow through automation platforms like Zapier and Make.com, embed Wrike request forms directly into your site using iframe code, or build custom integrations using both platforms' REST APIs.

Use Zapier or Make.com apps

Automation platforms connect Webflow and Wrike without writing code. Zapier offers a pre-built template called "Create new tasks in Wrike from new form submissions in Webflow" that creates Wrike tasks from Webflow form submissions. Make.com requires building custom scenarios from scratch since no pre-built templates exist for Wrike-Webflow connections. Both platforms handle authentication automatically and let you map form fields to task properties through dropdown menus.

Setup takes 10-20 minutes for basic Zapier workflows using the pre-built template. Make.com typically requires 15-25 minutes for custom scenario construction. Zapier's Professional plan starts at $19.99/month and includes Wrike integration. Both platforms use polling intervals on free tiers rather than instant webhooks, with 5-15 minute delays between checks for new Webflow form submissions.

This integration enables the following actions:

• Form-to-task automation: Webflow form submissions automatically create Wrike tasks, mapping form fields like name, email, and message to task title, description, and custom fields
• Client inquiry routing: Route Webflow form submissions to specific Wrike folders or projects based on request type, automatically assigning tasks to designated team members based on the service selected in the form
• Real-time notifications: Trigger Wrike comments or status updates when specific Webflow events occur, keeping teams informed without manual updates
• Complex workflows: Make.com scenarios support conditional logic, data transformation of Webflow CMS items into Wrike task properties, and multiple actions per trigger for complex business processes

Platform requirements and limitations:

Forms must be published with at least one submission before appearing in automation platforms. Component-based Webflow forms are inaccessible via major automation platforms. Place forms at page level for integration compatibility.

Embed Wrike request forms

Wrike provides iframe embed codes for request forms that you can place directly into Webflow pages using the Custom Code Embed element. Create a request form in Wrike, enable external access per the External Request Forms documentation, copy the generated iframe code, and paste it into a Webflow Embed element. This method maintains your site's branding while routing submissions directly into Wrike projects. Setup takes 10-15 minutes and requires Wrike Business plan or higher.

Dashboards, project views, and task displays cannot be embedded using this approach. This is the only official low-code embedding method available.

Implementation steps:

Create your request form in Wrike with custom fields, response routing, and branding settings by following the Creating Request Forms guide. Once your form is configured and published, copy the iframe code from the External Request Forms documentation. In Webflow, add a Custom Code Embed element to your page and paste the iframe code. Webflow's native form blocks cannot accept third-party iframe code, so you must use the Embed element. The form appears inline within your page layout with full design control over surrounding elements.

Build with Webflow and Wrike APIs

Building custom API integrations gives you complete control over data flow between platforms. Webflow's REST API v2 provides endpoints for CMS collections, items, and webhooks, while Wrike's REST API v4 offers task creation, project management, and webhook capabilities. This approach enables real-time synchronization and bidirectional data updates, though authentic two-way sync requires careful implementation to avoid infinite loops.

Automate form submissions to task creation

Use Webflow's webhook system to trigger Wrike task creation with near real-time processing. Configure a webhook in Webflow to monitor form submissions using the Working with Webhooks documentation, then build an integration server (middleware) that receives webhook payloads and creates Wrike tasks via POST /folders/{folderId}/tasks from the Wrike Tasks API. This pattern minimizes delays compared to polling-based approaches. Webhook reliability depends on maintaining active monitoring since Wrike automatically suspends webhooks after three consecutive failed deliveries.

Your integration server must verify webhook signatures using HMAC SHA-256 (a cryptographic method that confirms webhooks originate from Webflow) following the Webhook Signatures documentation. Extract form data from the webhook payload, transform it into Wrike's task creation format, and map Webflow form fields to Wrike task properties including title, description, and custom fields. Implement error handling for API failures and respond to Webflow with HTTP 200 status to confirm successful webhook receipt.

Authentication requirements:

Wrike uses OAuth 2.0 exclusively with tokens that expire after one hour according to Wrike's OAuth 2.0 documentation. Implement token refresh logic to maintain continuous API access. Webflow supports both site tokens for single-site integrations and OAuth tokens for multi-site access. Store credentials securely and never expose tokens in client-side code.

Sync CMS data with project information

Build bidirectional synchronization between Webflow CMS collections and Wrike projects. Configure Webflow webhooks with triggerType: "collection_item_created" to monitor content changes, fetch full item details via the CMS Items API using GET /collections/{collection_id}/items/{item_id}, and create corresponding Wrike tasks using POST /folders/{folderId}/tasks. For reverse synchronization, implement polling using Wrike's GET /tasks endpoint with query parameters to fetch recently modified tasks, then update Webflow CMS items via PATCH /collections/{collection_id}/items/{item_id}.

Map CMS item IDs to Wrike task IDs within your integration server to maintain synchronization state between the platforms. This enables task updates in Wrike to be retrieved and reflected on client-facing Webflow pages, project milestone tracking through CMS collections updated via API polling, and consolidated reporting by querying both platform APIs. Real-time bidirectional synchronization requires custom development, as neither platform provides native CMS sync capabilities or direct integration. Wrike does not offer a native Forms API, so task creation must occur directly via the Tasks API rather than form submissions.

Request pacing considerations:

Implement request pacing strategies when making API calls to both platforms. Wrike enforces approximately 400 requests per minute according to their Help Center documentation. Monitor response headers and implement exponential backoff when receiving HTTP 429 responses. Use webhook-based architecture to minimize API calls. Wrike webhooks will be automatically deactivated after three consecutive failed delivery attempts, requiring active monitoring and manual reactivation.

Implement webhook-based automation

Both platforms provide webhook infrastructure for event-driven integration. Webflow's Create Webhook endpoint supports form submissions, site publishes, and CMS changes. Wrike's Webhooks documentation describes webhook event types including TaskCreated, TaskUpdated, TaskDeleted, TaskCompleted, TaskCustomFieldChanged, FolderCustomFieldChanged, FolderTitleChanged, ProjectCreated, ProjectUpdated, ProjectDeleted, CommentAdded, CommentDeleted, AttachmentAdded, AttachmentDeleted, and TimelogAdded, with filtering capabilities by custom fields and Custom Item Types.

Configure webhooks at appropriate scopes (folder, space, or account level for Wrike; site level for Webflow) and implement signature verification for security. Wrike webhooks automatically deactivate after three consecutive failed deliveries according to Rollout's implementation guide. Build active monitoring, prioritize fast response times, and push heavy processing to background jobs to prevent deactivation.

What you can build

Integrating Wrike with Webflow through automation platforms or custom APIs automates client intake, creates project tasks from website activity, and syncs project data between systems.

• Automated client intake system: Convert website inquiry forms into Wrike tasks using automation platforms like Zapier or Make.com, map contact details and project requirements from form fields into task properties, and route tasks to appropriate team members based on service type or project category
• Client project portals: Build branded client dashboards in Webflow that sync with Wrike project data through API integrations or automation platforms, display project status and milestone information from Wrike's API, and give clients visibility into project progress
• Design feedback workflow: Create revision request forms that map to Wrike tasks through automation platforms, include client comments and priority levels, and assign tasks to designers with approval cycle tracking
• Website maintenance tracking: Capture bug reports and feature requests through Webflow forms connected to Wrike via automation platforms, create prioritized tasks with category-based assignment, and generate maintenance reports from completed task data

‍