Skip to main content

​
Frequently Asked Questions

Common questions and troubleshooting for OpenCompany.

​
General

OpenCompany is an open-source workflow automation platform inspired by n8n. It lets you create visual workflows that connect AI models, messaging services, devices, and APIs using a drag-and-drop interface.
Yes, OpenCompany is open-source and free to self-host. You only pay for external services you use (AI API calls, cloud hosting, etc.).
OpenCompany is inspired by n8n’s node-based approach but focuses on:
  • Deep AI integration (12 LLM providers with memory, tools, and skills)
  • WhatsApp, Telegram, and Twitter/X automation
  • Android device control
  • Real-time WebSocket communication
OpenCompany is built with React and Python, while n8n uses Node.js.
Yes, OpenCompany is released under an open-source license. Check the repository for specific license terms.

​
Installation

Minimum:
  • 2GB RAM
  • 2 CPU cores
  • 10GB disk space
Recommended:
  • 4GB+ RAM
  • 4+ CPU cores
  • SSD storage
Yes. OpenCompany runs natively on Windows with Node.js 22+ and Python 3.12+ installed. macOS, Linux, WSL2, and Git Bash are also supported. All launch scripts are cross-platform.
company start auto-installs any new dependencies before launching.
Change the port in your .env file:
Then restart the services. Default ports: client 3000, backend 3010, Node.js executor 3020, WhatsApp 9400, Temporal gRPC 7233 + UI 8080, Redis 6379.

​
Workflows

  • Save: Persists your workflow to the database. The workflow is not running.
  • Deploy: Activates triggers and starts listening for events. Required for cron schedules, webhooks, and message triggers.
  1. Make sure the workflow is deployed (not just saved)
  2. Check if filters are too restrictive
  3. Verify external services are connected (WhatsApp, Android)
  4. Check backend logs for errors
Use template variables:
Example: {{webhookTrigger.body.message}}
Yes, each deployed workflow runs independently. Multiple workflows can have triggers active at the same time.
  1. Use the Run button on individual nodes to test them
  2. Check the output panel for node results
  3. Use the Console tab in the bottom panel to view node execution logs
  4. Add Python Executor nodes with print() statements
  5. Check the backend Terminal tab or the server logs for errors

​
AI Integration

Click the key icon in the toolbar to open the API Credentials modal — the Add your AI key page walks through it step by step. OpenCompany supports 12 providers (11 dedicated model nodes, plus xAI through the OpenAI-compatible path):
  • OpenAI, Anthropic, Gemini
  • OpenRouter, xAI, Groq, Cerebras, DeepSeek, Kimi, Mistral
  • Ollama and LM Studio (local servers — enter the server URL, no cloud key needed)
Service credentials (Google Workspace, Google Maps, Twitter/X, Telegram, WhatsApp, and more) live in the same modal — see Credentials.
Yes, API keys are:
  • Encrypted before storage
  • Stored locally in SQLite
  • Never sent to OpenCompany servers
  • Only transmitted to the respective AI providers
The Simple Memory node stores conversation history as editable markdown, keyed by session ID. Connect it to an AI Agent’s memory handle to enable multi-turn conversations. It keeps a rolling window of recent exchanges and can optionally archive older messages to a vector store for long-term semantic retrieval.
Model availability changes over time — the model dropdown on each AI Model node always reflects the current supported list.

​
WhatsApp

  1. Click the WhatsApp/Android icon in the toolbar
  2. A QR code appears
  3. Open WhatsApp on your phone
  4. Go to Settings > Linked Devices > Link a Device
  5. Scan the QR code
  • Ensure your phone has stable internet
  • Don’t use WhatsApp Web simultaneously
  • Keep the OpenCompany server running continuously
  • Check if you’re logged out on your phone
Yes, WhatsApp Business accounts work the same way as regular accounts.
Use the group’s JID (ends with @g.us) as the recipient. The WhatsApp Receive node provides group_info.group_jid for incoming group messages.

​
Android

Local (USB):
  1. Enable Developer Options and USB Debugging on your phone
  2. Connect via USB
  3. Run adb devices to verify
  4. Select device in Android Device Setup node
Remote:
  1. Configure relay URL in .env
  2. Add API key in Credentials
  3. Install companion app on device
  4. Scan QR code to pair
Also ensure USB debugging is enabled in Developer Options.
Some Android automation features require root or special permissions:
  • Airplane mode toggle
  • Some system settings
  • Protected app access
Use automation apps like Tasker for restricted features.

​
Webhooks

Local: http://localhost:3010/webhook/{path} Production: https://your-domain.com/webhook/{path}Replace {path} with the path you set in the Webhook Trigger node.
  • Verify the workflow is deployed
  • Check the path matches exactly (case-sensitive)
  • Ensure backend is running on the correct port
Use authentication in the Webhook Trigger node:
  • Basic auth (username/password)
  • Bearer token
  • API key header

​
Deployment

Yes. The requirements are Node.js 22+ and Python 3.12+. The backend uses uv for Python dependencies (not pip). For local development, the simplest path is:
company start frees ports, auto-installs dependencies (uv sync for Python, npm for the frontend and Node executor), and launches everything. Environment variables bootstrap from .env.template.
OpenCompany can run on a small VM:
  • GCP e2-micro / e2-small: low single-digit dollars per month
  • AWS EC2 t3.micro / small: ~$10/month
  • Self-hosted: hardware cost only
Plus costs for AI API calls and domain/SSL.
OpenCompany keeps its state under the data directory (~/.opencompany/ by default; a pre-rebrand ~/.machina/ directory is still auto-discovered for upgrades): the SQLite databases (workflow.db, credentials.db, temporal.db), per-workflow workspaces, and the WhatsApp session. To back up, copy that directory while the server is stopped. API keys and OAuth tokens live encrypted in credentials.db.

​
Something broken?

Install failures, port conflicts, blank pages, and workflow problems all live on the dedicated Troubleshooting page, with exact commands and expected output for each fix.

​
Getting Help

GitHub Issues

Report bugs and request features

Documentation

Browse the full documentation