Flow starts when receiving a get http call
Configured with Aggregate, N8N Training Customer Datastore, Respond To Webhook, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Integration
- Transform
- Trigger
- 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 |
|---|---|---|---|
| Customer Datastore (n8n training) | Integration | N8N Training Customer Datastore | getAllPeople |
| insert into variable | Transform | Edit Fields | See node parameters |
| Aggregate variable | Transform | Aggregate | See node parameters |
| On new flutterflow call | Trigger | Webhook | See node parameters |
| Respond to flutterflow | Web / API | Respond To Webhook | 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
Low-code API for Flutterflow apps
Low-code API for Flutterflow apps
Set up
- Copy the Webhook URL from
On new flutterflow callstep. This is the URL you will make a GET request to in FlutterFlow. - Replace the "Customer Datastore" step with your own data source or any other necessary workflow steps to complete your API endpoint's task.
Flow starts when receiving a get http call
Flow starts when receiving a get http call
Purpose and structure
This folder contains the Flow starts when receiving a get http call workflow. Its executable nodes use aggregate, n8nTrainingCustomerDatastore, respondToWebhook, set, 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
On new flutterflow call
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/Webhook/0499_Webhook_Respondtowebhook_Create_Webhook.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Flow starts when receiving a get http call
- Here you can change to your database node
- Step required to transform data for response to flutterflow