-
Notifications
You must be signed in to change notification settings - Fork 454
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add common issues to Google Sheets Trigger node
- Loading branch information
1 parent
5ea156b
commit e4ab911
Showing
3 changed files
with
42 additions
and
1 deletion.
There are no files selected for viewing
36 changes: 36 additions & 0 deletions
36
...tions/builtin/trigger-nodes/n8n-nodes-base.googlesheetstrigger/common-issues.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
#https://www.notion.so/n8n/Frontmatter-432c2b8dff1f43d4b1c8d20075510fe4 | ||
title: Google Sheets Trigger node common issues | ||
description: Documentation for common issues and questions in the Google Sheets Trigger node in n8n, a workflow automation platform. Includes details of the issue and suggested solutions. | ||
contentType: integration | ||
priority: high | ||
--- | ||
|
||
# Google Sheets Trigger node common issues | ||
|
||
Here are some common errors and issues with the [Google Sheets Trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.googlesheetstrigger/) and steps to resolve or troubleshoot them. | ||
|
||
## Stuck waiting for trigger event | ||
|
||
When testing the Google Sheets Trigger node with the **Test step** or or **Test workflow** buttons, the execution may appear stuck and unable to stop listening for events. If this occurs, you may need to exit the workflow and open it again to reset the canvas. | ||
|
||
Stuck listening events often occur due to issues with your network configuration outside of n8n. Specifically, this behavior often occurs when you run n8n behind a reverse proxy without configuring websocket proxying. | ||
|
||
To resolve this issue, check your reverse proxy configuration (Nginx, Caddy, Apache HTTP Server, Traefik, etc.) to enable websocket support. | ||
|
||
## Date and time columns are rendering as numbers | ||
|
||
Google Sheets can render dates and times a few different ways. | ||
Check warning on line 23 in docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googlesheetstrigger/common-issues.md GitHub Actions / runner / vale
|
||
|
||
The [**serial number** format](https://developers.google.com/sheets/api/reference/rest/v4/DateTimeRenderOption), popularized by Lotus 1-2-3 and used my types of spreadsheet software, represents dates as a decimal number. The whole number component (the part left of the decimal) represents the number of days since December 30, 1899. The decimal portion (the part right of the decimal) represents time as a portion of a 24-hour period (for example, `.5` represents noon). | ||
|
||
To use a different format for date and time values, adjust the format in your Google Sheet Trigger node. This is available when **Trigger On** is set to **Row Added**: | ||
|
||
1. Open the Google Sheet Trigger node on your canvas. | ||
2. Select **Add option**. | ||
3. Select **DateTime Render**. | ||
4. Change **DateTime Render** to **Formatted String**. | ||
|
||
The Google Sheets Trigger node will now format date, time, datetime, and duration fields as strings according to their number format. | ||
Check failure on line 34 in docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googlesheetstrigger/common-issues.md GitHub Actions / runner / vale
|
||
|
||
The number format depends on the spreadsheet's locale settings. You can change the local by opening the spreadsheet and selecting **File > Settings**. In the **General** tab, set **Locale** to your preferred locale. Select **Save settings** to adjust the value. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters