Authenticate requests with your Snapshots API credentials. The connection requires the saas/location.read scope to access location data.
Clockify must authorize access to the Snapshots API using your token or OAuth flow. Set up credentials in both apps to establish a secure link.
The integration uses endpoints like GET /locations to fetch location data. Other endpoints may be used as needed; check the API docs for the full list.
Trigger: when a new location is added in Clockify, pull the updated list from Snapshots API.
Actions: fetch locations via GET /locations and map fields such as location_id and location_name into Clockify records.
GET /locations
location_id, location_name, address
Trigger: new time entries in Clockify update Snapshots API.
Actions: pull time entries via GET /time_entries and map to Snapshots fields.
GET /time_entries
time_entry_id, start_time, end_time, task_id, project_id
Trigger: user or project changes in Clockify propagate to Snapshots.
Actions: fetch users GET /users and fetch projects GET /projects and map fields.
GET /users, GET /projects
user_id, email, role; project_id, project_name
Automate data syncing between Clockify and Snapshots API without writing code.
Reduce manual data entry and errors by linking time tracking and location data.
Accelerate reporting with unified dashboards across apps.
A quick glossary of terms used in this integration and how they relate to Clockify and Snapshots API.
API stands for Application Programming Interface. It defines how software components talk to each other.
A webhook is a published endpoint that sends real-time data to another app when a defined event occurs.
OAuth is an authorization framework that uses tokens to grant access without sharing passwords.
An endpoint is a specific URL in an API where you can request data or perform actions.
Enrich Clockify reports by pulling analytics from Snapshots API to reveal project performance
Combine Clockify and Snapshots data into a single dashboard for smarter decisions
Set up alerts when key metrics change, such as new time entries or location updates
Register your Snapshots API credentials and Clockify access in their dashboards to enable the connection.
Enter the API base URL, select the saas/location.read scope, and authorize the app.
Run tests in a sandbox environment, then enable live syncing once everything passes.
Snapshots API provides programmatic access to your data and endpoints that Clockify can consume. It is designed to be secure and easy to connect. Using the saas/location.read scope lets you pull location data safely and synchronize it with Clockify to improve reporting.
No deep coding knowledge is required for many no code connectors. You can start with guided steps and test the connection in a sandbox. If your use case needs custom logic, you can add simple scripts or use the API with tokens to tailor mappings.
You can sync location data, time entries, users and projects between Clockify and Snapshots. The exact fields you map depend on your workspace, but common objects include locations, time entries, users and projects.
Credentials typically include a Snapshots API key or OAuth token and a Clockify access token. Keep credentials secure and rotate keys regularly according to your security policy.
The integration uses secure HTTPS connections and token based access. The scope saas/location.read defines what data can be read. Always follow best practices for credential storage and rotation.
Yes, you can map fields to align with Clockify projects and tasks. Most mappings are configurable in the connector settings and can be adjusted as your workflow evolves.
If authentication fails, verify that your tokens are valid, the correct scopes are granted, and the API base URL is accurate. Reauthorize if needed and re-run the test.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
