n8n Integration

What is n8n

n8n is a highly extensible workflow automation tool. Through a graphical interface, users can connect various applications, APIs, or databases as “nodes” to easily design automated processes for data retrieval, processing, and delivery. n8n supports self-hosting, meaning you can deploy it on your own server or in your cloud environment and maintain full control over data security and privacy.

Core Features

• Intuitive Workflow Editor
  A drag-and-drop node editor lets you build complex workflows without writing code; you can also add custom logic via code nodes.
• Rich Integration Support
  Comes with hundreds of built-in service nodes (e.g. HTTP Request, Slack, Google Sheets, MySQL) and allows easy development of custom community or third-party nodes.
• Event-Driven Triggers
  Supports multiple trigger types—scheduled triggers, webhooks, polling, etc.—to flexibly meet various automation needs.
• Extensible Community Ecosystem
  Boasts an active community and a node marketplace where developers share custom nodes and users can easily install others’ contributions.

How to Integrate

1. Deploy a Self-Hosted n8n Instance

   Because the Ragic Node is a community node, it isn’t available on n8n Cloud. To use it, you must self-host n8n and manually install the node.

2. Install the Ragic Node

   1. In the n8n UI, click the menu at the lower-left → Settings → Community nodes.

   2. Click Install a community node.

   3. In the popup, enter "n8n-nodes-ragic" in the “npm Package Name” field. Agree to the risks of using community nodes: select I understand the risks of installing unverified code from a public source. Click Install.

   

   4. After installation, search for “Ragic” in your workflow. (You will see two nodes with the same name. The one has grey-arrowed on the right is the Trigger node; the one without an arrow is the Action node.)

   

3. Trigger Node

   Purpose: Uses webhooks to start a workflow when the target form changes.

   

   First, create credentials: in “Credential to connect with,” choose Create new Credential, then enter your API Key and the Sheet URL (the URL from “http” up to—but not including—the ? character), then save.

   

   In the Event field, select which form event to listen for: Create Records, Update Records, or Create & Update Records.

   Click Test step at the upper right; the node will open a temporary webhook listener. Make a change in the target form to confirm the trigger node works. (If you don’t receive a webhook, see Additional Notes.)

   

4. Action Node

   Purpose: Create or update data.

   

   First, create credentials: in “Credential to connect with,” choose Create new Credential, then enter your API Key and your Server Name (e.g., www.ragic.com or ap12.ragic.com), then save.

   

   In the Action field, choose Create New Data or Update Existed Data.

   In the Form dropdown, select your target form. If it’s missing or you see an error, reselect your credentials and try again.

   If set to Update Existed Data, a Record Index field appears—enter the Record ID of the record you wish to update.

   In the JSON Body, write a JSON data you want to create or update according to the Ragic HTTP API format.

   Click Test step at the upper right to confirm the action node works.

   

5. Save and Activate Your Workflow

   After designing your workflow, click Save at the upper right, then switch its status to Active.

Additional Notes

• If you follow the official n8n docs and deploy Self-Hosted n8n with Docker, you may encounter:
  1. Trigger Node never receives webhook requests - Start your n8n container or process with the environment variable "NODEJS_PREFER_IPV4=true" to force Node.js to use IPv4.*
  2. Trigger Node occasionally misses webhook requests - Built-in tunneling can be unstable on Windows or certain environments; consider using a more reliable public tunnel like ngrok and set the "WEBHOOK_URL={YOUR_WEBHOOK_URL}" environment variable when starting n8n.*