Actions21
- Lead Actions
- Client Actions
- Check-in Actions
- Webhook Actions
Check-in → Get by Client
AI-generatedSummary
Fetches check-ins submitted by a single Brixfit client via GET /api/public/v1/checkins filtered by client_id, with optional status, date range and pagination filters.
Inputs
- Client ID (required) — ID of the client whose check-ins to fetch. Must be a plain ID (letters, numbers, hyphens, underscores, up to 128 chars); otherwise the node errors. Sent as the client_id query parameter.
- Options > Status — Filter by check-in status: All (no filter), Completed, Pending or Reviewed.
- Options > From Date — Start date filter in YYYY-MM-DD format. Omitted if empty.
- Options > To Date — End date filter in YYYY-MM-DD format. Omitted if empty.
- Options > Page — Page number to request (UI default 1).
- Options > Per Page — Results per page (UI default 20).
Output shape
One output item per check-in returned by the API (the response's data array is unpacked), each linked to the input item that produced it. If the API returns a single object instead of an array, one item is emitted.
Returns only a single page per input item; there is no automatic pagination or Return All here, so use Page and Per Page to step through results. Only options that are set and non-empty are sent. With Continue on Fail enabled, failures yield an item with an error message instead of stopping the workflow. Runs once per input item.
Examples
Example 1: Pull a client's pending check-ins for review
Client ID = {{ $json.clientId }}; Options: Status = Pending
Example 2: Get a client's check-ins for January 2026
Client ID set; Options: From Date = 2026-01-01, To Date = 2026-01-31, Per Page = 50