KamoCRM + Rippling

Approved KamoCRM hours into Rippling payroll, per legal entity

Rippling logo
Start freeBook a demoView Pricing

Overview

Rippling holds the employment record; KamoCRM holds the hours. Connecting them pushes approved timecards to Rippling for the open pay period, syncs the employee directory with work-email matching, and reads back pay periods and PTO balances so leave figures agree across the two systems. Rippling connects either through OAuth or with an API token, whichever your account is set up for, and the sync can be scoped to one legal entity — useful when Rippling holds several and only one is in scope for the CRM.

Common use cases

Approved hours into the open pay period

Timecards that clear approval push to Rippling automatically, so the pay run is not waiting on a manual export.

Scoped to the right legal entity

Point the sync at a single legal entity, or leave it across all of them, depending on how your Rippling account is structured.

Directory matched on work email

Employees sync from Rippling and match on work email, so a hire added in Rippling appears in KamoCRM without a second entry.

Leave balances that agree

PTO balances read from Rippling, so what an employee sees when requesting time off is what payroll is holding.

Setup

  1. 1Open Settings → HR → Payroll Provider Setup in KamoCRM
  2. 2Choose Rippling and pick the connection mode — OAuth or API token
  3. 3Authorize in Rippling, or paste the API token if you are using one
  4. 4Confirm the company; it is detected when you connect
  5. 5Choose the legal entity to sync, or leave it across all of them
  6. 6Match KamoCRM members to Rippling employees; email matching does most of this
  7. 7Map your earning codes to Rippling's
  8. 8Run the connection test, then push one pay period to confirm

What data syncs

Approved time entries, pushed per pay period
Time entries pulled back from Rippling for reconciliation
Employee directory with work-email matching
Pay period calendar
PTO balances

Questions about Rippling

OAuth or API token — which should we use?
OAuth where your Rippling account supports it, since there is no secret to store or rotate. The API token mode exists for accounts that are provisioned that way.
We have several legal entities. Does it sync all of them?
Your choice. Leave the setting empty to cover all entities, or name one to scope the sync to it.
Does it push job costing?
Not currently. Rippling receives the approved hours, the employee, and the pay period. Labor allocation is pushed for the vendors whose APIs accept it — ADP, BambooHR, Dayforce, Gusto, Paycor, Paylocity, UKG, and Workday.
What happens to an unmapped earning code?
The sync reports it as a configuration issue and names the code rather than dropping the hours. Map it once and re-run the period.
Can we verify the connection before pushing anything?
Yes. The connection test checks credentials and company access without writing, and you can push a single pay period before switching over fully.

More integrations like Rippling

ADP Workforce NowPush approved KamoCRM timecards into ADP Workforce NowBambooHRApproved KamoCRM timecards and directory sync with BambooHRDayforceApproved KamoCRM hours into your Dayforce namespaceGustoSend approved KamoCRM timecards straight to Gusto payroll

Connect Rippling with KamoCRM — free forever. No credit card required.

Start free

Ready to connect Rippling?

Start your free KamoCRM account and connect in minutes.

Start freeSee all integrations