CONNECT APP
Build with Rippling
Human Resources
- API key
MCP
Give your agent Rippling tools
Every Rippling action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Rippling account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "rippling",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Get User:
const result = await mcp.callTool({
name: "rippling-get-user",
arguments: {
userId: "User ID",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "rippling",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Get User:
result = await session.call_tool("rippling-get-user", {
"userId": "User ID",
})API PROXY
Call the Rippling API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Rippling API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://rest.ripplingapis.com",
})
// Any allowed Rippling endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://rest.ripplingapis.com
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9yZXN0LnJpcHBsaW5nYXBpcy5jb20?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Rippling actions from your backend
Connect a user's Rippling account once, then run Get User on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "rippling-get-user",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
rippling: { authProvisionId: "apn_xxxxxxx" },
userId: "User ID",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="rippling-get-user",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"rippling": {"authProvisionId": "apn_xxxxxxx"},
"userId": "User ID",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "rippling-get-user",
"configured_props": {
"rippling": { "authProvisionId": "apn_xxxxxxx" },
"userId": "User ID"
}
}'TOOLS
Rippling actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Get User
actionRetrieves a specific user from Rippling. See the documentationRead-onlyv0.0.2 -
List Companies
actionRetrieves a list of all companies from Rippling. See the documentationRead-onlyv0.0.2 -
List Teams
actionRetrieves a list of all teams from Rippling. See the documentationRead-onlyv0.0.2 -
List Workers
actionRetrieves a list of all workers from Rippling. See the documentationRead-onlyv0.0.2
EVENTS
Rippling triggers
Event sources your backend can deploy for users and receive through a webhook.
MULTI-APP
Use Rippling with other popular apps
Most products don't stop at one integration. Pair Rippling with the other apps your users rely on, and ship use cases that span both.
- App slug
- rippling
- Authentication
- API key
- Categories
- Human Resources
- Actions
- 4
- Triggers
- 1
- API proxy
- Available