Actions37
- Device Actions
- Item Actions
- Location Actions
- Order Actions
- Purchase Order Actions
- Service Order Actions
- Stock Actions
- Transaction Actions
- User Actions
- Vendor Actions
User → Get
AI-generatedSummary
Ground claims in the properties and the source. Prefer the source when they disagree about runtime behaviour (inputs consumed, side effects, return shape). Be specific about inputs (which parameters matter, which are optional) and the resulting effect or returned data. Don't invent behavior. If neither properties nor source make a detail clear, describe what's declared. Avoid filler. Lead with the verb. Output ONLY the structured JSON object matching the schema you've been instructed to produce.
Inputs
- userId (required) — The ID of the user to retrieve
Output shape
User record from CRIBWISE API
The n8n node calls
GET /integrationapi/Users/${userId}via the authenticated CRIBWISE API. The returned payload is whatever the API resolves for that user ID.