n8n deAPI node

​

Why Use the Community Node?

​

Prerequisites

• A self-hosted n8n instance accessible via HTTPS (required for webhook callbacks)
• A deAPI API key from the deAPI Dashboard
• A Webhook Secret from deAPI Webhook Settings

​

Installation

​

Option 1: GUI Installation (Recommended)

1. In your n8n instance, go to Settings > Community Nodes
2. Click Install a community node
3. Enter n8n-nodes-deapi and click Install
4. Restart n8n if prompted

​

Option 2: Manual Installation (docker)

docker exec -it <n8n-docker> sh
mkdir ~/.n8n/nodes
cd ~/.n8n/nodes
npm i n8n-nodes-deapi

​

Credential Configuration

1. In n8n, go to Credentials > Add Credential
2. Search for deAPI API and select it
3. Fill in the required fields:

4. Click Save to store the credentials

​

Available Operations

​

Deapi Node (Regular Operations)

Image Operations

Video Operations

Audio Operations

Prompt Operations

​

DeapiTrigger Node (Webhook Trigger)

• Building event-driven workflows
• Processing results from jobs submitted outside n8n
• Monitoring job progress across multiple systems

​

How the Webhook-Based Waiting Works

1. Execute Phase

   +-----------+     POST /txt2img      +-----------+
   |   Deapi   | ---------------------> |   deAPI   |
   |   Node    |   (includes webhook)   |   Server  |
   +-----------+                        +-----------+
        |
        v
   Workflow pauses
   (frees memory)

2. Processing Phase (no n8n resources used)

   +-----------+                        +-----------+
   |    n8n    |  <-- job.processing    |   deAPI   |
   | (waiting) |     (acknowledged)     | (working) |
   +-----------+                        +-----------+

3. Resume Phase

   +-----------+                        +-----------+
   |    n8n    |  <-- job.completed     |   deAPI   |
   | (resumes) |   (with result_url)    |  (done)   |
   +-----------+                        +-----------+
        |
        v
   Workflow continues
   with generated content

• No polling loop consuming API calls
• Workflow pauses and frees memory during processing
• Results include binary data ready for downstream nodes

​

Example Workflow: Text-to-Image Generation

​

Workflow Overview

+------------------+      +-------------------+
|  Manual Trigger  | ---> |    Deapi Node     |
|                  |      | (Image: Generate) |
+------------------+      +-------------------+
                                   |
                                   v
                          Generated image as
                          binary data output

​

Step 1: Add a Trigger

​

Step 2: Add the Deapi Node

1. Add a Deapi node to your workflow
2. Select your deAPI API credentials
3. Configure the operation:

4. Optionally configure:
   • Negative Prompt — Elements to exclude from the image
   • Resolution — Select image dimensions other than the default ones, depending on your needs
   • Seed — For reproducible results (use -1 for random)
   • Steps — Number of inference steps (higher = more detail)

​

Step 3: Run the Workflow

1. Click Test Workflow or Execute Workflow
2. The node will:
   • Submit the generation request to deAPI
   • Pause the workflow while waiting
   • Resume automatically when the image is ready
3. The output contains the generated image as binary data

​

Using the Generated Image

• Write Binary File — Save to disk
• Send Email — Attach to an email
• HTTP Request — Upload to cloud storage
• Slack/Discord — Share in a channel

​

Using the DeapiTrigger Node

​

Setup

1. Add a DeapiTrigger node to a new workflow
2. Select your deAPI API credentials
3. Configure event filtering:

4. Activate the workflow to make the webhook URL live
5. Copy the Webhook URL displayed in the node
6. Add this URL to your deAPI Webhook Settings

​

Event Types

​

Comparison: Community Node vs HTTP Request

​

Troubleshooting

​

HTTPS Required

• Use a reverse proxy (nginx, Caddy, Traefik) with SSL termination
• Use a tunnel service (ngrok, Cloudflare Tunnel) for development
• Ensure your SSL certificate is valid and not self-signed

​

Webhook Verification Failures

1. Verify your Webhook Secret matches the one in deAPI Webhook Settings
2. Ensure your n8n server clock is synchronized (signature includes timestamp)
3. Check that no proxy is modifying the request body

​

Timeout Errors

1. Select the Deapi node
2. Expand Options
3. Increase Wait Timeout to allow more time

​

Rate Limiting

​

Example Workflow Download

1. Download deAPI_guide.json
2. In n8n, go to Workflows > Import from File
3. Select the downloaded file
4. Configure your deAPI credentials
5. Explore the example nodes and sticky notes

​

Resources

• n8n Community Nodes Documentation
• n8n Integration (HTTP Request approach)
• deAPI API Reference
• Execution Modes & HTTP Queue
• Model Selection Guide
• GitHub Repository
• NPM Package