Services/Custom Development

Build on Rippling, not around it.

Custom apps, functions, data pipelines and AI connections built on the Rippling platform, by developers who know App Studio, the API and the MCP server inside out.

Scope a build What we build with

Sample function

Class sign-up action

TypeScriptApp Studio

// Runs when an employee clicks “Sign up”

export default async function signUp(ctx) {

const cls = await ctx.objects.get(

"training_class", ctx.recordId);

if (cls.seats < 1) return ctx.error("Class full");

await ctx.objects.update(cls.id,

{ seats: cls.seats - 1 });

return ctx.ok("You’re booked");

}

Tested in a sandbox firstDeployed as a package

</>

Teams come to us when…

Rippling connects to a lot. When it doesn’t, there’s usually a spreadsheet filling the gap.

01Someone exports and re-keys data every week.

02Your ERP or accounting tool has no native connector.

03You need a workflow Rippling can’t build out of the box.

04An in-house system still needs employee data.

05Reporting needs data Rippling doesn’t hold.

06A past integration breaks and nobody can fix it.

What we build with

Every part of the Rippling platform, used properly.

App Studio

Custom apps inside Rippling

No-code pages for simple tools, or function pages built in code when the logic gets complex.

Custom objects

Your data, in the employee graph

Model vehicles, certifications or projects so they work like native Rippling data in reports and workflows.

Functions

Serverless code that runs in Rippling

JavaScript or TypeScript triggered from app buttons, page loads, workflows or the API.

Workflows

Automations in Workflow Studio

Chain functions together and act on changes to custom objects or employee records.

Transformations

Clean data as it arrives

Reshape pipeline data, like consolidating dozens of training records into one per employee.

Rippling API

REST API and JavaScript SDK

Read and write workforce data from your own systems, with scoped tokens and service accounts.

Sandboxes

Build without touching real data

Isolated Rippling environments seeded with mock data for development and testing.

Packages

Versioned, repeatable releases

Managed packages to publish a version from a sandbox and install it cleanly in production.

Sites

Pages and portals on your data

Branded pages built on Rippling data for the people who need them.

MCP Server

Rippling in Claude, ChatGPT and Cursor

Set up the governed Rippling MCP so AI tools act within each user’s existing permissions.

Rippling AI

Answers from your custom data

Make custom objects and app data available so people can ask questions in plain language.

Not sure which to use? We’ll pick the right tool for the job.Talk to a developer →

How we build

Scoped, built, then supported.

Most builds take two to eight weeks from sign-off to live.

Scope

Define the build

Systems, data, triggers and edge cases written into a spec you sign off.

Your time:1–2 calls

Build

Develop and test

Built against a sandbox, tested with real scenarios, reviewed with you.

Your time:Demo and UAT

Support

Run and maintain

Monitoring, fixes and updates when Rippling or your other systems change.

Your time:None

Custom build or native integration?

We always check for a native Rippling option first. Custom work is for the gaps.

Custom development

Native integration

Consulting

Best for

Systems without a connector

Apps in the Rippling marketplace

Working out what you need

Length

2–8 weeks

Days

Per project

Ongoing

Monitored and maintained

Maintained by vendor

—

Questions we get asked

Can't find what you need? Talk to our team.

What Rippling plan do custom builds need?

Custom objects need Rippling Platform Pro. Functions need Platform Pro or an App Studio custom apps pack. The MCP server needs Rippling AI. We’ll confirm what you have before scoping.

Do you build in our live account?

No. We build and test in a Rippling sandbox with mock data, then publish a versioned package to production.

Can AI tools like Claude use our custom data?

Yes. We set up the Rippling MCP server and access assignments so AI clients work within each person’s Rippling permissions.

Who owns the code?

You do. It lives in your Rippling account, documented, with an optional support plan.