Skip to content
Developer tools ⇄ Business productivity

PagerDuty to Wrike integration — real-time, two-way sync

Keep PagerDuty and Wrike in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect PagerDuty and Wrike

Connect the tickets, records, and events in Wrike to the systems engineering runs in PagerDuty, kept current in real time and in both directions.

Wrike is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. PagerDuty is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.

Stacksync syncs Folders & Projects, Custom Fields, Comments, Timelogs in Wrike with Services, Users, Teams, Schedules in PagerDuty field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.

Common use cases

  • 01 Mirror Folders, Projects, and Timelogs into a warehouse for cross-team reporting on status, timelines, and logged hours without manual exports.
  • 02 Push support tickets or intake requests from an operational database into Wrike Tasks, then read completion and status Custom Fields back when work finishes.
  • 03 Provision and deactivate Users and Team memberships two-way from an HRIS or identity provider so the on-call roster matches the current org.
  • 04 Write Schedules and Escalation Policies from a workforce tool or source-of-truth spreadsheet so rotations and overrides stay consistent across teams.

Common sync patterns

Where PagerDuty moves messages between services: activity lands on the stream

Records created or changed in Wrike publish to the queue or topic in PagerDuty as they happen, so downstream services react to real events rather than polling for them.

Where PagerDuty is the directory or identity source: one set of users

People and accounts in Wrike stay matched to the users in PagerDuty, so access, provisioning, and org changes propagate instead of being keyed in twice.

Where PagerDuty watches operations: live volumes for visibility

Open items, throughput, and error counts from Wrike replicate into PagerDuty, so the operational view reflects what is actually happening in the business.

What you can sync between PagerDuty and Wrike

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

PagerDuty objects Wrike objects How this pairing syncs
Incidents Core records with status of triggered, acknowledged, or resolved plus urgency and assignments; created, updated, and resolved two-way, with V3 webhooks firing on each transition. Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. Incidents is specific to PagerDuty and Timelogs to Wrike — each maps to any object or custom field on the other side.
Services Technical services that group incidents and hold integration keys; read and written two-way, with service.created, service.updated, and service.deleted webhook events. Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. Services is specific to PagerDuty and Contacts to Wrike — each maps to any object or custom field on the other side.
Users Responders with contact methods and notification rules; provisioned and updated two-way to keep the on-call roster aligned with an HRIS or identity provider. Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. Users is specific to PagerDuty and Workflows to Wrike — each maps to any object or custom field on the other side.
Teams Groupings of users, services, and escalation policies; synced two-way so membership mirrors org structure from an IdP or HRIS. Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. Teams is specific to PagerDuty and Spaces to Wrike — each maps to any object or custom field on the other side.
Schedules On-call rotations built from layers and overrides; read and written so calendar or workforce tools can drive who is on call. Tasks The primary unit of work and main record; created, updated, completed, and deleted via the REST v4 API and synced two-way. Subtasks are Tasks linked by superTask/subTask references. Schedules is specific to PagerDuty and Tasks to Wrike — each maps to any object or custom field on the other side.
Escalation Policies Ordered rules routing incidents to users and schedules; read and written two-way to codify paging logic from a source of truth. Folders & Projects The container hierarchy: Folders group Tasks, and Projects add dates, an owner, and a status. Each maps to a synced table scope, and its structure defines what a sync covers. Escalation Policies is specific to PagerDuty and Folders & Projects to Wrike — each maps to any object or custom field on the other side.

How changes propagate between PagerDuty and Wrike

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

PagerDuty Wrike Sub-second propagation

DetectionPagerDuty notifies Stacksync of record changes through webhook events. V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated).

DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.

Wrike PagerDuty Sub-second propagation

DetectionWrike notifies Stacksync of record changes through webhook events. Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event.

DeliveryEach detected change is written to PagerDuty through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • PagerDuty: REST API allows 960 requests per minute per token and returns HTTP 429 when exceeded; the Events API is rate-limited separately per integration key.
  • Wrike: Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff.
What ships with PagerDuty ⇄ Wrike

Connect PagerDuty and Wrike for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every PagerDuty–Wrike connection.

Real-time

Two-way sync

Changes in PagerDuty or Wrike instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever PagerDuty or Wrike data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single PagerDuty or Wrike record.

Observability

Monitoring

Track your PagerDuty ⇄ Wrike sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between PagerDuty and Wrike.

How the PagerDuty and Wrike connectors work

PagerDuty

Integration surface
REST API v2 (plus Events API v2 for inbound alerts)
Authentication
REST API token via the Authorization: Token header (account-level for full access or user-level scoped to the user's permissions), or OAuth 2.0 (Authorization Code / PKCE); the Events API v2 uses a per-service routing (integration) key
Change detection
V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated); list endpoints also support polling with updated_at and since/until windows
Capabilities
read · write · webhooks
Rate limits
REST API allows 960 requests per minute per token and returns HTTP 429 when exceeded; the Events API is rate-limited separately per integration key.
PagerDuty setup guide

Wrike

Integration surface
REST API v4 (JSON), single account endpoint such as www.wrike.com/api/v4; the data-center host (US or EU) comes from the OAuth token response, plus REST-managed Webhooks
Authentication
OAuth 2.0 for multi-user apps (Authorization header carrying access_token and requested scopes), and a legacy Permanent Access Token for single-account and testing use
Change detection
Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event filtering and custom payload fields; polling the task updatedDate is the fallback
Capabilities
read · write · webhooks
Rate limits
Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff
Wrike setup guide
How it works

How to connect PagerDuty to Wrike — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate PagerDuty and Wrike with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    PagerDuty connected
    Wrike connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the PagerDuty and Wrike objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · PagerDuty ⇄ Wrike
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    PagerDuty Wrike
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

PagerDuty and Wrike integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 390 integrations available for PagerDuty and Wrike.

Popular · 7 of 390
All PagerDuty integrations All Wrike integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own