Connect Google Forms

For: Company admins and integration owners
Owner: Integration operations
Outcome: Test, monitor, recover, rotate, and disconnect Google Forms safely.
Last verified: 2026-08-30
Next review: 2026-11-28
Status: supported

Send approved Google Forms responses to Sakhaa through the supported connector. This guide uses the current supported Sakhaa setup surface and keeps provider-owned approval and availability separate.

Prepare the connection

Provider approval and field availability can differ by source.

Use a form owned by the customer and confirm access to its Apps Script project.
Keep the generated connector key in script properties, not in the form or a sheet cell.
Submit one synthetic response and confirm field mapping and duplicate handling.

Connect and prove health

Open /app/settings/lead-sources in the correct workspace.
Save the oauth, webhook secret, or connector key only in the protected setup surface.
Use the source test action or a provider test record. Do not use customer data.
Confirm this healthy result: The test record appears once with the expected source, owner, and fields.

Use synthetic data and an approved test identity. Do not use customer traffic only to prove a connection.

Monitor and recover

Monitor: Review connector status, source logs, duplicate results, and routing outcome.
Recover: Correct credentials or mappings, retest with a new test identifier, and review failed logs.
Rotate: Rotate the source secret in the provider and Sakhaa during the same maintenance window.
Disconnect: Disable intake first, preserve logs, and confirm where new records will be routed.
Limits: Provider approval and field availability can differ by source.
Fallback: Keep the previous approved intake source active, or route new work to a reviewed manual queue until the connection is healthy.

Support boundary

Sakhaa supports the CRM configuration and product behavior. The provider controls account approval, billing, quotas, and external service availability.

Record the provider, workspace, approximate time, safe error code, expected result, and actual result.
Do not include passwords, access tokens, API secrets, message content, or unnecessary customer data.