Authenticate requests to the GHL Documents & Contracts API using OAuth 2.0 or API keys. Learn about scopes, token lifetimes, and secure storage for seamless integration.
Authenticate the Zapier App Connector to access GHL endpoints, configure client credentials, and test connections to ensure reliable data flow.
The 97Display integration leverages core endpoints for documents, templates, statuses, and retrieval. Typical usage includes creating documents from templates, updating document status, retrieving details, and piping data between GHL and Zapier.
Trigger: New item in Zapier creates a document in GHL using a 97Display template.
Actions: map fields, apply templates, set status, and return document ID to Zapier.
Method path: /documents
Key fields: customer_id, template_id, due_date
Trigger: GHL status change pushes to Zapier.
Actions: update Zapier record, notify users, trigger follow-up workflows.
Method path: /documents/{id}
Key fields: id, status, last_modified
Trigger: on-demand detail retrieval from Zapier.
Actions: fetch and map data to Zapier fields.
Method path: /documents/{id}/details
Key fields: id, fields
Automate workflows without custom code using triggers, actions, and field mappings.
Drag-and-drop automation between GHL and apps via Zapier templates.
Rapid deployment with reusable 97Display templates and workflows.
This glossary defines essential terms and processes used when connecting GHL to the Zapier App Connector for 97Display.
The process of proving identity to access GHL APIs, typically via OAuth 2.0 or API keys.
A URL path and HTTP method used to perform an action against the GHL API.
An HTTP callback that informs Zapier of events in GHL in real time.
A predefined document structure used to generate 97Display documents.
Extract contract PDFs from emails and auto-create GHL documents via 97Display.
Map CRM records to 97Display templates to auto-populate documents.
Trigger sending of documents for e-signature when a condition is met.
Collect your GHL API credentials and OAuth setup, plus Zapier app credentials.
Create a Zap with triggers, actions, and precise field mappings to connect 97Display.
Run end‑to‑end tests, verify data flow, and enable automations for production.
Most APIs support OAuth 2.0 or API keys for authentication. Use the method your org supports; store tokens securely and rotate them regularly.
Yes. Use Zapier’s field mapping to align GHL fields with your templates, ensuring data consistency across apps.
No extensive coding is required for standard flows. Use the Zapier editor to configure triggers, actions, and mappings.
Endpoint details are in the GHL developer docs and your app credentials dashboard within the GHL portal.
Use Zapier’s test feature to validate triggers and actions and verify data handoff between GHL and Zapier.
If credentials expire, refresh tokens or reauthenticate within the Zapier app connection and re-test the flow.
Yes. Many standard integrations are achievable with no-code templates, triggers, and actions.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
