Reference · built on requestConnectorHR, scheduling & workforce

Connecteam

Users, time clock activity, scheduler shifts, forms, tasks, and time off from Connecteam, with webhooks.

Request accessPricing ↗

About

Connecteam is an employee app for deskless teams that combines a time clock, shift scheduler, forms, tasks, chat, and onboarding in one workspace. Its REST API, available on the Expert plan or higher, exposes users, time clocks and their time activities, schedulers and shifts, forms and submissions, task boards, time off requests, jobs, pay rates, and sales data, with webhooks for time activity, users, shifts, forms, tasks, and chat.

Through Fibric, an operator listens for clock_in, clock_out, and shift events, reads the affected records, and proposes a shift, a time-off decision, or a task for your approval. Approved changes are applied once, and each leaves a receipt of what changed and why.

This is a reference listing. It documents what Fibric would read from Connecteam and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Users with userType, isArchived, customFields, and smartGroupsIds through GET /users/v1/users, filtered by modifiedAt
  • Time clocks and their time activities through GET /time-clock/v1/time-clocks/{timeClockId}/time-activities, plus timesheet totals
  • Shifts for a scheduler through GET /scheduler/v1/schedulers/{schedulerId}/shifts, with shift custom fields
  • Form submissions filtered by user and submission timestamp through GET /forms/v1/forms/{formId}/form-submissions
  • Tasks on a task board through GET /tasks/v1/taskboards/{taskBoardId}/tasks and time off requests through GET /time-off/v1/requests
  • Webhook events such as clock_in, clock_out, user_timesheet_approved, shift_created, shift_updated, form_submission, and task_completed

Proposed actions

  • Target capability: propose shifts through POST /scheduler/v1/schedulers/{schedulerId}/shifts, up to 500 per call, or an update through PUT
  • Target capability: propose a time-off decision by updating status on PUT /time-off/v1/requests/{requestId}
  • Target capability: propose a task through POST /tasks/v1/taskboards/{taskBoardId}/tasks
  • Target capability: propose a time activity correction through PUT /time-clock/v1/time-clocks/{timeClockId}/time-activities
  • Target capability: propose manager field updates on a form submission through PUT /forms/v1/forms/{formId}/form-submissions/{formSubmissionId}

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Respond to a missed clock-in

    A shift_created record with no matching clock_in event by the start time is a no-show signal. The operator proposes a message to the manager and an open shift to cover it.

    With No-Show Response, Missed Punch

  • Offer an open shift to the right people

    When a shift loses its assignee, the operator reads users by smart group and proposes the offer list and the shift update for the scheduler to approve.

    With Open Shift Offer

  • Close the timesheet on time

    user_timesheet_approved and admin_day_locked events show which timesheets are still open. The operator proposes reminders and lists the time activities a manager must still review.

    With Timesheet Signoff

  • Track onboarding packs to completion

    Onboarding pack assignments and form submissions show who has finished each step. The operator proposes the next task for each new hire and flags overdue packs.

    With Onboarding Checklist

Requirements

  • A Connecteam account on the Expert plan or higher, where API access is available
  • An account Owner to create webhooks, either under Settings → API & Integrations or through the webhook API
  • OAuth scopes chosen at app creation, such as users.read, schedule.write, and time_clock.write; they cannot be edited afterward
  • The base URL for your region: api.connecteam.com, or api-au.connecteam.com for Australian accounts
  • An HTTPS endpoint that answers webhook deliveries within 10 seconds
Authentication
An API key sent in the X-API-KEY header, or an OAuth 2.0 client-credentials app created under Integration Center → OAuth 2.0 whose access tokens last 24 hours.

Limits

  • Rate limits are per account, not per key: Expert allows 100 requests per minute and 10,000 per day; Enterprise 200 and 20,000
  • Webhook deliveries are retried up to 3 times with the same requestId, so receivers must deduplicate on requestId, eventType, and entity
  • Bulk shift deletes take up to 20 shifts per call; list endpoints page with limit and offset
  • Form submission updates change manager fields only; employee answers cannot be edited through the API

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Connecteam ↗

Questions and answers

Which plan includes the Connecteam API?
API access is available on the Expert plan or higher. Rate limits scale by plan and apply per account rather than per key: Expert allows 100 requests per minute and 10,000 per day, and Enterprise allows 200 per minute and 20,000 per day.
Does Connecteam send webhooks?
Yes. An account Owner can add a webhook under Settings → API & Integrations or through the API. Events cover time activity, form submissions, users, scheduler shifts, tasks, and chat. Deliveries carry a requestId, may retry up to 3 times, and are signed with x-webhook-secret when a secretKey is set.
Can the API clock a user in or out?
Yes. POST /time-clock/v1/time-clocks/{timeClockId}/clock-in and /clock-out clock a user in real time, and manual breaks can be started and ended the same way. Through Fibric these run only as proposals that a person approves first.
Ask about Connecteam

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Connecteam through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy