Common Issues
Connection issues
I can't find my file in the file picker
The file picker searches by file name in Google Drive. If you can't find your file:
Check permissions: Make sure the file is shared with your Google account or you own it. If it's in a shared drive, verify your account has access.
Use the direct URL: Instead of searching, paste the file's full URL or ID directly. Open the file in Google Drive, copy the URL from the address bar, and paste it into the "File" field.
Search for shared files: If the file is shared with you but not in "My Drive," it may appear under "Shared with me." Copy its URL directly.
"This importer is using a destination file that is no longer available to the current connection"
This error happens when the destination file's access has been revoked or the authentication token has expired. To fix it:
Re-authenticate the destination: Go to your data flow settings, find the destination connection, and re-authorize it.
Check file permissions: Make sure the destination file is still shared with your Google account and you have edit access.
Verify the file exists: Confirm the destination file hasn't been moved, deleted, or its sharing settings changed.
If you're using Excel as a destination, this error is more common due to Microsoft API changes. Try re-connecting your Microsoft account.
I get "undefined" or "file not found" errors
This usually means Coupler.io can't access the file you specified. Check:
File format: Is the file a Google Sheet, .csv, .xlsx, or .xlsm? Other formats (like .xml) are not supported.
File is shared: If using a file you don't own, make sure it's explicitly shared with your Google account email.
File ID changed: If you replaced the file in Google Drive (even with the same name), its ID changed. Update the URL in your data flow settings.
Character encoding: CSV and Excel files must be UTF-8 encoded. Files with other encodings may fail to load.
Missing data
Some rows or columns didn't import
If you specified a range (like A1:Z100), the import only pulls data within that range. Check:
Range is correct: Verify the range includes all rows and columns you want. Use
A:Zor similar to capture the full extent.Hidden rows/columns: Google Sheets and Excel can hide rows or columns. Unhide them in the source file before importing.
Empty rows in the middle: If your data has blank rows, they import as empty rows too. Remove them from the source or expand your range awareness.
First row is data, not headers: If you don't have a header row and Coupler.io treats the first row as headers, enable "Skip header" in advanced settings.
The data looks corrupted or has strange characters
Text corruption usually means an encoding mismatch:
Check source file encoding: CSV and Excel files should be UTF-8 encoded. If you're exporting from another tool, ensure UTF-8 is selected during export.
Re-save the file: Open the source file in Google Sheets or Excel, make a small edit, and save. This can reset encoding.
Try a smaller subset: Export a few rows to a new CSV file and try importing that to isolate the issue.
New edits to my source file aren't showing up in the import
Coupler.io imports based on the file's unique ID, not its name. If you:
Replaced the file: Even with the same name, a new file gets a new ID. Update the file URL in your data flow settings.
Want to auto-update: Schedule your data flow to run automatically (e.g., daily or hourly). The flow will always pull from the same file ID you specified.
Are editing the same file: If you're editing the same file and just re-running the flow, changes should appear. Try a manual run to confirm.
If you need to import a different file every day without manually updating the URL, you'll need a workaround like Integromat to rename/move files to a consistent location first.
Permission errors
"Permission denied" or "Access forbidden" error
You don't have access to the file. Check:
File is shared: Open the file in Google Drive. Click "Share" and verify your Google account email is listed with at least "Viewer" access.
Shared drive access: If the file is in a shared drive, make sure your account is a member of that shared drive.
Public link vs. account access: A public link doesn't grant automatic access. The file must be explicitly shared with your account email.
Re-authenticate: Disconnect and reconnect your Google account in Coupler.io to refresh your credentials.
Data discrepancies
Row count in source doesn't match import (e.g., 394 rows in source, 377 imported)
This is usually due to empty rows or header/footer content in the source:
Check for empty rows: Look for blank rows between data blocks in your source sheet. These count as rows but may look empty.
Specify a range: Instead of importing the entire sheet, use a precise range (e.g.,
A2:Z350) to exclude headers or footers.Use "Skip header": If the first row should not be counted as data, enable the "Skip header" option.
Filter before import: Clean up your source file by removing blank rows, then re-run the import.
Percentages or special values convert to decimals (0.5 instead of 50%)
Google Drive imports preserve the raw data value, not the formatting:
Formatting in destination: After import, format the column in your destination (Google Sheets, Excel, etc.) as a percentage.
Multiple formats in one column: If a column has mixed data types (some percentages, some text), only numeric values will convert. Ensure consistent formatting in the source.
Rate limits
"Quota exceeded" or "Resource has been exhausted" error
You've hit Google Sheets API rate limits. This happens when multiple data flows or imports run at the same time. To fix:
Stagger your schedule: Instead of running all data flows at once, spread them out over time (e.g., one at 8am, one at 9am).
Run manually one at a time: If you need to run multiple flows now, trigger them individually from the Coupler.io dashboard.
Reduce frequency: Lower data flow schedules from every 10 minutes to every hour, if possible.
Check external tools: If you use other tools (Zapier, Integromat, etc.) that also access Google Sheets, pause them temporarily to reduce API pressure.
This error is temporary and usually clears within a few minutes. Retry your data flow once the quota resets.
Last updated
Was this helpful?
