Skip to content
Business productivity ⇄ Human resources

Campfire to Ceridian Dayforce integration — real-time, two-way sync

Keep Campfire and Ceridian Dayforce 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 Campfire and Ceridian Dayforce

Keep the people, teams, and status that Campfire and Ceridian Dayforce share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in Campfire 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. Ceridian Dayforce 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 Invoice, Credit Memo, Bank Account, Bank Transaction in Campfire with Work Assignments, Compensation Summary & Pay Adjustments, Employee Punches & Raw Clock Entries, Employee Schedules in Ceridian Dayforce bi-directionally and in real time. A person added, moved, or offboarded in Ceridian Dayforce creates or updates the matching user in Campfire within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Campfire captures details of its own, such as a corrected contact or a login identity, those can flow back to Ceridian Dayforce 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 Notify a team room when a deal closes, a ticket escalates, or a sync job fails.
  • 02 Route inbound lead or form submissions into the right room via a bot.
  • 03 Two-way sync of Employee and Work Assignment data (position, department, location, org unit) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR keeps editing in Dayforce.
  • 04 Push new hires (Employee, Employment Status, Work Assignment) from an ATS or onboarding tool into Dayforce with POST once a candidate is hired, pre-fetching valid XRefCodes for department, position, location, and pay group.

Common sync patterns

Onboarding: access ready on day one

A new hire recorded in Ceridian Dayforce creates the matching user in Campfire 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 Ceridian Dayforce, the matching account in Campfire 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 Campfire and Ceridian Dayforce

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.

Campfire objects Ceridian Dayforce objects How this pairing syncs
Bank Account Synced with incremental and full sync per the Stacksync docs. Work Assignments Effective-dated position, department, location, and org-unit assignment; the most-synced record for org charts, provisioning, and analytics. Read and updatable via PATCH. Bank Account is specific to Campfire and Work Assignments to Ceridian Dayforce — each maps to any object or custom field on the other side.
Bank Transaction Synced with incremental and full sync per the Stacksync docs. Compensation Summary & Pay Adjustments Compensation Summary returns pay rate and frequency for reporting; Employee Pay Adjustments are written as effective-dated records via PATCH to post pay changes back to Dayforce. Bank Transaction is specific to Campfire and Compensation Summary & Pay Adjustments to Ceridian Dayforce — each maps to any object or custom field on the other side.
Journal Entry Synced with incremental and full sync per the Stacksync docs. Employee Punches & Raw Clock Entries Time-and-attendance punches; raw clock entries are added with POST and punches removed with DELETE, so time data flows both ways between Dayforce and scheduling or workforce tools. Journal Entry is specific to Campfire and Employee Punches & Raw Clock Entries to Ceridian Dayforce — each maps to any object or custom field on the other side.
Intercompany Journal Entry Synced with incremental and full sync per the Stacksync docs. Employee Schedules Shift and schedule assignments; created and updated through POST and PATCH schedule endpoints and paged with pageSize, used to push schedules from a WFM tool or pull them for analytics. Intercompany Journal Entry is specific to Campfire and Employee Schedules to Ceridian Dayforce — each maps to any object or custom field on the other side.
Chart of Accounts Synced with incremental and full sync per the Stacksync docs. Org Units, Departments, Jobs & Positions Configuration reference data; POST creates org units and departments and PATCH updates job, position, department, and org-unit data. Used to resolve and validate XRefCodes when mapping employee writes. Chart of Accounts is specific to Campfire and Org Units, Departments, Jobs & Positions to Ceridian Dayforce — each maps to any object or custom field on the other side.
Chart Transaction Synced with incremental and full sync per the Stacksync docs. Time Away From Work & Balances Time-off requests and accrual balances read per employee; pulled into scheduling, payroll, or absence-reporting databases and used to reconcile leave against downstream systems. Chart Transaction is specific to Campfire and Time Away From Work & Balances to Ceridian Dayforce — each maps to any object or custom field on the other side.

How changes propagate between Campfire and Ceridian Dayforce

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.

Campfire Ceridian Dayforce Sub-second propagation

DetectionCampfire pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking (incremental sync).

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

Ceridian Dayforce Campfire Sub-second propagation

DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.

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

Rate-limit considerations

  • Campfire: Limits depend on the self-hosted deployment; confirm against the instance's documentation.
  • Ceridian Dayforce: Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
What ships with Campfire ⇄ Ceridian Dayforce

Connect Campfire and Ceridian Dayforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Campfire–Ceridian Dayforce connection.

Real-time

Two-way sync

Changes in Campfire or Ceridian Dayforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Campfire or Ceridian Dayforce 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 Campfire or Ceridian Dayforce record.

Observability

Monitoring

Track your Campfire ⇄ Ceridian Dayforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Campfire and Ceridian Dayforce.

How the Campfire and Ceridian Dayforce connectors work

Campfire

Integration surface
HTTP endpoints for bot integrations on a self-hosted instance
Authentication
API key — create an API user with a Super User Role in Campfire (Settings -> API Keys), generate an API Key secret, and provide it in the Stacksync connection setup
Change detection
Near real-time updates via change tracking (incremental sync); delete detection per object (some objects detected every 24h)
Capabilities
read · write · CDC · webhooks
Rate limits
Limits depend on the self-hosted deployment; confirm against the instance's documentation.
Campfire setup guide

Ceridian Dayforce

Integration surface
REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads
Authentication
HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account.
Change detection
No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged.
Capabilities
read · write · webhooks
Rate limits
Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
Ceridian Dayforce setup guide
How it works

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

    Choose tables

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

Campfire and Ceridian Dayforce 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
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 492 integrations available for Campfire and Ceridian Dayforce.

Popular · 8 of 492
All Campfire integrations All Ceridian Dayforce 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