Skip to content
Business productivity ⇄ Database

Asana to Reltio integration — real-time, two-way sync

Keep Asana and Reltio 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 Asana and Reltio

Mirror Asana's data into Reltio so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Asana through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Reltio.

Stacksync mirrors Users, Portfolios, Tags, Teams / Workspaces from Asana into Entities, Relations, Crosswalks, Interactions in Reltio and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Asana, so the tool and the database never disagree.

Common use cases

  • 01 Mirror Projects, Sections, and Portfolios into a warehouse for cross-team reporting on status, timelines, and workload without CSV exports.
  • 02 Push support tickets or intake requests from an operational database into Asana Tasks, then read completion and status Custom fields back when work finishes.
  • 03 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 04 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.

Common sync patterns

Read Asana with a query

Records from Asana are ordinary rows in Reltio; join them, index them, and use them in application logic without touching the vendor API.

Automate Asana from your codebase

Write to the synced tables in Reltio and Stacksync propagates the change into Asana, replacing custom integration code.

React to changes as they happen

Updates in Asana arrive as row changes in Reltio, so triggers, jobs, and services can respond in near real time.

What you can sync between Asana and Reltio

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.

Asana objects Reltio objects How this pairing syncs
Tasks The primary unit of work and main record; created, updated, completed, and deleted via REST and synced two-way. Subtasks are Tasks with a parent reference. Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Tasks is specific to Asana and Activity Log to Reltio — each maps to any object or custom field on the other side.
Projects Collections of Tasks with a layout (list, board, timeline, calendar); each project maps to a synced table scope and its custom fields define the mapping. Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Projects is specific to Asana and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side.
Sections Ordered groupings of Tasks within a project; synced as a grouping attribute or category field on the row. Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Sections is specific to Asana and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side.
Custom fields Typed fields (text, number, enum, multi-enum, date, people) defined at project or workspace level; mapped to database columns, with enum values written by option GID. Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Custom fields is specific to Asana and Entities to Reltio — each maps to any object or custom field on the other side.
Stories Comments and activity entries on a Task; read out for history and reporting or written back as comments. Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Stories is specific to Asana and Relations to Reltio — each maps to any object or custom field on the other side.
Users Members of a workspace or organization referenced by assignee and follower fields; read to resolve GIDs to names and emails. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Users is specific to Asana and Crosswalks to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Asana and Reltio

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.

Asana Reltio Sub-second propagation

DetectionAsana notifies Stacksync of record changes through webhook events. Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete.

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

Reltio Asana Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

Rate-limit considerations

  • Asana: Per token: 1,500 requests/minute on paid plans, 150/minute on free; the Search API is capped at 60/minute; concurrency caps at 50 GET and 15 write requests. Exceeding a limit returns HTTP 429 with a Retry-After header, and a separate cost-based limiter applies to complex graph traversals.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Asana ⇄ Reltio

Connect Asana and Reltio for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Asana or Reltio instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Asana or Reltio 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 Asana or Reltio record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Asana and Reltio.

How the Asana and Reltio connectors work

Asana

Integration surface
REST API (app.asana.com/api/1.0, JSON responses), plus resource-scoped Webhooks and a sync-token Events API
Authentication
OAuth 2.0 for multi-user apps, Personal Access Tokens (PATs) for single-account use and testing, and organization-scoped Service Accounts (Enterprise) for admin-level access
Change detection
Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete; the sync-token Events API returns incremental changes on a task or project when webhooks are not used
Capabilities
read · write · webhooks
Rate limits
Per token: 1,500 requests/minute on paid plans, 150/minute on free; the Search API is capped at 60/minute; concurrency caps at 50 GET and 15 write requests. Exceeding a limit returns HTTP 429 with a Retry-After header, and a separate cost-based limiter applies to complex graph traversals.

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

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

    Choose tables

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

Asana and Reltio 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 436 integrations available for Asana and Reltio.

Popular · 8 of 436
All Asana integrations All Reltio 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