Obtain your Forms API credentials in GHL and grant 17hats access to read and write form data. Secure tokens are required.
In 17hats, generate an API key or OAuth token to connect to the Forms API and keep it renewed for ongoing access.
Endpoints used: GET /forms/ to list forms; GET /forms/submissions to fetch submissions. Additional endpoints may be used as your integration grows.
Trigger: a new submission is received from a form in Forms API.
Actions: create or update the corresponding contact in 17hats and attach the submission details.
Method path: GET /forms/submissions
Key fields: form_id, submission_id, respondent name, email, and answer values.
Trigger: form is created or updated in Forms API.
Actions: map form fields to 17hats contact fields and create/update records.
Method path: GET /forms/
Key fields: form_id, form_name, fields definitions.
Trigger: scheduled sync (daily/hourly).
Actions: enqueue data for processing, create or update 17hats records, and trigger workflows.
Method path: POST /forms/batch_import
Key fields: batch_id, form_ids, status.
No coding required: use the built-in connectors to authenticate and map fields. If you want more control, you can manage access with API keys and scopes.
Automate lead capture, routing, and follow-ups directly in 17hats.
Create a single source of truth by syncing form data into 17hats.
A quick glossary of API terms, data fields, and processes used to connect GHL’s Forms API to 17hats.
Application Programming Interface; a set of rules that lets apps talk to each other.
A specific URL and method exposed by an API that performs a function.
A protocol for authorizing access without sharing credentials.
The process of verifying identity and granting access tokens.
Automatically create a client profile in 17hats when a form is submitted, initialize tasks and reminders.
Route submissions to the right team in 17hats based on form fields.
Set up templates to follow up with leads after submission.
Obtain credentials in GHL and add them to 17hats; run a test to confirm the connection.
Define which Form fields map to 17hats contact fields and how submissions update records.
Turn on batch sync or real-time triggers and monitor results.
No coding required: use the built-in connectors to authenticate and map fields. If you want more control, you can manage access with API keys and scopes.
For basic sync, you need endpoints GET /forms/ and GET /forms/submissions. You may also use endpoints to fetch form metadata.
Data in transit is secured with TLS. Use OAuth or tokens with least privilege.
Testing is done with sandbox or test credentials. Run a test submission and verify it appears correctly in 17hats.
Yes, field mapping is configurable in the connector. You can customize which fields sync and how they’re transformed.
The system supports retry logic and exponential backoff. If you hit limits, stagger requests and monitor quota.
API keys and tokens are found in GHL and 17hats account settings. Keep them secure and rotate periodically.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
