Wrike

How to integrate Wrike with Webflow

Connect Wrike and Webflow by embedding Wrike request forms directly into your pages or building with Webflow and Wrike APIs for custom data synchronization. You can also use third-party automation platforms like Zapier or Make.com for no-code workflows.

Embedding request forms maintains your site's branding while routing submissions to Wrike. Setup takes 10-15 minutes. API integrations give developers full control over real-time data flow between platforms.

Embed Wrike request forms

Wrike provides iframe embed codes for request forms that you can place into Webflow pages using the custom code embed element.

Create a request form in Wrike, enable external access, copy the generated iframe code, and paste it into Webflow.

To implement this integration follow these steps:

1. Create your request form in Wrike with custom fields, response routing, and branding settings per the Creating Request Forms guide
2. Copy the iframe code from the External Request Forms settings
3. In Webflow, add a custom code embed element and paste the iframe code

Webflow's native form blocks cannot accept third-party iframe code, so use the custom code embed element instead.

Build with Webflow and Wrike APIs

Custom API integrations provide complete control over data flow between platforms. The Webflow REST API provides endpoints for CMS collections, items, and webhooks, while Wrike's REST API v4 offers task creation, project management, and webhook capabilities. Learn more in the intro to the Webflow APIs.

Note that bidirectional sync requires careful implementation to avoid infinite loops.

Automate form submissions to task creation

Use Webflow's webhook system to trigger Wrike task creation. Configure a webhook in Webflow to monitor form submissions, then build middleware that receives webhook payloads and creates Wrike tasks via POST /folders/{folderId}/tasks from the Wrike Tasks API. Wrike automatically suspends webhooks after three consecutive failed deliveries for retryable status codes. Non-retryable 4xx errors cause immediate suspension.

Your integration server must verify webhook signatures using HMAC SHA-256. Map Webflow form fields to Wrike task properties, including title, description, and custom fields. Respond to Webflow with HTTP 200 to confirm successful receipt.

Wrike uses OAuth 2.0 exclusively with tokens that expire after one hour. Implement token refresh logic to maintain API access. Webflow supports 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 using the CMS API. Configure Webflow webhooks with triggerType: "collectionitemcreated" to monitor content changes, fetch item details via the List Collection Items endpoint, and create Wrike tasks using POST /folders/{folderId}/tasks. For reverse sync, poll Wrike's GET /tasks endpoint for recently modified tasks, then update Webflow CMS items via PATCH requests.

Map CMS item IDs to Wrike task IDs in your integration server to maintain sync state. This enables task updates in Wrike to reflect on Webflow pages, project milestone tracking through CMS collections, and consolidated reporting by querying both APIs. Real-time bidirectional sync requires custom development since neither platform provides native CMS sync capabilities.

Wrike enforces rate limits of 100-400 requests per minute per IP. Monitor response headers and implement exponential backoff for HTTP 429 responses. Wrike webhooks are automatically deactivated after failed delivery attempts, requiring monitoring and manual reactivation.

What you can build

Integrating Wrike with Webflow enables form submission automation, project task creation, and automated team collaboration workflows.

• Automated client intake system: Convert website inquiry forms into Wrike tasks using automation platforms like Zapier or Make.com, mapping contact details, project requirements, and budget information from form fields into task properties, with automatic routing to appropriate team members based on service type or project category
• Design feedback workflow: Create revision request forms that map to Wrike tasks through automation platforms, including client comments and priority levels, with assignments to designers and approval cycle tracking
• Website maintenance tracking: Capture bug reports and feature requests through Webflow forms connected to Wrike via automation platforms like Zapier or Make.com, creating prioritized tasks with category-based assignment
• Project request portal: Embed Wrike request forms directly into Webflow pages using the custom code embed element, allowing clients to submit project briefs that automatically create structured tasks in specific Wrike folders with custom field mapping