Resources · n8n integration

Google Perspective n8n integrationAutomate Google Perspective with n8n.

Every comment you collect can be scored before a human reads it. The Google Perspective n8n integration gives you one node, one operation, Analyze Comment, and 8 attributes to pick from. No trigger ships with it, so the workflow starts somewhere else and the node scores on the way through.

Try the Google Perspective integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Google Perspective n8n integration actually do?

The Google Perspective n8n integration connects the Google Perspective node to the rest of your workflow. You hand a piece of text to the Analyze Comment operation, choose the attributes you want measured, and n8n hands back a score for each one as ordinary workflow data. The same run can then store it, compare it, or tell someone, without anyone opening a moderation queue first.

Start with the gesture, not the field list. Pick the one attribute your team will actually act on, set Score Threshold so quiet results never reach the rest of the workflow, and point the text at the field that carries the message with an expression like {{ $json.field }}, which is how n8n reads a value from the previous step. At 0, every score comes back, which is handy while you calibrate and noisy once you are live.

A community team running a public forum scores each new message and pushes only the ones above the threshold into a Slack channel, original text included. The moderator reads a handful of cases instead of the whole feed, and nothing sits unread for a day.

A marketplace takes a different angle. Every review gets scored on its way in and lands as a row in Google Sheets, with the attribute that flagged it next to the score. Sorting that sheet is enough to see which listings attract the rough comments. Scores that pile up week after week can also feed a Grafana board, so the trend shows up as a curve rather than a feeling.

Outbound text works the same way. A support team scores the draft reply before it leaves through Gmail, and an answer written at the end of a long day gets a second look before a customer reads it.

The node covers the Analyze Comment operation. Anything outside the catalog operations goes through the HTTP Request node, which calls any endpoint of the API, meaning any address the API exposes, and reuses the same credential through predefined authentication. If you are still weighing platforms, the n8n review walks through the trade-offs.

Connect

How do you connect Google Perspective to n8n?

  1. 01

    Create the Google Cloud project

    Open the Google Cloud Console and create a project, or reuse one you already have, then enable the APIs the credential will need. On n8n Cloud, Managed OAuth2 covers certain Google nodes with a Sign in with Google button and no console work at all. Self-hosted instances always go the Custom OAuth2 route, so the console is part of the job either way.

  2. 02

    Configure the consent screen

    In APIs & Services, open OAuth consent screen and fill in App name and User support email. For Audience, Internal keeps the app inside your own Google Workspace, External opens it to any Google account. Under Branding, add an authorized domain: n8n.cloud for the hosted service, or the domain of your instance when you self-host.

  3. 03

    Create the OAuth client

    Back in Credentials, pick Create credentials, then OAuth client ID, and set Application type to Web application. Copy the OAuth Redirect URL shown by your half-finished n8n credential into Authorized redirect URIs. Google then gives you a Client ID and a Client Secret, the two values n8n is waiting for. A credential is created once and reused by every workflow.

Actions

What can the Google Perspective node do?

The Google Perspective node exposes one operation. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Analyze Comment

analyzeComment

What you see in n8n

Notes & use cases

Sends text to Google Perspective and returns a score for each attribute you selected, ready for the next node to read.

Key parameters

  • Text: the comment to analyze, required, usually an expression such as {{ $json.field }}.
  • Attributes to Analyze: required; each entry picks an Attribute Name among toxicity, severe_toxicity, insult, profanity, threat, identity_attack, sexually_explicit and flirtation.
  • Score Threshold: the score above which results come back; at 0, all scores are returned.
  • Language Name or ID: the language of the text; left empty, the API detects it on its own.
Use cases
score a forum post as it arrives and let only what clears the threshold reach a human.
Need help

Need help automating Google Perspective with n8n?

A person reads every message.

FAQ

Google Perspective and n8n, the questions that come next

01Is the Google Perspective n8n integration free?
Yes on the n8n side. The node ships with n8n, so there is nothing to install and no extra cost, whether you run n8n Cloud or a self-hosted instance on the Community Edition under its Sustainable Use license. A workflow, meaning a chain of automated steps, behaves the same on both. What Google charges for the Perspective API itself is a separate conversation and this page does not cover it. The real cost of starting is the time you spend in the Google Cloud Console getting the credential ready.
02What credentials does the Google Perspective node need?
A Google OAuth2 credential for a single service. A credential is a connection you save once in the n8n Credentials menu, and every workflow reuses it from the node's dropdown. On n8n Cloud, Managed OAuth2 covers certain Google nodes with a Sign in with Google button. Self-hosted users, and Google nodes outside that list, go through Custom OAuth2 instead: a project in the Google Cloud Console, the APIs enabled, a configured consent screen, and an OAuth client ID that hands you the Client ID and the Client Secret. Google's own documentation recommends OAuth2 over a service account for most cases.
03What are the limits of the Google Perspective node in n8n?
The catalog fits in one operation, Analyze Comment, on a single resource. Anything outside the catalog operations goes through the HTTP Request node, which calls any endpoint of the API, meaning any address the API exposes, and reuses the same credential through predefined authentication, so you stay on one connection. The other limit is the one you set yourself: Score Threshold. Leave it at 0 and every score comes back, which helps while you calibrate and turns noisy in production. Tick the attributes your team acts on rather than all 8, and the output stays readable.
04Can Google Perspective trigger an n8n workflow in real time?
No, there is no Google Perspective trigger node in n8n. A trigger is the step that starts a workflow. Here the workflow starts elsewhere: a Schedule Trigger running at a fixed interval, an n8n Webhook, meaning a URL a third-party service calls when something happens, or the trigger of another tool you already connected. It gets in the way less than it sounds, because the text you want to score almost always arrives through one of those paths. The chat platform, the form, the database row: whatever brings the comment in becomes the starting point.
05n8n or Make for Google Perspective?
It depends on where your data is allowed to live. n8n self-hosts with Docker or npm, or runs on n8n Cloud, and the workflow is identical either way. Make is a hosted platform with no self-hosting option, billed per operation. If your users' comments have to stay on your own infrastructure, the question is already settled. If you never want to maintain a server, the hosted model saves you that work. Both draw workflows visually, so the comparison comes down to hosting, control over the data and the cost model, not the editor.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations