Linear (API key) ACTION
List Users
List members of the Linear workspace. Use this to discover valid user IDs for assigning issues or initiatives. Returns
{nodes, pageInfo}, where each node includes id, name, and email. If pageInfo.hasNextPage is true, call again with after set to pageInfo.endCursor to fetch more. Example: call with no filters to list all members → returns {nodes: [{id: "abc123", name: "Alice", email: "alice@acme.com"}], pageInfo: {endCursor: "abc123", hasNextPage: false}}. See the documentation.- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Linear (API key) account once, then configure and run List Users 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: "linear_app-list-users",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
linear_app: { authProvisionId: "apn_xxxxxxx" },
first: 10,
after: "After",
},
})
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": "linear_app-list-users",
"configured_props": {
"linear_app": { "authProvisionId": "apn_xxxxxxx" },
"first": 10,
"after": "After"
}
}'// 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": "linear_app",
},
},
},
)
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: "linear_app-list-users",
arguments: {
first: 10,
after: "After",
},
})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 |
|---|---|---|
first First | integer | Maximum number of records to return (min 1, max 100). Example: 10. Optional |
after After | string | Pagination cursor from a previous response's pageInfo.endCursor to fetch the next page. Example: 4919b279-3121-4609-880e-a70c11deca5a. Optional |
includeArchived Include archived | boolean | Should archived resources be included? (default: false) Optional |
fields Fields | string[] | Optional list of field names to include in each returned user object. When omitted, the full user payload is returned. Pass a subset to reduce response size, e.g. ["id", "name", "email"]. Optional |
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
- linear_app-list-users
- Version
- 0.0.1
- App
- Linear (API key)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗