← All N8N workflows
Automation & utilitiesHTTP RequestManual TriggerEdit Fields

when clicking test workflow

Configured with HTTP Request. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerTransformSet ParamsEdit FieldsTransformClean OutputEdit FieldsWeb / APIPerplexity RequestHTTP Request

Node categories in this workflow

  • Trigger
  • Transform
  • 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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
Set ParamsTransformEdit FieldsSee node parameters
Clean OutputTransformEdit FieldsSee node parameters
Perplexity RequestWeb / APIHTTP RequestPOST

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

  • httpBasicAuth
  • httpHeaderAuth

Workflow notes

Credentials Setup

Credentials Setup

1/ Go to the perplexity dashboard, purchase some credits and create an API Key

https://www.perplexity.ai/settings/api

2/ In the perplexity Request node, use Generic Credentials, Header Auth.

For the name, use the value "Authorization" And for the value "Bearer pplx-e4...59ea" (Your Perplexity Api Key)

Sticky Note1

Sonar Pro is the current top model used by perplexity. If you want to use a different one, check this page:

https://docs.perplexity.ai/guides/model-cards

when clicking test workflow

when clicking test workflow

Purpose and structure

This folder contains the when clicking test workflow workflow. Its executable nodes use httpRequest, manualTrigger, 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/0710_Manual_Stickynote_Automation_Webhook.json MIT; preserve source notices.

More in Automation & utilities