Wrike TRIGGER
New Task Created
- Trigger
- Instant
- OAuth
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Wrike account, configure the source, and choose the webhook where your backend receives events.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const deployed = await pd.triggers.deploy({
id: "wrike-new-task-created",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wrike: { authProvisionId: "apn_xxxxxxx" },
folderId: "Folder ID",
spaceId: "Space ID",
},
webhookUrl: "https://example.com/webhooks/wrike",
})
console.log(deployed.id)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "wrike-new-task-created",
"webhook_url": "https://example.com/webhooks/wrike",
"configured_props": {
"wrike": { "authProvisionId": "apn_xxxxxxx" },
"folderId": "Folder ID",
"spaceId": "Space ID"
}
}'MCP servers expose Wrike actions as on-demand tools.
New Task Created is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
folderId Folder ID | string | Receive notifications for tasks in a folder and, optionally, in its subfolders. Leave blank to receive notifications for all tasks in the account Optional |
spaceId Space ID | string | Receive notifications for changes to tasks, folders, and projects within a space. Leave blank to receive notifications for all tasks in the account Optional |
recursive Recursive | boolean | Specifies whether hook should listen to events for subfolders or tasks anywhere in the hierarchy. Defaults to false Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Wrike through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — as it happens.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- wrike-new-task-created
- Version
- 0.0.3
- App
- Wrike
- Authentication
- OAuth
- Delivery
- Instant event
- Output
- Events emitted by Wrike.
- Source
- View on GitHub ↗