extracthtmlcontent html and http request and item lists
Configured with Html, HTTP Request, Item Lists, Medium, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Transform
- Web / API
- Integration
- Routing
- Trigger
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 |
|---|---|---|---|
| HTML | Transform | Html | extractHtmlContent |
| HTTP Request | Web / API | HTTP Request | See node parameters |
| HTML1 | Transform | Html | extractHtmlContent |
| Item Lists | Transform | Item Lists | See node parameters |
| Medium | Integration | Medium | See node parameters |
| HTTP Request1 | Web / API | HTTP Request | See node parameters |
| Loop Over Items | Routing | Loop Over Items | See node parameters |
| Item Lists1 | Transform | Item Lists | limit |
| When clicking "Execute Workflow" | Trigger | Manual Trigger | 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
Usage
Usage
How to use me This workflow gets all the posts from your WordPress site and sorts them into a clear format before publishing them to medium.
Step 1. Set up the HTTP node and set the URL of the source destination. This will be the URL of the blog you want to use. We shall be using https://mailsafi.com/blog for this.
Step 2. Extract the URLs of all the blogs on the page This gets all the blog titles and their URLs. Its an easy way to sort ou which blogs to share and which not to share.
Step 3. Split the entries for easy sorting or a cleaner view.
Step 4. Set a new https node with all the blog URLs that we got from the previous steps.
Step 5. Extract the contents of the blog
Step 6. Add the medium node and then set the contents that you want to be shared out.
Execute your work flow and you are good to go
extracthtmlcontent html and http request and item lists
extracthtmlcontent html and http request and item lists
Purpose and structure
This folder contains the extracthtmlcontent html and http request and item lists workflow. Its executable nodes use html, httpRequest, itemLists, manualTrigger, medium, splitInBatches. 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
When clicking "Execute Workflow"
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/Http/0390_HTTP_Manual_Automation_Webhook.json MIT; preserve source notices.