n8n-nodes-lindo
This is an n8n community node for Lindo.ai, a website builder platform. It lets you automate website and client management directly from your n8n workflows.
n8n is a fair-code licensed workflow automation platform.
Installation
Follow the installation guide in the n8n community nodes documentation.
- Go to Settings > Community Nodes
- Select Install
- Enter
n8n-nodes-lindo
- Agree to the risks and click Install
Credentials
Select OAuth2 (default) or API Key on either node.
- OAuth2: Create a Lindo OAuth2 API credential, connect your account, and authorize your Lindo workspace.
- API Key: Copy your workspace API key from Lindo settings and create a Lindo API credential in n8n. Select API Key on the node. API requests use
https://api.lindo.ai.
Nodes
Lindo Trigger
Starts a workflow when one of these events occurs in your workspace:
| Blog AI Build Completed | A standalone AI blog creation workflow finishes |
| New Client Created | A new client is created |
| New Website Created | A website record is created; its AI build may still be running |
| Page AI Build Completed | A standalone AI page creation workflow finishes |
| Website AI Build Completed | An AI website creation workflow finishes |
Lindo
All six resources and their operations:
| Blog | Batch Create Blogs (AI), Create Blog (AI), List Blogs, Publish Blog |
| Client | Assign Website, Create Client, Generate Magic Link, List Clients |
| Credit | Allocate Credits, Get Client Credits, Get Workspace Credits |
| Page | List Pages |
| Website | Batch Create Websites (AI), Create Website (AI), Edit Website (AI), List Websites |
| Workflow Status | Batch Check Blog Status, Batch Check Website Status, Check Blog Status, Check Edit Status, Check Website Status |
Website
Create Website (AI) requires Prompt. Describe the business, content, design, and desired language in the prompt. Optional fields are Schedule At, Client ID, Client Email, and Client Name. Client Email can look up or create a client to assign the website to.
Edit Website (AI) requires Website ID and Prompt. Optionally enable Publish to Live Site or set Schedule At.
Batch Create Websites (AI) accepts Items (JSON): up to 25 objects containing prompt, optionally schedule_at and client.
Blog
Create Blog (AI) requires Website ID and Prompt. Language is optional (for example de-CH); leave it blank to use the prompt or website language. Schedule At is optional.
Batch Create Blogs (AI) requires Website ID and Items (JSON): up to 25 objects containing prompt, optionally language and schedule_at.
Publish Blog publishes supplied content rather than generating it. Required fields: Website ID, URL Path, Blog Content (Markdown), and Page Title. Additional fields: Author, Category, Excerpt, and Publish Date.
Client
Create Client requires Name and Email. Phone and Send Invitation Email are optional.
Assign Website requires Website ID and Client ID. Generate Magic Link requires Client ID and returns a client login link; treat that link as sensitive.
Credit
Get Workspace Credits returns the workspace balance. Get Client Credits requires Client ID.
Allocate Credits requires Client ID, Credit Type (Daily, Monthly, or Purchased), and Amount. Optional additional fields: Notes and Source.
Lists and workflow status
List operations accept Page and optional Search. List Pages and List Blogs also require Website ID.
AI creation and editing run asynchronously. Use the returned workflow_id with the matching Workflow Status operation, or use a completion trigger. Single checks require Workflow ID; batch checks accept Workflow IDs (JSON), an array of up to 25 IDs. Page creation is not an action exposed by this node, but page completion events can trigger it.
Workflow Templates
Ready-to-use workflow templates are included in the templates/ folder:
To use a template: copy the JSON, go to your n8n instance, click Import from file, and paste.
Resources
License
MIT
Website form submissions (1.5.0)
Add the Form Submission trigger and a Website Form Webhook credential containing the website signing secret from Website Settings → Integrations → Form webhooks. Publish the workflow, then paste its production webhook URL into the website default or a form URL override. The trigger verifies the raw-body signature and timestamp before emitting form.submitted payloads. An optional slug filter selects one form. Normal submissions send webhooks; ?test=1 does not. Deduplicate submission id before side effects; manual retries can repeat delivery. No API key or automatic hook registration is needed for this trigger.