Skip to content
Business productivity

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

Keep GitHub 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 GitHub and Wrike

Stop re-entering the same information in GitHub and Wrike: Stacksync keeps the records they share consistent in real time, in both directions.

Two tools in the daily stack often hold overlapping information: the same people, the same companies, or the same pieces of work, described twice. The tools do different jobs, so consolidating is not the answer; the overlap just needs to stop drifting.

Stacksync syncs Issues, Pull Requests, Commits, Releases in GitHub with Custom Fields, Comments, Timelogs, Contacts in Wrike in real time. You choose which records overlap, map the fields that should match, and pick a direction or let changes flow both ways. From then on, an update made in either tool is reflected in the other within seconds, without exports or copy-paste.

Because the sync is field-level, each tool keeps its own extras; only the shared data is held in agreement.

Common use cases

  • 01 Publish release data into customer-communication tools when a new version ships.
  • 02 Two-way sync of GitHub issues with Jira, Linear, or a support system so engineering and customer-facing teams work in their own tools.
  • 03 Sync Comments and status changes from Wrike into a database so downstream dashboards and tools react to project progress in near real time.
  • 04 Two-way sync of Tasks and their Custom Fields between a Wrike project and Postgres so ops teams work in SQL while project owners stay in Wrike.

Common sync patterns

Where one tool produces events: mirror them in the other

Payments, replies, messages, or tickets created in one tool can create or update matching records in the other, keeping context in one place.

Where Wrike is where the team documents or plans: keep its data fed

Information that originates in GitHub stays current in Wrike instead of going stale after a one-time paste.

Handoffs between teams

When work started in one tool continues in the other, the shared fields travel with it automatically.

What you can sync between GitHub 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.

GitHub objects Wrike objects How this pairing syncs
Issues Synced two-way with project trackers and support tools, including labels and assignees. Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. Issues is specific to GitHub and Comments to Wrike — each maps to any object or custom field on the other side.
Pull Requests Review state, status checks, and merge status feed engineering dashboards and workflow tools. Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. Pull Requests is specific to GitHub and Timelogs to Wrike — each maps to any object or custom field on the other side.
Commits Read-only history used to link code activity to tickets and releases. Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. Commits is specific to GitHub and Contacts to Wrike — each maps to any object or custom field on the other side.
Releases Tagged versions synced into changelogs, CRMs, or customer-notification systems. Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. Releases is specific to GitHub and Workflows to Wrike — each maps to any object or custom field on the other side.
Workflow runs (Actions) CI results synced into incident and reporting systems. Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. Workflow runs (Actions) is specific to GitHub and Spaces to Wrike — each maps to any object or custom field on the other side.
Organizations and Teams Membership data synced with identity systems and HR directories for access reviews. 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. Organizations and Teams is specific to GitHub and Tasks to Wrike — each maps to any object or custom field on the other side.

How changes propagate between GitHub 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.

GitHub Wrike Sub-second propagation

DetectionGitHub notifies Stacksync of record changes through webhook events. Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases.

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

Wrike GitHub 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 GitHub through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • GitHub: Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.
  • 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 GitHub ⇄ Wrike

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever GitHub 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 GitHub or Wrike record.

Observability

Monitoring

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

Trading partners

EDI

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

How the GitHub and Wrike connectors work

GitHub

Integration surface
REST API and GraphQL API
Authentication
OAuth 2.0, fine-grained personal access tokens, or GitHub App installation tokens
Change detection
Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases; polling for backfill
Capabilities
read · write · webhooks
Rate limits
Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.

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 GitHub 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 GitHub 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
    GitHub connected
    Wrike connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the GitHub 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 · GitHub ⇄ 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
    GitHub Wrike
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

GitHub 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
CSA STAR
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 462 integrations available for GitHub and Wrike.

Popular · 8 of 462
All GitHub 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