Wrike
Wrike is a cloud-based work management platform that teams use to plan, manage, and track projects and tasks. The Wrike API provides programmatic access to projects, tasks, folders, spaces, workflows, contacts, comments, and custom fields, allowing Nexla to both ingest work-management data and push task updates back into Wrike.
Power end-to-end data operations for your Wrike API with Nexla. Our bi-directional Wrike connector is purpose-built for Wrike, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Wrike or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Wrike workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a Wrike credential, you need a permanent access token and the Wrike API base URL. Wrike authenticates API requests with a bearer token sent in the Authorization header. A permanent access token never expires, so it is well suited to a Nexla integration that runs on an ongoing schedule.
To obtain a permanent access token, follow these steps:
-
Sign in to your Wrike account with a user that has the permissions required for the data you plan to read or write.
-
Click your profile image in the sidebar, and select Apps & Integrations from the drop-down menu.
-
Click the API tab at the top of the view.
-
Select the app you want to generate a token for, or hover over the app and click the Settings gear icon. If you do not already have an app, click + App to create one, provide an app name and description, and save it.
-
Scroll down to the Permanent access token section and click Get token.
-
In the pop-up, click Obtain token. You will be asked to enter your Wrike password before the token is generated.
-
Copy and securely store the token immediately, as it is shown only once. Treat this token like a password, because anyone who holds it can access your Wrike data through the API.
The Base URL for the Wrike API is typically https://api.wrike.com/api/v4 for production accounts. Some accounts are hosted on a regional data center and use a host such as https://app-us2.wrike.com/api/v4 or https://app-eu.wrike.com/api/v4; confirm the correct host for your account in the Wrike API documentation if requests to the default host are redirected. For details about authentication, tokens, and available endpoints, see the Wrike API documentation.
Authenticate
Credentials required
Authenticate using a Wrike API token. Generate a permanent token from your Wrike account settings and use it as a bearer token in the Authorization header.
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key Value | Yes | Yes | An encoded string value used as a secret token to authenticate API requests |
| Base URL | Yes | No | Wrike API base URL. Typically https://api.wrike.com/api/v4 for production. |
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter your Wrike permanent access token in the API Key Value field. This token is sent as a bearer token in the
Authorizationheader for all API requests and must be kept confidential. -
Enter the Wrike API base URL in the Base URL field. For most accounts this is
https://api.wrike.com/api/v4; use your account's regional host if applicable.If your permanent access token is compromised, revoke it in your Wrike Apps & Integrations settings and generate a new one. The token grants access to your Wrike data and should be treated as sensitive information.
For detailed information about Wrike authentication, tokens, and available endpoints, see the Wrike API documentation.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Wrike connector tile, then select the credential that will be used to connect to the Wrike instance, and click Next; or, create a new Wrike credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Wrike endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Wrike data sources can also be manually configured to ingest data from any valid Wrike API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Wrike data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Use as a destination
Click the + icon on the Nexset that will be sent to the Wrike destination, and select the Send to Destination option from the menu. Select the Wrike connector from the list of available destination connectors, then select the credential that will be used to connect to the Wrike account, and click Next; or, create a new Wrike credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Wrike endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Manual configuration
Wrike destinations can also be manually configured to send data to any valid Wrike API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Wrike APIs typically expect form-encoded or JSON parameters for write operations. For update and delete operations, include the identifier of the target task in the request URL.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Wrike endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Wrike endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.