http request and filter
Configured with Filter, HTTP Request. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Routing
- Web / API
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 |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Set Loop | Transform | Edit Fields | See node parameters |
| If | Routing | If | See node parameters |
| User ID | Transform | Edit Fields | See node parameters |
| Collections | Web / API | HTTP Request | See node parameters |
| Loop Discount | Transform | Edit Fields | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| Select Collection | Routing | Filter | See node parameters |
| Filter | Routing | Filter | See node parameters |
| Get Articles | Web / API | HTTP Request | See node parameters |
| Merge 100+ | Transform | Merge | 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
User ID
Get from Zotero Web > Settings > Security:
https://www.zotero.org/settings/security
Select Collection
Select Collection
Sticky Note1
On the same page, create an Application Key to setup the Header Auth inside the Collections Node: https://www.zotero.org/settings/security
Use Zotero-API-Key as Header name
Sticky Note2
See the "Table" results, of previous nodes and replace the second value of "IS EQUAL TO" with your Collection KEY
Sticky Note3
Optional Filter for Results
Sticky Note4
Optional Edit Fields for Results
http request and filter
http request and filter
Purpose and structure
This folder contains the http request and filter workflow. Its executable nodes use filter, httpRequest, if, manualTrigger, merge, set. 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 ‘Test 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/Manual/0589_Manual_Filter_Update_Webhook.json MIT; preserve source notices.