Integrations
The valuable part is the workflow, not a wall of logos. We only list connections we can describe honestly — available, coming soon, or planned.
How to read this page
Email notifications are available today. Accounting, supplier catalogs, maps, texts, payments from your customers, and a public API are planned. Wrench Cove’s own subscription billing is not an integration you connect.
Accounting
Connect operational work in Wrench Cove with the accounting system your business already uses.
Finish the work in Wrench Cove. Keep accounting in QuickBooks. The intended use is that customer, estimate, and invoice information can move without the office typing the same job twice. That connection is not built yet.
Inventory and suppliers
Look up supplier parts without leaving the job — then let inventory and history stay in Wrench Cove.
A technician records a part on the job. Inventory at the site can drop. The part becomes part of the equipment’s service history. Purchasing already knows how to raise a purchase order when stock needs attention. A live supplier catalog — product lookup, supplier SKU matching, and supplier pricing — is planned.
Payments from your customers
A planned way to collect on completed work. This is not how you pay for Wrench Cove.
The job is finished and the history is on the equipment. Collecting what the customer owes should not require a second system you cannot reconcile. That handoff is planned. Wrench Cove’s own subscription is billed separately and is not this integration.
Email and communications
Wrench Cove can email your team when work arrives, is assigned, or changes status.
A request comes in or a job is assigned. Wrench Cove can send the email. The work still lives on the customer, location, and equipment — the message is just the tap on the shoulder.
Text messages to technicians or customers are not available yet.
Email and in-app notifications already cover assignment and status for the team. A text message path is contemplated for later. There is no SMS provider to connect today.
Maps and location
Addresses already live on service locations. Mapping and driving directions are not built yet.
A job already knows the customer, the location, and the equipment. Seeing that address on a map, or building a route for the day, is planned. In-app routing rules assign work to people — they do not draw a path on a map.
API and webhooks
A planned public API and outbound webhooks. Not launch-ready, and not an Enterprise-only lockout of ordinary automation.
Some businesses will need Wrench Cove to talk to a system we do not list here. The intended path is a documented API and outbound webhooks. Core is intended to cover ordinary automation. Enterprise is intended for higher limits, service accounts, and custom integrations. There are no customer API keys and no outbound webhook subscriptions today.
Joining the list does not create an account or connect a third-party system.