Use OAuth 2.0 to securely authorize Wrike to access the Blogs API. You will configure a client, request access tokens, and grant the correct scopes for blog creation and management.
In Wrike, register your application, choose the Blogs API scopes, and set redirect URIs to complete the OAuth flow.
Core endpoints you will use include: POST /blogs/posts to create posts, PUT /blogs/posts/:postId to update, POST /blogs/post-update.write for changes, GET /blogs/posts/url-slug-exists to check if a slug exists, GET /blogs/check-slug.readonly to verify slug availability, GET /blogs/categories to fetch categories, GET /blogs/authors to list authors.
Trigger when a Wrike task becomes publish ready
Actions create a new blog post via POST /blogs/posts, populate title and content from the Wrike task, and set author and category fields
Method path POST /blogs/posts
Key fields title content excerpt authorId categoryId publishDate
Trigger Wrike calendar indicates publish date
Actions set publishDate and status to scheduled using POST /blogs/posts
Method path POST /blogs/posts
Fields publishDate title content status authorId
Trigger when a Wrike task updates a related blog post
Actions update via PUT /blogs/posts/:postId, refresh slug if needed and sync categories
Method path PUT /blogs/posts/:postId
Fields postId title content categoryId status
Create, schedule, and update blog posts without writing code
Automate publishing and syncing between Wrike and the Blogs API
Centralized control with clear audit trails across teams
This section defines the main elements and processes used in the integration including endpoints, authentication, triggers, actions, and data mapping
An application programming interface that lets Wrike talk to the Blogs API to perform actions like create and update
A defined URL in the API to perform a specific action such as posting or updating a blog entry
A secure authorization framework used to grant Wrike access to the Blogs API without sharing user credentials
A URL friendly string that uniquely identifies a blog post
Turn Wrike task details into structured blog outlines with sections and bullet points ready for writing
Sync product launch calendars with blog publish dates to maintain cadence
Reuse drafts across platforms and manage metadata from Wrike
Create a Blogs API app, obtain client credentials, and configure OAuth in Wrike
Set up endpoint mappings, triggers, and data fields as shown earlier
Run tests for create update and schedule flows and enable activity logs
No coding is required with the built in Wrike to Blogs API bridge. You can enable the connection in your Wrike settings and point to the Blogs API endpoints for create and update actions. The mapping interface lets you tie Wrike task fields to blog post fields without touching code. This makes it quick to start and iterate.
For basic publishing you will use endpoints like POST /blogs/posts to create posts, GET /blogs/posts/url-slug-exists to check slugs, and PUT /blogs/posts/:postId to update. The exact mappings depend on your content model, but these calls cover typical create publish update flows.
Authentication uses OAuth 2.0. Wrike requests an access token with your Blogs API client credentials and uses refresh tokens to maintain access. Tokens are kept secure by the connector and do not require embedding credentials in requests.
Yes. You can schedule post publish dates by passing a publishDate field and setting the status accordingly. The flow can create a post with a future publish date and automatically publish when the date arrives.
Data mapping lets you connect Wrike fields such as title, content, and author to blog post fields like title, body, and author. Use mapping rules to transform Wrike data into the Blogs API payload.
If a Wrike task updates after a post is published you can trigger an update to the corresponding blog post using PUT /blogs/posts/:postId. The integration supports syncing title content and metadata to reflect changes.
Activity logs in Wrike show connection events, errors, and successful calls to the Blogs API. You can review logs to diagnose failures and confirm content flows between Wrike and your blog platform.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
