Integrations and provider controls
Start with customers, estimates, schedules, job records, and invoices. Add online payments, accounting sync, or business messaging when you need them. These optional connections require setup and verification, and providers may charge their own fees.
Riverbend Service Co.
Product previewInvoices
Money & price book
Pricing, invoices, and payment records connected to customers and jobs
INV-2107
Riverside Apartments · JOB-1042
Total
$1,655
Paid
$800
Due
$855
QuickBooks Online
Reviewed customers, invoices and applied payments move one way from Ironline with visible reconciliation.
| Item | Type | Unit price | Status |
|---|---|---|---|
| Diagnostic visit | Service | $129 | Active |
| Service labor | Labor | $95/hr | Active |
| Standard materials | Material | $45 | Active |
| Dispatch fee | Fee | $35 | Active |
Job photos
Stored with the work
Team access
Role-based controls
Audit trail
Every change connected
Start with the included tools
Use customer links, CSV exports, device call and email links, and browser maps. Create a private calendar feed when you want to view the schedule elsewhere.
Connect and test before use
Online payments, QuickBooks sync, and business messaging need your provider account, authorization, and a successful workflow check. Ask us what applies to your business.
Scoped building block
Useful for an approved workflow, but not marketed as a plug-and-play marketplace integration.
Included fallback paths
These are current Ironline and device-native paths—not future marketplace claims. They reduce add-on dependency while preserving clear boundaries around provider-backed automation.
Open a service address or the day’s ordered stops in the device’s map app. Ironline keeps a clear schedule-order fallback when a paid route provider is not configured; it never invents traffic, distance, or ETA.
Use Customer Center, secure estimate and invoice links, click-to-call, click-to-email, and the device’s own text composer before adding a dedicated carrier-backed Ironline number.
Subscribe to Ironline’s private schedule feed and export operational or accounting-ready CSV files while Google, Microsoft, Intuit, or another paid connection remains inactive.
Publish request forms, let customers return through Customer Center, and use honest review, referral, warranty, and repeat-service links without buying a separate booking or reputation product.
Third-party providers keep their own fees, limits, terms, and activation requirements. Technical per-item security limits and reasonable-use protections still apply; Ironline does not turn them into plan usage buckets.
Available product connections
Subscribe an external calendar to scheduled Ironline work through a private, workspace-scoped feed.
Create named, scoped, and revocable credentials for approved external intake, operational reads, and trusted event workflows.
Ironline subscriptions use provider-hosted Stripe checkout and billing management. Customer invoice payments use a separate workspace activation path.
Deliver selected operational and automation events to a tested Zapier or Make webhook through a five-minute signed dispatcher.
Controlled provider activation
These connections have implemented product foundations but remain authorization-, configuration-, or proof-dependent. A saved connection alone is not treated as a successful production workflow.
When a workspace is authorized, configured, and verified, reviewed customers, invoices, and applied payments move one way from Ironline into the business’s own QuickBooks company.
Where connected payments are activated for the workspace, customers use a provider-hosted payment page and Ironline records provider-confirmed outcomes.
A dedicated provider number can connect service conversations and phone-intake records to customers and work after workspace activation and supervised proof.
After owner authorization, limited read-only availability can support scheduling review without importing event content or writing calendar events.
Geocoding, route previews, and browser maps require protected provider configuration, usage controls, and supervised route proof before operational reliance.
Integration foundations and external handoffs
Use scoped credentials for approved intake, operational reads, and trusted event polling. Ironline supplies the API foundation and safe recipes but does not claim a native marketplace listing.
A matched automation can queue one signed automation.rule_matched event to a deliberately selected active and tested endpoint. The rule stores the endpoint ID—not its URL or signing secret.
Provider activations receive signed events, preserve receipts, reject duplicates, and reconcile durable records instead of trusting browser redirects or ambiguous success pages.
Connection principles
Accounting, payment, calendar, communications, and maps connections use the customer’s own authorization and remain separated by workspace.
Failed, partial, stale, or conflicting records stay visible for review and reconciliation instead of disappearing behind a generic connected badge.
Each connection explains what moves, which system remains authoritative, and which actions require deliberate approval or activation.
We will identify what can connect now, what requires activation, what should remain authoritative, and what should not be promised yet.
Review security and data practices