How we test, and what we don't claim

MainStreet Skills publishes a small number of automation recipes for HVAC and plumbing shops in the US and Canada. Each one is built and run by us before it's listed.

The test setup

Every workflow was imported into n8n 2.45.4 and run end to end on our test machine. Twilio, Jobber and Stripe were replaced by a local mock server that accepts the same request shapes as their documented APIs and records every call. The AI steps used a small local model (Qwen2.5-3B-Instruct, 4-bit) and the speech-to-text steps used Whisper base.en running locally. Mock data (customers, quotes, invoices, recordings) is invented. Nothing was sent to a real phone, customer or account.

The labels

• Verified with mocks: the behaviour ran end to end in n8n and passed our scenarios against the mock server.
• Documented from official API docs only: the request is built to the vendor's documentation but has not been run against a live account. Where a field name came from somewhere other than the vendor's docs, the page says so.

Costs and figures

• Prices come from each vendor's official pricing page (checked October 2026) and link to it. "Example month" totals are arithmetic on stated assumptions, not measurements.
• Problem figures link to their source and say who published it. Most come from vendors that sell to the trades.
• We don't publish hours-saved or revenue-recovered numbers.

Earlier directory

This site used to list about 100 third-party automations across seven trades. Those listings are unpublished while we focus on tested recipes for one audience.

Corrections

Found a mistake, or a vendor price that changed? Use the submit form with a link and a note.