RU RU

063 | n8n + Appwrite: An Open-Source Firebase Alternative for Self-Hosting

Published on July 25, 2025

n8n + Appwrite: An Open-Source Firebase Alternative for Self-Hosting

We’ve already explored Supabase and Firebase — now it’s time to look at Appwrite, a powerful and fully open-source BaaS platform designed for self-hosting and complete data control.

If you want to build a backend on your own infrastructure, Appwrite can be the perfect partner in combination with n8n.


What Is Appwrite?

Appwrite is a full-featured Backend as a Service (BaaS) platform with open-source code. It provides REST APIs for most features a modern application needs:

  • Databases — collections and documents (PostgreSQL-based).
  • Storage — file storage with access control.
  • Authentication — built-in auth and user management.
  • Functions — serverless functions triggered by events or schedules.
  • Realtime — subscriptions to changes in databases, users, and storage.

Pros of Appwrite

  • Open source (BSD 3-Clause): full control, self-hosting, and freedom.
  • 🔄 Unified API: REST interfaces for everything (DB, Auth, Files, Users).
  • 🧠 PostgreSQL under the hood: reliability and extensibility.
  • ⚙️ Serverless functions: custom logic without external backend.
  • 🎛 User-friendly web UI: clean and intuitive admin console.
  • 👥 Active community: rapid updates, support, and good docs.

Cons of Appwrite

  • 🍼 Young project: the ecosystem is still maturing.
  • 🐳 Requires Docker: deployment is tightly coupled with containers.
  • 🛠 Needs own infrastructure: VPS, config, updates.
  • 🔧 No native node in n8n: use HTTP Request node instead.

Integrating Appwrite with n8n

How to connect Appwrite to n8n:

  1. Deploy Appwrite (via Docker or Docker Compose).
  2. Create a project in the Appwrite Admin Console.
  3. Create an API Key (with proper permissions).
  4. Configure an HTTP request in n8n:

Sample HTTP Request setup:

  • Method: POST, GET, PUT, DELETE
  • URL: https://your-appwrite/v1/databases/{dbId}/collections/{collectionId}/documents
  • Headers:
    • X-Appwrite-Project: your project ID
    • X-Appwrite-Key: your API key
    • Content-Type: application/json
  • Body: JSON with the desired data

Automation Examples

1. 📎 Handling Uploaded Files

User uploads file → Function triggers → sends a webhook to n8n → notification in Slack.

2. 👥 Syncing Clients from CRM

n8n receives a new client event → sends POST request to Appwrite to create a document in the customers collection.

3. 👶 Welcome Email to New User

Appwrite Function captures users.create → sends POST to n8n → n8n sends email via SMTP/SendGrid, etc.


Unique Appwrite Features

FeatureDescription
🧩 Self-hosted BaaSYou control all data and infrastructure.
🔗 REST APIFull CRUD operations via HTTP requests.
⏱ Serverless FunctionsAutomation via events or cron schedules.
🔔 RealtimeSubscribe to updates in real-time.

Conclusion

Appwrite is a strong Firebase alternative — especially if you value open-source, self-hosting, and flexible automation with n8n. While HTTP request setup is manual, integration remains accessible and extensible, and Appwrite’s API is among the most consistent and developer-friendly in the BaaS ecosystem.


In the next (and final) article in this series, we’ll explore Xano — a no-code, API-first platform ideal for business logic and advanced automation.

Need help?

Get in touch with me and I'll help solve the problem

Related Posts