Two-way sync
Changes in Asana or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Asana and Smartrecruiters in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Each tool in Asana keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Smartrecruiters is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Stories, Users, Portfolios, Tags in Asana with Interviews, Offers, Users, Approvals in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in Asana within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Asana captures details of its own, such as a corrected contact or a login identity, those can flow back to Smartrecruiters in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
A new hire recorded in Smartrecruiters creates the matching user in Asana with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
When someone is marked as leaving in Smartrecruiters, the matching account in Asana is deactivated or flagged, so departures do not leave open access behind.
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
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 | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Users Members of a workspace or organization referenced by assignee and follower fields; read to resolve GIDs to names and emails. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Projects is specific to Asana and Candidates to Smartrecruiters — 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. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Sections is specific to Asana and Applications to Smartrecruiters — 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. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Custom fields is specific to Asana and Jobs to Smartrecruiters — 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. | Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Stories is specific to Asana and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Portfolios Collections of Projects for program-level rollup; read for cross-project status and progress reporting (Business and Enterprise). | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Portfolios is specific to Asana and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. |
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.
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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
DeliveryEach detected change is written to Asana through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Asana–Smartrecruiters connection.
Changes in Asana or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Asana or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Asana or Smartrecruiters record.
Track your Asana ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Asana and Smartrecruiters.
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.
Authenticate Asana and Smartrecruiters with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Asana and Smartrecruiters 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Asana and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Asana's Users and Projects), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Asana and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Asana: 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. On Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Asana side: Stories, Users, Portfolios, Tags, plus custom fields where Asana exposes them. On the Smartrecruiters side: Interviews, Offers, Users, Approvals. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Asana and Smartrecruiters: Onboarding: access ready on day one; Offboarding: no standing access after a departure; One employee directory. A new hire recorded in Smartrecruiters creates the matching user in Asana with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 511 integrations available for Asana and Smartrecruiters.