> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking SafetyCulture as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/safetyculture

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The SafetyCulture connector syncs your workplace-operations data – inspections and their answers, templates, corrective actions, issues, assets, users, groups, sites, and schedules – into the PostHog data warehouse, so you can analyze your safety and operations workflows alongside your product data.

## Prerequisites

You need a SafetyCulture account on a **Premium or Enterprise plan** with permission to create an API token. Data feed access follows the token owner's permissions, so SafetyCulture recommends granting the **Data Access** permission for warehouse integrations.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking SafetyCulture, you'll need:

-   **API token** – generate one under **Account settings → Integrations → Manage API tokens** in [SafetyCulture](https://app.safetyculture.com).

API tokens expire after 30 days of inactivity, so SafetyCulture recommends a [service user](https://help.safetyculture.com/en-US/1064186-service-users) token for long-term integrations.

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

Inspections, inspection items, templates, and actions support incremental sync on `modified_at` via SafetyCulture's server-side `modified_after` filter. The other tables are full refresh only.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `inspections` | An inspection (audit) conducted from a template, with its score, timings, and location. | Incremental, Full refresh | modified\_at | — |
| `inspection_items` | A single question/item answered within an inspection, with its response, score, and media. | Incremental, Full refresh | modified\_at | — |
| `templates` | An inspection template that inspections are conducted from. | Incremental, Full refresh | modified\_at | — |
| `actions` | A corrective action, optionally raised against an inspection item, with its priority, status, and assignment context. | Incremental, Full refresh | modified\_at | — |
| `issues` | An issue reported in SafetyCulture, with its category, priority, status, and linked inspection/site. | Full refresh | — | — |
| `assets` | An asset tracked in SafetyCulture, with its type, custom fields, site, and state. | Full refresh | — | — |
| `users` | A user in your SafetyCulture organization. | Full refresh | — | — |
| `groups` | A user group in your SafetyCulture organization. | Full refresh | — | — |
| `sites` | A site (location, area, region, state, or country) in your SafetyCulture organization. | Full refresh | — | — |
| `structures` | A node in the organization's hierarchy (a site or a group), from the Structures API. | Full refresh | — | — |
| `schedules` | A recurring inspection schedule, with its recurrence pattern, template, and site. | Full refresh | — | — |

## Troubleshooting

-   If you see an authentication error, your API token is invalid or has expired – tokens expire after 30 days of inactivity. Generate a new token (ideally for a service user), then reconnect.
-   If you see a permissions error on a specific table, the token's user is missing access to that data feed. Grant the user the **Data Access** permission in SafetyCulture, then reconnect.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.