Google Page Entity Extraction Template
Configured with HTTP Request, Respond To Webhook, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Trigger
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Respond to Webhook | Web / API | Respond To Webhook | See node parameters |
| Google Entities | Web / API | HTTP Request | POST |
| Get Url | Trigger | Webhook | See node parameters |
| Get URL Page Contents | Web / API | HTTP Request | See node parameters |
| Respond with detected entities | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Google Page Entity Extraction Template
Google Page Entity Extraction Template
What this workflow does
This workflow allows you to extract named entities (people, organizations, locations, etc.) from any web page using Google's Natural Language API. Simply send a URL to the webhook endpoint, and the workflow will fetch the page content, process it through Google's entity recognition service, and return the structured entity data.
How to use
- Replace "YOUR-GOOGLE-API-KEY" with your actual Google Cloud API key (Natural Language API must be enabled)
- Activate the workflow and use the webhook URL as your endpoint
- Send a POST request to the webhook with a JSON body containing the URL you want to analyze: {"url": "https://example.com/page"}
- Review the returned entity analysis with categories, salience scores, and metadata
Webhook Input Format
The webhook expects a POST request with a JSON body in this format:
{
"url": "https://website-to-analyze.com/page"
}
Response Format
The webhook returns a JSON response containing the full entity analysis from Google's Natural Language API, including:
Entity names and types (PERSON, LOCATION, ORGANIZATION, etc.) Salience scores indicating entity importance Metadata and mentions within the text Entity sentiment (if available)
Google Page Entity Extraction Template
Google Page Entity Extraction Template
Purpose and structure
This folder contains the Google Page Entity Extraction Template workflow. Its executable nodes use code, httpRequest, respondToWebhook, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Get Url
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0980_Code_Webhook_Automation_Webhook.json MIT; preserve source notices.