Access is secured with an API key or OAuth token scoped to businesses.readonly. Keep credentials safe, rotate regularly, and apply the least privilege principle.
To authorize requests from 123FormBuilder, configure your GHL credentials in the integration setup. Treat all credentials as sensitive and store them securely.
GET /businesses – list all businesses; GET /businesses/{businessId} – retrieve a single business; POST /businesses – create a new business; PUT /businesses/{businessId} – update a business; DELETE /businesses/{businessId} – delete a business. Scope: businesses.readonly.
Trigger: form loads to populate dropdowns with current businesses.
Actions: fetch list of businesses and populate form fields or dropdowns.
METHOD PATH: GET /businesses
Key fields: id, name, industry, city
Trigger: user selects a specific business in a form.
Actions: retrieve a single record and prefill form fields.
METHOD PATH: GET /businesses/{businessId}
Key fields: id, name, contact, address
Trigger: form submission creates or updates a business record.
Actions: use POST to create and PUT to update existing records.
METHOD PATH: POST /businesses and PUT /businesses/{businessId}
Key fields: name, contact, description, status
No coding required to connect forms with your business data; data sync happens automatically.
Automate workflows and trigger actions in connected apps when a form is submitted or a business record changes.
Fast setup with ready to use blocks and clear mappings between form fields and API fields.
This glossary covers endpoints, authentication methods, request and response formats, and data mappings used to connect GHL with 123FormBuilder.
Application Programming Interface: a defined interface that allows apps to communicate by sending requests and receiving responses.
A specific URL in an API that performs a defined action, such as listing or updating data.
The process that proves identity and grants access to API resources, typically via API keys or OAuth tokens.
GET, POST, PUT, DELETE are the verbs used to perform actions on resources.
Auto fill form fields with the latest business data from the GHL API when a form loads to reduce manual entry.
Push new form submissions to your CRM via the API to keep records up to date.
Trigger downstream workflows in other apps when business data changes or new records are created.
In the GHL developer portal create or select an application to obtain the client ID and secret or an API key.
In 123FormBuilder select endpoints like GET /businesses and map fields to your form fields.
Run test submissions to verify data flow, then enable the integration for live use.
You can access the integration using standard API authentication methods such as API keys or OAuth tokens. Ensure the token or key has the appropriate scope, typically businesses.readonly for read operations. Keep credentials secure and rotate them on a regular schedule. When setting up, apply the least privilege principle to minimize risk.
For basic read access use GET /businesses to list records. For read and write operations you may also use POST /b usinesses to create new records and PUT /businesses/{businessId} to update existing ones. Ensure you map only the fields you need for your forms and validate responses.
Most of this integration is no code and can be accomplished in the 123FormBuilder UI. Some advanced mappings may require light configuration, but no custom coding is necessary to get started.
Field mapping is done in the integration settings. Select the API fields such as id, name, and contact, and map them to the corresponding form fields. Validate with test submissions to ensure data flows correctly.
The API enforces reasonable rate limits. If you exceed them you may receive a 429 response. Plan requests, use batching where possible, and stagger high frequency calls during peak usage.
Yes, you can update existing business records using PUT /businesses/{businessId}. You can also create new records with POST /businesses. Ensure you pass the required fields and keep data synchronized with forms.
If authentication fails, verify credentials, check the token scope, confirm the correct endpoint, and reauthorize if needed. Review your integration settings and consult logs for detailed error messages.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
