How can a small business automate repetitive tasks?

Analysis of official documentation, with no testing on a paid account.

Bid status consulted the 27 September 2026. The features and quotas mentioned come from official documentation. The calculations use the volumes indicated in each example.

A first workflow that reveals real problems

A very small business receives enquiries through a form. The current manual process is to read the email, copy the name and requirement into a table, then notify the right person. A pilot workflow can create the record after the form is submitted, mark its source, assign an owner and send a notification. The final step remains human: qualify the enquiry and decide how to respond. This separation prevents incorrect data from automatically triggering a commercial promise.

Write five columns before choosing a tool: departure event, data to copy, destination, responsible for failure, and acceptable delay. The form can be submitted twice, the address may be missing and the table API may not be available. Your test must cover these three cases. If the same client creates two plugs, the workflow speed is not a gain.

Four products, four arbitrations

Make: calculate credits on your branch lines

Make lists 1,000 credits per month on Free. Most actions cost one credit, while some advanced modules may cost more; the router and several error handlers are not counted. When credits run out, scenarios stop until credits are added or the plan is changed. See the grid Make and its definition of appropriations at the time of subscription.

If 300 monthly requests each trigger three ordinary actions, the initial estimate is 900 credits, excluding searches, iterations and errors. A scenario that checks each contact in two services may exceed that estimate. Run it ten times on real cases, record average and maximum usage, then multiply by the monthly volume. Allow a margin for retries and set a usage alert.

n8n: execution may include several steps

n8n Cloud counts an execution for a full workflow launch, regardless of the number of steps, according to its tariff documentation. The model may favour workflows with lengthy logic, but concurrency, duration and history limits matter when processing overlaps. The self-hosted version requires you to manage updates, backups, access and secrets. For a very small business with no one assigned to these tasks, self-hosting does not mean free when considering total cost.

A useful test is to interrupt the connection to the destination tool and check what is retried, how many times and where the responsible person reads the error log. Also ask who will own the credentials if the person building the workflow leaves the company.

Albato: fast for a simple bridge, with visible limits

Albato defines a transaction as a successful automation step after the trigger. Its free plan lists 100 transactions, five active automations, two steps per automation, updates every fifteen minutes and seven days of logs. Pro increases these limits and offers features including automatic retries, according to the tariff page. If your workflow needs to respond within seconds or include three actions, the free plan is insufficient to validate the intended setup.

Pabbly Connect: Check the exact offer and countdown

Pabbly indicates that triggers and certain internal steps, such as filter or router, do not consume tasks, unlike actions sent to applications. Its website also highlights long-term offers. Compare the cost with the number of actions performed and the extent of assistance, rather than projecting an economy from a "lifetime" slogan. Commercial rules and conditions must be reviewed on the official page before payment.

Calculate a comparable cost

Use the same scenario for all four quotes. For example: 200 forms per month, with 30 duplicates discarded; for each of the remaining 170, a record is created and a notification sent. Record 200 trigger events on one side and 340 useful actions on the other, then add searches, filters, retries and steps that also run on duplicates. An “execution” is not the same as a “task” or “transaction”. Entry-level pricing tables do not answer the question until this count is established.

Add construction time, weekly monitoring, connected application fees and exceedance thresholds. The real economy is the avoided capture time less control time and errors created. If manual processing takes one minute and the flow check takes as much, simplify the process first.

Start-up checklist

1. Run five normal data, duplicate, missing field, and simulated failure.
2. Check that a resume does not create a second sheet or bill: set a unique identifier and a reconciliation rule.
3. Limit the rights of each connection to the necessary data and keep an identified maintainer.
4. Activate the failure alert and test who receives it during an absence.
5. Keep a documented manual process for urgent requests and a procedure for stopping the scenario.

Make or Albato can be tested quickly for an initial connection between two applications. n8n may suit a more technical workflow that the team knows how to operate. Pabbly is worth comparing if the number of actions drives the budget. These are starting points for selection; decide using the logs from your own runs.