# N8N Integration
**URL:** https://community.noloco.io/t/n8n-integration/1658
**Category:** Feature Requests
**Tags:** feature-request
**Created:** [January 28, 2025, 4:15pm UTC](https://community.noloco.io/t/n8n-integration/1658 "2025-01-28T16:15:52Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@growfastr](https://community.noloco.io/u/growfastr)
#### Post date: [January 28, 2025, 4:15pm UTC](https://community.noloco.io/t/n8n-integration/1658/1 "2025-01-28T16:15:52Z")
It would be great to get some more integrations. One in particular that would be amazing is a direct integration with N8N to create automations. I find it far superior to Zapier or Make when creating actual custom app automations.
---
### Author:  [@seanvosler](https://community.noloco.io/u/seanvosler)
#### Post date: [January 29, 2025, 7:18pm UTC](https://community.noloco.io/t/n8n-integration/1658/2 "2025-01-29T19:18:29Z")
Howdy, I use loads of N8N integrations with Noloco, I use the ‘webhook’ node to trigger n8n workflows from Noloco, then within N8N you can use the HTTP nodes to send/query/modify data within noloco
cheers
---
### Author:  [@growfastr](https://community.noloco.io/u/growfastr)
#### Post date: [January 29, 2025, 7:31pm UTC](https://community.noloco.io/t/n8n-integration/1658/3 "2025-01-29T19:31:40Z")
That’s awesome! I was trying to do that, but I couldn’t figure out the structure that Noloco would accept to write data from the HTTP node. Can you share a screenshot, or is there a link to an example or walkthrough online somewhere?
---
### Author:  [@seanvosler](https://community.noloco.io/u/seanvosler)
#### Post date: [January 29, 2025, 8:08pm UTC](https://community.noloco.io/t/n8n-integration/1658/4 "2025-01-29T20:08:34Z")
Ill try and get some more details over later today! But basically you want to do what’s called a ‘graphQL mutation’ via the HTTP ‘POST’ request… here’s some details from the noloco api documentation: [Update a Record | Noloco](https://guides.noloco.io/api-documentation/api-overview/update-a-record)
here’s details from n8n on how to configure the body of the HTTP node: [HTTP Request node documentation | n8n Docs](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/#send-body)
Also, in your app’s settings under the API key is a link to the ‘api explorer’ which will help you design mutations/queries to use within the body of the HTTP node within N8N - sorry I don’t have more details ATM!
---
### Author:  [@showcal\_rob](https://community.noloco.io/u/showcal_rob)
#### Post date: [February 12, 2025, 6:47pm UTC](https://community.noloco.io/t/n8n-integration/1658/5 "2025-02-12T18:47:32Z")
Figured out how to get this working. You need to set the Webhook in n8n as a POST method, a response code of 200, and response data of Accepted
Once I did all of those, I tested the workflow action, and it worked like a charm!
---
### Author:  [@seanvosler](https://community.noloco.io/u/seanvosler)
#### Post date: [February 20, 2025, 5:15pm UTC](https://community.noloco.io/t/n8n-integration/1658/6 "2025-02-20T17:15:47Z")
Ah that makes sense, basically emulating a [Make.com](http://Make.com) webhook at that point… clever
---
### Author:  [@showcal\_rob](https://community.noloco.io/u/showcal_rob)
#### Post date: [February 20, 2025, 7:03pm UTC](https://community.noloco.io/t/n8n-integration/1658/7 "2025-02-20T19:03:49Z")
Exactly! I imagine @darragh and the folks have done some webhook verifications to ensure that the webhook is going to a valid address as a part of some normal try catch error handling, to prevent the rest of the workflow from completing. i like it!
---
### Author:  [@Nexaverse](https://community.noloco.io/u/Nexaverse)
#### Post date: [May 15, 2025, 8:51pm UTC](https://community.noloco.io/t/n8n-integration/1658/8 "2025-05-15T20:51:42Z")
I strongly support this n8n integration request! We’ve recently migrated several of our business processes from Make to n8n and the difference is substantial.