Skip to content
Accounting and finance ⇄ Business productivity

Adyen to Monday integration — real-time, two-way sync

Keep Adyen and Monday 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 Adyen and Monday

Connect the financial records in Adyen with the work happening in Monday, so both stay current without exports or copy-paste.

Adyen holds the financial truth: who the customers are, what they were billed, what they paid. Monday is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Merchant Accounts, Stores, Users and API Credentials, Webhook Configurations in Adyen and Items, Subitems, Column values, Groups in Monday in sync, bi-directionally and in real time. Whatever records Monday keeps and whatever events it produces, the overlap with Adyen is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

Common use cases

  • 01 Load Settlement Detail Reports into a warehouse to break out fees, interchange, and net payouts by merchant account for finance and treasury reporting.
  • 02 Ingest AUTHORISATION, CAPTURE, REFUND, and CHARGEBACK webhooks into Postgres or a warehouse so finance reconciles Adyen settlements against orders in an ERP without manual report exports.
  • 03 Sync Updates and status changes from monday.com into a database so downstream tools and dashboards react to project progress in near real time.
  • 04 Two-way sync of Items and their Column values between a monday.com board and Postgres so ops teams work in SQL while project owners stay in monday.com.

Common sync patterns

Where Monday handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Adyen next to the customer they are helping, without logging into the finance system.

Where Monday collects payments or triggers charges: events land in Adyen

Payment and charge activity flows into Adyen as it happens, so the books reflect reality without manual reconciliation.

Where Monday tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

What you can sync between Adyen and Monday

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.

Adyen objects Monday objects How this pairing syncs
Payments Checkout API payment requests and results (/payments); created to authorize a card, wallet, or local payment, and retrieved by pspReference. Final state arrives asynchronously via the AUTHORISATION webhook. Boards Table-like containers that hold items; each board maps to a synced table, and its columns define the field mapping. Payments is specific to Adyen and Boards to Monday — each maps to any object or custom field on the other side.
Modifications (Captures, Refunds, Cancels) Actions on an authorized payment via /payments/{pspReference}/captures, /refunds, and /cancels; written to settle, return, or void funds, with results confirmed by CAPTURE and REFUND webhooks. Items Rows within a board and the primary record; synced two-way and created, updated, archived, or deleted via GraphQL mutations. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Items to Monday — each maps to any object or custom field on the other side.
Payment Links Hosted payment link objects created through /paymentLinks; created, retrieved, and expired, with paid or expired status reported back through webhooks for accounts-receivable sync. Subitems Nested rows under items, stored on a separate hidden board; synced as a child table linked to the parent item. Payment Links is specific to Adyen and Subitems to Monday — each maps to any object or custom field on the other side.
Merchant Accounts Company and merchant account entities in the Management API; read and updated to keep account configuration, payment-method settings, and capabilities aligned with internal systems. Column values Typed fields (status, date, people, numbers, connect-boards); polymorphic JSON usually written together via change_multiple_column_values. Merchant Accounts is specific to Adyen and Column values to Monday — each maps to any object or custom field on the other side.
Stores Physical and online store entities under a merchant account (Management API); full CRUD, so new locations and their payment-method configuration can be provisioned from an internal admin source. Groups Named sections that group items inside a board; synced as a grouping attribute or category field on the row. Stores is specific to Adyen and Groups to Monday — each maps to any object or custom field on the other side.
Users and API Credentials Customer Area users and API-credential objects managed via the Management API; created, updated, and deprovisioned to keep Adyen access aligned with an IdP or HR source. Updates Comment and activity threads attached to items; read out into a database for reporting or written back as notes. Users and API Credentials is specific to Adyen and Updates to Monday — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Monday

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.

Adyen Monday Sub-second propagation

DetectionAdyen notifies Stacksync of record changes through webhook events. Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks.

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

Monday Adyen Sub-second propagation

DetectionMonday notifies Stacksync of record changes through webhook events. Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events.

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

Rate-limit considerations

  • Adyen: Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.
  • Monday: Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window.
What ships with Adyen ⇄ Monday

Connect Adyen and Monday for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Adyen or Monday instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adyen or Monday 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 Adyen or Monday record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Adyen and Monday.

How the Adyen and Monday connectors work

Adyen

Integration surface
REST APIs on adyen.com - Checkout (/checkout/v71), Management (/v3), Balance Platform / Configuration, Transfers, Payouts, and Reports, with standard webhooks for events
Authentication
API key in the X-API-Key header per web service or Balance Platform user (primary for Checkout, Management, and Balance Platform); Basic auth for classic web-service users; OAuth 2.0 for partner integrations; client keys are client-side only
Change detection
Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks; all HMAC-signed and acknowledged with a 2xx within about 10 seconds. No database-style CDC; historical transactions come from Settlement Detail Reports
Capabilities
read · write · webhooks
Rate limits
Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.

Monday

Integration surface
GraphQL API (single endpoint, api.monday.com/v2)
Authentication
OAuth 2.0 for installed apps, or a per-user personal API token (admin/member scope); a date-based API version is sent via request header
Change detection
Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events; polling falls back to the item updated_at field
Capabilities
read · write · webhooks
Rate limits
Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window
Monday setup guide
How it works

How to connect Adyen to Monday — 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 Adyen and Monday 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
    Adyen connected
    Monday connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Adyen and Monday 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 · Adyen ⇄ Monday
    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
    Adyen Monday
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Adyen and Monday 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 506 integrations available for Adyen and Monday.

Popular · 8 of 506
Coworkers laughing in front of a laptop in a casual office setting

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