Build Workflows That Work.Give Them a Place to Run.

n8n connects apps and actions into a visual workflow. A trigger starts the process, and the steps that follow can check data, call another service or send a result.

• Sales: turn a form submission into a CRM contact and a follow-up notification.
• Operations: move order details into a sheet or database.
• Reporting: collect figures on a schedule and send a summary.
• AI-assisted work: create a draft or classify incoming text for review.

Start with one repetitive task that has a clear input and a result you can check. See the workflow examples.

You can build many workflows with the visual editor and supported integrations. You still need to map fields, connect accounts and decide what should happen when data is missing or a step fails.

For a first project, connect a form to a spreadsheet and a team notification. Custom APIs and complex transformations require more technical knowledge. Begin with a small workflow before adding branches or custom code.

Truehost provides hosting for a self-hosted n8n installation. n8n Cloud is a separate hosted service operated by n8n.

• Truehost hosting: choose hosting resources for your preconfigured n8n environment and connect your accounts.
• n8n Cloud: use n8n’s hosted service under its own plans and feature limits.

Compare the operating work you want to take on, the integrations you need and total costs. A Truehost hosting subscription does not include an n8n Cloud account.

Yes, a local installation can be useful for learning and testing. Your computer must remain running and connected for scheduled work, and incoming webhooks need a reachable endpoint.

Hosted n8n separates the workflow environment from your laptop. Workflows can keep running when your laptop is off, provided the hosting and connected services remain available. Test locally if that suits you, then use hosting for a persistent deployment.

The plan cards show current Nigerian pricing, available billing terms and the payment for the selected term. Compare the full billing amount as well as any per-month equivalent.

Your total automation budget can include:

• The Truehost hosting plan.
• Paid app subscriptions or API usage.
• AI-model or messaging-provider charges.
• A separate n8n software licence if you need paid features.

Choose a hosting plan around the work you expect to run, then measure actual usage before increasing resources.

n8n’s Community edition can run without a paid software licence. Hosting and connected-service usage can still cost money.

Some collaboration, security and administration features belong to paid n8n editions. Check the official edition comparison before choosing features for a team. Free software use does not make every deployment or commercial use unrestricted.

No. They are separate products. N8N Business is a Truehost hosting tier with a particular allocation of server resources.

n8n’s Business software subscription unlocks software features through a licence. Buying the similarly named hosting tier does not provide that subscription. Select hosting for capacity and the software edition for the features your organisation needs.

Choose around the size and overlap of your executions. Workflow count alone is a poor guide: one large data transformation can use more resources than several simple notifications.

• Starter: consider it for small payloads and a few focused automations.
• Pro: consider it as scheduled jobs and incoming events begin to overlap.
• Business: consider it for heavier processing and more headroom.

These are starting suggestions, not throughput guarantees. The plan recommendations show catalogue-backed CPU, RAM and storage beside each option.

The catalogue lists unlimited workflows and concurrent executions, but server capacity is finite. This does not mean an unlimited amount of processing can happen at once.

• CPU and RAM affect how much work can run together.
• Storage is used by databases, execution history and files.
• Connected APIs can impose their own rate and usage limits.

Test representative workloads and set sensible concurrency, batch sizes and retention. Add resources when measurements show you need them.

Yes. A standard VPS suits a custom software stack. It gives you an alternative when you want to install n8n alongside your own apps or tools.

Budget resources for every service and keep their data, ports and backups organised. Choose n8n hosting for a preconfigured workflow environment; choose a standard VPS for your own mix of software.

n8n has a WhatsApp Business Cloud integration. You need the appropriate Meta business/API setup and credentials; hosting alone does not connect a personal WhatsApp account.

1. Prepare the required WhatsApp Business Cloud access.
2. Add the credentials to n8n and configure the relevant node.
3. Test the workflow with the intended trigger and recipient.

Messaging rules, templates and provider charges still apply. Use the official WhatsApp integration guide for supported operations.

An API may provide a route to connect it. First check whether the service exposes the operation you need and permits automation.

• Identify its authentication method and required permissions.
• Check the request format, response fields and pagination.
• Account for rate limits and failure responses.

A custom API connection takes more setup than a ready-made integration. Test with a small request before processing production records.

You can connect supported AI services using your own provider credentials. For a cloud-hosted model, the provider performs the model computation; your n8n server coordinates the workflow.

For example: receive a document, extract text, request a summary and save a draft for a person to review. Model usage is billed separately by the provider.

Your n8n workflows connect to the model through its API; model hosting is separate from this n8n environment.

You can configure a domain or subdomain for your instance. For example, use a dedicated automation subdomain rather than placing the editor at your main website address.

1. Point the relevant DNS record at your hosting endpoint.
2. Configure HTTPS and the correct public instance/webhook URL.
3. Register the production webhook URL with the sending service.
4. Send a test event and verify the workflow result.

After a domain change or migration, check callback URLs and webhook registrations as well as browser access.

Pick a frequent task with clear rules and an easily checked result. A lead-capture workflow is a practical starting point:

1. Receive a website enquiry.
2. Check that the required fields are present.
3. Create or update the contact in your CRM.
4. Notify the person responsible for following up.

Test missing fields and duplicate submissions as well as a valid enquiry. Once this works reliably, add routing, scheduled follow-ups or reporting.

Queue mode separates trigger handling from workflow execution. The main process receives work, Redis coordinates the queue, and workers execute jobs.

This helps organise a growing workload, but adding workers consumes resources. Tune worker concurrency around available RAM, CPU and the services your workflows call.

The plans list queue mode. Review n8n’s queue-mode documentation before changing the worker setup, encryption configuration or binary-data storage.

Look for a recurring bottleneck during normal workloads. One slow run may be waiting on an external API rather than your server.

• CPU: sustained high use during transformations or overlapping jobs.
• Memory: failures or restarts when processing larger payloads.
• Storage: execution history or files consuming the available disk.
• Queues: work taking progressively longer to start.

Try smaller batches and sensible data retention, then review server capacity. More RAM will not remove a third-party API rate limit.

Compatible workflows can be exported and imported. Moving workflow definitions is different from restoring an entire instance.

1. Back up the existing setup.
2. Import workflows and install any required compatible nodes.
3. Reconnect credentials and check environment-dependent settings.
4. Update webhook URLs, then test before enabling production triggers.

Coordinate the switch so both instances do not perform the same scheduled actions. For full-instance recovery, follow the backup and restore guide.

Keep enough to recover the instance, not only its workflow definitions.

• The n8n data folder and credential encryption key.
• The external database, if used.
• Deployment settings and any custom-node files.
• Separately stored files or external execution/binary data.

Without the original key, encrypted credentials cannot be recovered from the database. Store backups securely and test a restore. See n8n’s backup guidance.

The plans list automated installation and dedicated support. Confirm the ongoing service scope for application updates, server maintenance and scheduled backups.

You still need to configure your business logic, connect authorised accounts and check workflow results. Before an update, take a recoverable backup and test important integrations against the new version.

For a support request, record the failed step, time and error message. Remove passwords, tokens and customer data before sharing diagnostic details.

Plan an exception path before relying on unattended runs. A failed API call, expired credential or missing field can stop the intended result.

• Inspect the failed execution to locate the step and input involved.
• Send an alert or create a task for failures that need attention.
• Use retries where appropriate for temporary problems.
• Check for an existing result before repeating a side effect, such as creating an order.

Do not assume a failed workflow made no changes: earlier steps may already have completed.

Only the data handled locally stays within that environment. A workflow that calls a CRM, messaging service or AI provider sends the selected information to that service.

• Send only the fields the receiving service needs.
• Limit credential permissions.
• Review saved execution data and retention settings.
• Keep administrative access and backups protected.

Map the services each workflow reaches before putting sensitive business data into it.