Connect Chekku to your stack with REST API, webhooks, Workflows, and connectors.

Audience: Admin · Developer

Chekku exposes field data to external systems through a REST API, webhooks, optional connectors, and first-party Workflows. Choose the path that matches who maintains the integration and how real-time the sync must be.

REST API

The Chekku REST API lets authenticated clients:

Read and write places, users, visits, form submissions, and tasks (scopes vary by endpoint and plan).
Query paginated lists with filters (date, team, place).
Attach files where endpoints support multipart upload.

Authentication typically uses API keys or OAuth-style tokens issued from your Chekku workspace settings. Rotate keys on the same schedule as other production secrets.

Full reference: Chekku API docs — OpenAPI-style documentation with request schemas and examples. Start with read-only calls against a sandbox visit before writing data.

Webhooks

Webhooks push HTTP POST payloads to your URL when events occur—visit completed, form submitted, task updated, etc.

Good for	Less ideal for
ERP / CRM ingestion in real time	Simple "create task when form X submits" inside Chekku
Data warehouse staging	Ad-hoc email without a server
Custom validation pipelines	Non-technical admin maintenance

You must operate a reachable HTTPS endpoint, verify signatures (when provided), and handle retries idempotently.

Workflows vs. webhooks for form submit

When a mobile user submits a form, two patterns compete:

Prefer Workflows when

The next step stays inside Chekku (task, workflow record, notification).
Admins need to change routing without deploying code.
You want filters on form answers and visit type in the UI.

Trigger: form_submitted. See Automations on form submit.

Prefer webhooks when

An external system must receive every payload immediately (SAP, Salesforce, custom middleware).
You already operate integration infrastructure with monitoring and dead-letter queues.

Avoid duplicating both for the same event unless you explicitly need dual delivery—otherwise debugging which system created a task becomes painful.

Data Sources and external catalogs

Data Sources sync catalog rows from Google Drive, Sheets, Excel uploads, SQL, SAP, and other connectors (availability varies). Forms consume catalogs through List fields—not through ad-hoc API calls on each tap.

Office maintains catalogs; mobile reads synced copies. See Data Sources.

Connectors and tailored integrations

Beyond generic API/webhooks, Chekku and partners may offer prebuilt connectors for specific ERP or BI tools. Direct logo integrations on the marketing site indicate direction; confirm availability and plan with your account team before project planning.

Security checklist

Store API keys in a secrets manager, not in mobile apps or public repos.
Restrict webhook endpoints with TLS 1.2+, IP allow lists if supported, and payload verification.
Log correlation IDs from Chekku payloads when opening support tickets.
Minimize PII exported to third parties to what the use case requires.

Tips

Prototype with read-only API calls, then enable writes.
Map field keys before building BI models (Field keys and API).
Document which system owns master data for places vs. Chekku.
For reporting-only needs, Excel export may suffice—API is not mandatory.

Integrations overview