Skip to main content
Hellotracks no-code connectors use a REST API under /v1. This API is designed for automation tools such as Zapier, Make, and n8n. No-code endpoints use REST methods, query strings for filters, and JSON request bodies for create and update actions.

Base URL

Use the production base URL above for public Zapier, Make, and n8n workflows.

Authentication

Create an API key in Hellotracks under More -> API & Integrations. Send the key in the API-Key header.
All connector requests use JSON and include:

Response Format

List and action responses return a data object. Most connector endpoints return an items array inside data.
Connector packages unwrap data.items before returning records to Zapier, Make, or n8n.

Error Format

Failed requests may return an error object. Treat error.message as the user-facing failure reason.
Common HTTP statuses:

Authentication Test

Use this endpoint to validate that an API key works.
Example:

Jobs

Watch or list jobs

Use GET /jobs for polling triggers, job dropdowns, and lookup flows.
Query parameters: Examples:

Get a job

Use GET /jobs/{id} when you already have the Hellotracks job ID.
Example:

Create a job

Use POST /jobs to create a job. If externalId matches an existing job, Hellotracks uses it as a stable dedupe key and may update the existing job.
Request body:
Supported connector fields:

Update a job

Use PATCH /jobs to update an existing job. Send the Hellotracks job id in the JSON body and include only the fields you want to change.
Request body:

Archive a job

Use archive when the job should no longer appear in active schedules but should remain recoverable in Hellotracks.
Example:

Delete a job

Use delete only for disposable or intentionally removed jobs.
Example:

Job Object

Connector responses include stable job fields.

Members

Use members for assignment lookups, dropdowns, and exact-match searches.
Query parameters: Example:
Member response fields:

Connector Behavior

Zapier, Make, and n8n use the same production /v1 contract: