Authorize requests to the Workflows API using your GHL API key or OAuth tokens. Scope: surveys.readonly.
Connect TeamGantt to the Workflows API by generating an API token in TeamGantt and granting it access to your Workflows API workspace.
GET /surveys/ — Retrieve a list of surveys. GET /surveys/submissions — Retrieve submissions for surveys. (Endpoints 3-17 are not shown on this page.)
Trigger: when a new or updated survey is available, Workflows API pulls the data.
Actions: Create or update TeamGantt tasks from survey data.
GET /surveys/
Key fields: survey_id, title, type, date_created
Trigger: new survey submissions update your records.
Actions: Log submissions, update progress, or trigger follow-ups.
GET /surveys/submissions
Fields: submission_id, survey_id, respondent, answers, submitted_at
Trigger: on-demand or scheduled metadata sync.
Actions: Update metadata in TeamGantt tasks and timelines.
GET /surveys/{id}/metadata
Fields: survey_id, metadata, last_updated
Automate data transfer without writing code.
Speed up project planning by syncing survey insights to TeamGantt tasks.
Centralize data flow for reporting and analytics.
Core elements: endpoints, triggers, actions, and data mapping; Processes: authentication, data retrieval, and sync scheduling.
A specific URL path and HTTP method used to perform a function in an API.
A submission is a respondent’s complete set of answers to a survey.
A collection of questions designed to collect information from respondents.
An event that starts an automation or workflow run.
Automatically generate TeamGantt tasks when survey responses meet certain criteria.
Visualize survey completion in TeamGantt to gauge project momentum.
Use Workflows API to trigger TeamGantt reminders based on responses.
Grant access from TeamGantt to Workflows API by generating an API token and selecting the surveys scope.
Enable GET /surveys/ and GET /surveys/submissions to pull data.
Map survey fields to corresponding TeamGantt fields for accurate sync.
The Workflows API enables no-code automation between surveys and TeamGantt projects. It provides endpoints to retrieve survey data and manage related resources, allowing you to trigger actions in TeamGantt based on survey activity. Authentication is token-based for secure access. You can build automations without writing code.
Yes. The Workflows API supports multiple endpoints. You can combine surveys-related endpoints with others as needed. Check the API docs for a full list of available endpoints.
In many cases you can set this up without coding by using prebuilt automations and webhooks. A basic understanding of API concepts helps, but you can start with the no-code setup and iterate.
All data transfers use HTTPS with token-based authentication. Follow least-privilege access and rotate tokens regularly to maintain security.
This page highlights GET /surveys/ and GET /surveys/submissions. Other endpoints may exist in the API; refer to the official docs for a complete list.
Authenticate using an API key or OAuth token, then authorize the Workflows API to access your TeamGantt data with the surveys scope.
API documentation is available in your GHL developer portal. It provides endpoint details, examples, and usage guidelines.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
