Real-time
Two-way sync
Changes in Atlassian or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Human resources
Atlassian to Smartrecruiters integration — real-time, two-way sync
Keep Atlassian 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.
- 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 Atlassian and Smartrecruiters
Keep the people, teams, and status that Atlassian and Smartrecruiters share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Atlassian 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 Jira Projects, Boards and Sprints, Issue Comments, Attachments in Atlassian 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 Atlassian within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Atlassian 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.
Common use cases
- 01 Mirror Jira projects into a SQL database for engineering throughput and SLA reporting.
- 02 Create Jira issues from records in other systems, such as onboarding tasks generated from a closed-won CRM deal.
- 03 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update hiring status, tags, and custom fields in SQL while recruiters keep working in SmartRecruiters.
- 04 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.
Common sync patterns
Onboarding: access ready on day one
A new hire recorded in Smartrecruiters creates the matching user in Atlassian with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Smartrecruiters, the matching account in Atlassian is deactivated or flagged, so departures do not leave open access behind.
One employee directory
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.
What you can sync between Atlassian and Smartrecruiters
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.
| Atlassian objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Custom Fields Instance-specific fields (customfield IDs) that carry most business-specific data in syncs. | 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). | Custom Fields is specific to Atlassian and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Workflows and Statuses Status transitions mapped to stages in the paired system. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Workflows and Statuses is specific to Atlassian and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Users and Groups Assignees and reporters matched to identities in other tools. | Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). | Users and Groups is specific to Atlassian and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Confluence Pages Documentation content readable and writable through the Confluence REST API. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Confluence Pages is specific to Atlassian and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Confluence Spaces Namespaces that scope page syncs and permissions. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Confluence Spaces is specific to Atlassian and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Jira Issues The central work item, synced two-way with CRMs, support desks, and other trackers. | 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. | Jira Issues is specific to Atlassian and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Atlassian and Smartrecruiters
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.
Atlassian Smartrecruiters Sub-second propagation
DetectionAtlassian notifies Stacksync of record changes through webhook events. Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Atlassian Sub-second propagation
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 Atlassian through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with Atlassian ⇄ Smartrecruiters
Connect Atlassian and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Atlassian–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Atlassian or Smartrecruiters 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 Atlassian or Smartrecruiters record.
Observability
Monitoring
Track your Atlassian ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Atlassian and Smartrecruiters.
How the Atlassian and Smartrecruiters connectors work
Atlassian
- Integration surface
- REST APIs per product (Jira Cloud and Confluence Cloud)
- Authentication
- OAuth 2.0 (3LO) for apps or API tokens with basic auth for scripts
- Change detection
- Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill
- Capabilities
- read · write · webhooks
Smartrecruiters
- Integration surface
- SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions
- Authentication
- X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions
- Change detection
- 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.
- Capabilities
- read · write · webhooks
- Rate limits
- Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
How it works
How to connect Atlassian to Smartrecruiters — 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.
- 01
Connect your apps
Authenticate Atlassian 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.
Atlassian
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Atlassian 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.
objects · Atlassian ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Atlassian SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Atlassian and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Atlassian and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Atlassian's Custom Fields and Workflows and Statuses), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Atlassian and Smartrecruiters records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Atlassian and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Atlassian–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Atlassian and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Atlassian: Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill. 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 Atlassian side: Jira Projects, Boards and Sprints, Issue Comments, Attachments, plus custom fields where Atlassian exposes them. On the Smartrecruiters side: Interviews, Offers, Users, Approvals. Stacksync auto-detects both schemas and converts types between the two systems.
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
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 444 integrations available for Atlassian and Smartrecruiters.
Popular · 8 of 444
-
Atlassian ⇄ Ukg Pro -
Atlassian ⇄ Greenhouse -
Atlassian ⇄ Jobvite -
Atlassian ⇄ Lever -
Smartrecruiters ⇄ Zendesk -
Smartrecruiters ⇄ Campfire -
Smartrecruiters ⇄ Front -
Smartrecruiters ⇄ Amazon Seller Central
No integrations match .
