Deel ACTION
Create Shifts
Create one or more time tracking shifts for a GP (Global Payroll) contract in Deel. Each shift records worked time with a date, duration, and associated shift rate.
shifts must be a JSON array of shift objects. Each shift requires: description (string), external_id (your unique ID), shift_type (REGULAR, CORRECTION_ABSOLUTE, or CORRECTION_DELTA), date_of_work (ISO 8601 date), summary.time_unit (HOUR or DAY), summary.time_amount (number), summary.shift_rate_external_id (the external_id from Create Shift Rate). Example: [{"description": "Regular work", "external_id": "shift-001", "shift_type": "REGULAR", "date_of_work": "2026-07-15", "summary": {"time_unit": "HOUR", "time_amount": 8, "shift_rate_external_id": "rate-overtime-001"}}] Use List Contracts to find the contract ID. See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Deel account once, then configure and run Create Shifts from your backend or agent.
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: "deel-create-shifts",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
deel: { authProvisionId: "apn_xxxxxxx" },
contractId: "Contract ID",
shifts: "Shifts",
},
})
console.log(result)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": "deel-create-shifts",
"configured_props": {
"deel": { "authProvisionId": "apn_xxxxxxx" },
"contractId": "Contract ID",
"shifts": "Shifts"
}
}'// 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": "deel",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "deel-create-shifts",
arguments: {
contractId: "Contract ID",
shifts: "Shifts",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
contractId Contract ID | string | The unique identifier of the Deel contract. Use List Contracts to find contract IDs. Required |
shifts Shifts | string | JSON array of shift objects. Each must include description, external_id, shift_type (REGULAR|CORRECTION_ABSOLUTE|CORRECTION_DELTA), date_of_work, and summary (with time_unit, time_amount, shift_rate_external_id). Example: [{"description": "Regular work", "external_id": "shift-001", "shift_type": "REGULAR", "date_of_work": "2026-07-15", "summary": {"time_unit": "HOUR", "time_amount": 8, "shift_rate_external_id": "rate-overtime-001"}}] Required |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- deel-create-shifts
- Version
- 0.0.2
- App
- Deel
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗