Authenticate your connection using your GHL API credentials and ensure the scope includes objects/schema.readonly for read operations and objects/record.write for write operations.
Authorize the 123FormBuilder app to access your GHL account, using either API keys or OAuth-based flows, and securely store tokens for ongoing requests.
GET /objects/:key; GET /objects; objects/schema.write; objects/record.readonly; GET /objects/:schemaKey/records/:id; objects/record.write; POST /objects/:schemaKey/records; PUT /objects/:schemaKey/records/:id; DELETE /objects/:schemaKey/records/:id
Trigger when a 123FormBuilder form is submitted to instantly create or update a Custom Object record in GHL.
Actions include creating or updating a Custom Object, mapping form fields to object fields.
Method: Use GET to inspect schema, then POST to create and PUT/DELETE to update objects via the API endpoints.
Key fields: objectKey, schemaKey, recordId, formSubmissionId, timestamp
Webhooks notify 123FormBuilder of GHL object events, enabling real-time updates.
Actions: update form submissions, reflect changes in objects, or trigger new records.
Method: configure webhook endpoints in GHL and connect to 123FormBuilder’s listener.
Key fields: event, objectKey, payload, timestamp
Zapier triggers from 123FormBuilder or GHL to orchestrate actions.
Actions: call multiple endpoints, create/update records, and tag with IDs.
Method: use Zapier actions to call GET/POST/PUT/DELETE endpoints as needed with field mapping.
Key fields: zapierKey, mapping, endpointSequence
No development work is required to connect 123FormBuilder with GHL.
Keep data in sync without custom plugins; use built-in history and audit trails.
Scale quickly across many forms and objects with consistent mappings.
A quick glossary of terms used in the integration between GHL and 123FormBuilder.
A named container in GHL for storing related records (custom objects).
Defines the structure of an object: fields, types, and relationships.
A single row of data inside an object.
A URL path to an API operation you can call.
Map each form submission to a new object record for instant capture.
Sync edits back to the object as users update form responses.
Push notifications to teams when objects are created or updated.
Obtain an API key and authorize the connection.
Align 123FormBuilder fields to the Custom Objects schema fields.
Submit test entries and verify data sync across systems.
Security is a priority: all API calls should use HTTPS to encrypt data in transit. Store API keys securely and rotate credentials regularly. Access scopes are limited to the necessary endpoints (read and write for objects and records) to minimize exposure. Regular audits and logging help you monitor activity and detect anomalies.
You’ll typically need read access to objects and write access to records for the most common use cases (GET /objects, POST /objects/:schemaKey/records, PUT /objects/:schemaKey/records/:id, DELETE /objects/:schemaKey/records/:id). Webhooks or Zapier can help you trigger or listen for changes. Always start with the endpoints you explicitly need and expand as your flows mature.
Yes. Webhooks can notify your systems in real time about object events, enabling immediate action in 123FormBuilder or downstream apps. Configure event types you care about and secure the listener with signature verification.
No heavy coding is required. Use the Zapier app connector or built-in form-to-object mappings to connect fields. When necessary, small configuration and field mapping is enough to automate workflows without writing code.
Field mapping involves aligning each 123FormBuilder form field with the corresponding Custom Object field. Use consistent data types and validations. Test with sample submissions to confirm that values appear correctly on the object records.
Rate limits depend on your GHL plan and API quota. Plan for bursts during mass form submissions and implement exponential backoff in automation to stay within limits. Consider batching updates when dealing with large data loads.
API documentation is available in your GHL developer portal and the App Connector docs. Review endpoint details, authentication methods, and example payloads to build accurate integrations. Use sandbox environments when available.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
