Answer
How do you connect AI to the tools you already use?
Three routes exist, and the right one depends on whether the job needs to read, to act, or to run without you.
Three routes: paste the data in, enable a published connector, or wire it through an automation platform. Choose by what the job needs. Reading and drafting rarely justify a connection; acting on a schedule always does.
Start with the route people skip. For a large share of useful work, the connection is a copy and a paste, and it is not a lesser option. Exporting the enquiries, pasting the thread, attaching the spreadsheet: this supplies exactly the material the job needs, grants no standing access, leaves no credential lying around, and is available in every product immediately. If the job is done a few times a week and a person is present anyway, this is usually the correct answer and the analysis can stop here.
The second route is a published connector: an integration offered by the AI product or by your software vendor, authorised with your account. This is the right route when the job needs current data rather than a snapshot, when the data is too large or too scattered to paste, or when the assistant needs to write back. What you are agreeing to is a standing grant, so the question to ask at the authorisation screen is what the connection can reach when nobody is looking, not what you intend to use it for today.
The third is an automation platform sitting between your systems and a model: a trigger fires, data is fetched, a model call is made, a result is written somewhere. This is the route for anything that must happen without a person present, and it has a property the other two lack — the steps are visible and each one can be logged, retried and inspected. It also has a property people underestimate, which is that it is a piece of software your business now maintains.
The order matters because the routes are not equivalent in cost. Pasting has no ongoing cost and no permission surface. A connector has a small setup cost and a permanent permission surface. A platform has a real build cost, a subscription, and a maintenance burden that arrives the first time an interface changes upstream. Choosing the heaviest route for a job the lightest one would have done is the most common and most expensive mistake in this area.
Whichever route, the same two design questions apply. What is the smallest scope that does the job — one folder, one mailbox label, one table, one project rather than the whole account? And what happens when the connection fails, which it will, silently, on a weekend? A connection with no failure path produces the worst outcome available: a workflow everyone believes is running that quietly stopped, and nobody notices until a customer does.
One thing worth saying about direction. Reading from your systems and writing to your systems are different decisions and should be made separately. A great deal of value is available from read-only connections, and read-only removes the entire category of failure where the assistant changes a record it misunderstood. Grant write access when a specific job requires it, to the specific place it requires, and not as part of the same click.
Most businesses reach for an integration when what they needed was a copy and a paste, and pay for the difference in permissions.
Siddharth Sharma, Context Theory
Related questions
What about tools that have no AI integration?
Check for an export and a scheduled report before concluding there is no route. A nightly export to a folder that an assistant can read is a connection, and it is often better than a live integration: it is inspectable, it is a snapshot rather than a standing grant, and when it breaks the absence of a file is a visible failure rather than a silent one.
Is it safer to connect through one platform than several products?
It concentrates rather than reduces the exposure, which is genuinely useful for review and genuinely worse for blast radius. One place holding every credential is one place to audit and one place to lose. The practical compromise is to concentrate the connections you actually run and to avoid authorising anything in a second product because it was offered.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Sub-15-minute compliance — automated routing vs manual only | 62.5% vs 39.1% | Category-wide |
| Firms that never responded to a web enquiry at all | 23% | Category-wide |
2026 speed-to-lead benchmark · verified
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads", Harvard Business Review (March 2011) · 1.25M inbound leads across 2,241 US firms · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Procurement | The three connection routes carry different permanent costs: supplying material by hand has no permission surface and no maintenance, a published connector adds a standing grant, and an automation platform adds a build, a subscription and a maintenance obligation that begins when an upstream interface changes. | Listing, for a candidate job, what remains in place after the job is finished under each of the three routes. |
| Software | A scheduled export to a readable location functions as a connection for tools with no published integration, and is inspectable and snapshot-based rather than a standing grant, with a missing file as a visible failure signal. | The scheduled report or export feature of the business system in question. |
| Constraint | Read access and write access to a business system are separable decisions, and read-only connections remove the whole class of failure in which an assistant modifies a record it misread, while retaining most of the available value. | The permission scopes presented at authorisation for any business-system connector. |
| Response | A connection with no defined failure path produces a workflow believed to be running that has silently stopped, so the failure question must be answered at design time rather than after the first weekend outage. | Asking who is notified, and how, when the connection returns an error at a time nobody is present. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one