Authenticate using your API credentials and the surveys.readonly scope to securely access endpoints from Timetonic.
Authorize Timetonic to access the Workflows API with your app credentials and securely store tokens for ongoing requests.
GET /surveys/ — List surveys GET /surveys/submissions — Retrieve survey submissions Other endpoints are available in the API docs but not required for this page.
Trigger: when you need an up to date list of surveys.
Actions: create or update survey records in Timetonic and map key fields.
GET /surveys/
survey_id, title, status, created_at
Trigger: on new survey submissions or at scheduled intervals.
Actions: ingest submissions into Timetonic and compute response metrics.
GET /surveys/submissions
survey_id, submission_id, respondent, answers, submitted_at
Trigger: when a respondent submits data that meets criteria.
Actions: push updates to Timetonic records or notify teams.
N/A (Webhook endpoint configured in Timetonic)
N/A
Automate data flow without writing a line of code in your stack.
Turn survey responses into actionable insights in Timetonic dashboards instantly.
Scale data workflows with simple, repeatable setups.
This section explains the main data elements and the flow between GHL Workflows API and Timetonic, including surveys, submissions, respondents, and mappings.
A structured set of endpoints that allow apps to request and exchange data.
A secure authorization standard that grants tokens to access APIs on behalf of a user.
A callback URL that triggers when specified events occur in an app.
Defining how fields in one system align with fields in another when data moves between apps.
Set up live dashboards in Timetonic that refresh as survey data arrives via GET /surveys and GET /surveys/submissions.
Automate exports of survey results to spreadsheets or BI tools from Timetonic when new submissions are posted.
Trigger alerts in your team channels when responses meet predefined criteria.
Obtain your API key and set the surveys.readonly scope, then store securely.
Authorize Timetonic with the API credentials and run test calls to GET /surveys/ and GET /surveys/submissions.
Define field mappings between surveys and Timetonic records and enable automated workflows.
Use OAuth or API key based authentication as defined by your GHL account. Ensure you grant the surveys.readonly scope and securely store credentials. Test the connection with GET /surveys/ to verify access. Follow security guidelines to rotate credentials regularly.
The essential endpoints for this page are GET /surveys/ and GET /surveys/submissions. These endpoints provide survey definitions and responses which Timetonic can ingest and catalog. Other endpoints exist in the API but are not required for the core flow described here.
Yes, many more endpoints exist for various data operations. You can explore the full endpoint set in the API docs and enable additional actions as needed.
Data is transmitted over HTTPS and tokens are stored securely. Use least privilege access and rotate credentials. Timetonic can store access tokens securely and limit endpoint access per user.
The surveys.readonly scope allows reading survey data and submissions. It does not permit creating or editing surveys from Timetonic.
Map fields by aligning source fields like survey_id, title, and answers to Timetonic fields in your templates or records. Use transformation rules to normalize formats if needed.
Refer to the API rate limits in your GHL account or the API docs. Design calls with batching, caching, and exponential backoff to stay within limits.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
