Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
n8n-nodes-google-sheets-trigger
Advanced tools
This is an n8n community node. It lets you use Google Sheets in trigger mode with your n8n workflows. Using this trigger, you will be able to recover only new rows from any Google sheet.
Don't want to read? Import the sample workflow Recover only new rows from Google Sheets to test this node.
Follow the installation guide in the n8n community nodes documentation.
Using this node you recover only new rows added to any Google sheet.
You can choose any credential defined in other Google Sheets nodes. All credentials are compatible.
Tested with node 0.197.1. You need an n8n version with polling enabled.
With this node, you will be able to recover new rows added to any sheet.
Define your Google sheets node as usual (credentials, spreadsheet id, range, raw data) and choose your poll time
If you want the sample sheet, access the sample spreadsheet and copy it to your Google Drive.
Google sheet contains a list of numbered rows:
You have a sample below where I combine new rows from Google Sheets with Generate dynamic contents for EMAILS or HTML pages (this is another community node created by me).
Then, create a new template for this node:
{{#each items}}
{{sample}}
{{/each}}
First, execute the workflow directly to recover all rows and test the message to Telegram. Polling and recovering new rows only work for active tasks in the background. Define the poll time (every 5 minutes, every hour, every day), and activate your task to get only new rows. Check executions to ensure that Workflows are executed every defined poll time.
Now, add new numbered rows (row 24, row, 25, ...) to your Google sheet. If everything works as expected, a new message is sent to the Telegram channel with new rows.
This is a sample of how the message looks (I added rows 14 to 23).
Clone the n8n-nodes-google-sheets-trigger repository and execute:
# Use v16.17.0 = lts/gallium
nvm use lts/gallium
# Install dependencies
npm install
# Build the code
npm run build
# "Publish" the package locally
npm link
Create an N8N installation and add the n8n-nodes-document-generator to it:
# Create an N8N installation
cd ..
mkdir n8n_install
cd n8n_install
npm init
npm install
npm install n8n
# "Install" the locally published module
npm link n8n-nodes-google-sheets-trigger
# Start n8n
npx n8n
To make this node even better, please let us know, how you use it. Commits are always welcome.
If you have any issues, please let us know on GitHub.
Node by n8nhackers.com. For productive use and consulting on this, contact us please.
Special thanks to N8n nodemation workflow automation by Jan Oberhauser.
If you want to build your custom n8n nodes, check the N8N documentation on custom nodes.
FAQs
This is a trigger node for Google Sheets.
The npm package n8n-nodes-google-sheets-trigger receives a total of 14 weekly downloads. As such, n8n-nodes-google-sheets-trigger popularity was classified as not popular.
We found that n8n-nodes-google-sheets-trigger demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.