CONNECT APP
Build with Gem
Human Resources
- API key
MCP
Give your agent Gem tools
Every Gem 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 Gem 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": "gem",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Candidate:
const result = await mcp.callTool({
name: "gem-create-candidate",
arguments: {
createdBy: "Created By",
firstName: "First Name",
},
})# 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": "gem",
}
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 Create Candidate:
result = await session.call_tool("gem-create-candidate", {
"createdBy": "Created By",
"firstName": "First Name",
})API PROXY
Call the Gem API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Gem 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://api.gem.com/v0/users",
})
// Any allowed Gem 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://api.gem.com/v0/users
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZ2VtLmNvbS92MC91c2Vycw?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Gem actions from your backend
Connect a user's Gem account once, then run Create Candidate 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: "gem-create-candidate",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
gem: { authProvisionId: "apn_xxxxxxx" },
createdBy: "Created By",
firstName: "First Name",
},
})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="gem-create-candidate",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"gem": {"authProvisionId": "apn_xxxxxxx"},
"createdBy": "Created By",
"firstName": "First Name",
},
)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": "gem-create-candidate",
"configured_props": {
"gem": { "authProvisionId": "apn_xxxxxxx" },
"createdBy": "Created By",
"firstName": "First Name"
}
}'TOOLS
Gem actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
MULTI-APP
Use Gem with other popular apps
Most products don't stop at one integration. Pair Gem with the other apps your users rely on, and ship use cases that span both.
- App slug
- gem
- Authentication
- API key
- Categories
- Human Resources
- Actions
- 3
- Triggers
- 1
- API proxy
- Available