Building a flow in IBM App Connect with Wrike
Use App Connect to build flows that integrate with Wrike and other applications. The connector is displayed as Wrike on the IBM App Connect User Interface (UI) and the IBM Automation Explorer UI.
To allow App Connect to connect to your Wrike account, you need to fill in the connection fields that you see in the App Connect Designer Catalog page or flow editor.
Supported authorization types:
- BASIC OAUTH
- BEARER TOKEN
- OAUTH 2.0 AUTH CODE
For detailed information about different authorization types, a list of supported actions and events, how to generate connection field values, and how to use the Templates gallery, see How to use IBM App Connect with Wrike on the IBM Documentation webpage.
Supported objects in Wrike
Object |
Description |
Approvals |
Represents a request for approval sent to one or more users for a specific task or project in Wrike. |
Comments |
Represents a comment added to a task, project, or folder in Wrike. |
Folders or projects |
Represents a way to organize tasks and other work items in Wrike. |
Groups |
Represents a collection of users in Wrike, used to manage access, assign tasks, and track work for a specific team or department. |
Spaces |
Represents a top-level organizational unit in Wrike, used to separate and manage different work environments, such as departments, teams, or clients. |
Tasks |
Represents a single work item in Wrike, used to track and manage specific activities, projects, or initiatives. |
Time logs |
Represents a record of time spent working on a specific task in Wrike. |
Work schedules |
Represents a user's working hours and days in Wrike. |
Scenario 1: Create a comment in GitHub when a new comment is posted in Wrike and notify through a Slack message
Consider this scenario; When the flow is triggered, it detects new comments posted in Wrike and creates a subsequent comment in a Github issue while notifying the user through Slack.
The following steps are involved in the flow:
Scenario 2: Create a task in Wrike when a new issue is raised in GitHub and notify through a Slack message
Consider this scenario; when the flow is triggered, it detects new issues created in GitHub and creates a task in Wrike while notifying the user through Slack.
The following steps are involved in the flow: