Common Issues

Connection issues

I can't connect my Google account

Make sure you're signing in with the Google account that owns or has access to the forms you want to export. If you manage multiple Google accounts, double-check that the browser session is using the right one before authorizing. You can revoke and reconnect the integration from your Google account's security settings under Third-party apps with account access.

Authorization was successful but no forms are loading

This usually means the authorized account doesn't have access to the Form IDs you entered. Confirm that the account you connected is either the Owner or has Editor access to those forms. Shared forms from a different Google Workspace domain may also require explicit sharing before they appear.

Missing data

Some responses are missing from the export

Check whether the missing responses were submitted before or after you set up the data flow. Coupler.io pulls all available responses each time it runs, so responses submitted before the first run should still appear. If responses are still missing, verify that the form hasn't been moved to trash or had its sharing settings changed.

The respondent_email column is empty

This field is only populated when the form has Collect email addresses enabled. Open the form in Google Forms, go to Settings → Responses, and check whether email collection is turned on. Responses submitted before this setting was enabled will not have an email address retroactively.

File upload answers are showing as links, not files

This is expected behavior. The Google Forms API returns a Google Drive URL for file upload responses, not the file content itself. You'll need to open the link to access the uploaded file.

Permission errors

I get a "403 Forbidden" or "Access denied" error

The connected Google account doesn't have sufficient access to the form. You need at least Viewer access to read responses, but Owner or Editor access is recommended. Ask the form owner to share the form with your account and then re-run the data flow.

The data flow runs but returns no rows for a specific Form ID

Double-check that the Form ID is correct — it should be the string in the form URL between /d/ and the next /. A common mistake is copying the full URL or including extra characters. Also confirm the form has at least one response before expecting rows in the Form responses entity.

Data discrepancies

Question text in the export doesn't match what's in the form

If you edited a question after responses were already collected, the item_title field in earlier responses reflects the question text at the time of submission, not the current text. The Forms entity always shows the current question text. This is a Google Forms API behavior and cannot be changed.

Rate limits

The data flow fails with a rate limit or quota error

Google Forms API has per-minute and per-day quotas. If you're syncing a large number of forms or have very frequent schedules across multiple data flows, you may hit these limits. Try reducing the number of forms per data flow, or space out your sync schedules to avoid simultaneous runs.