API Integrations

Who this is for

Teams repeatedly copying the same information between two business tools. For example, turning an approved request into a job record or saving an attachment to the right folder.

What is included

• One workflow with one trigger and up to three action steps.
• Up to two existing tools with supported connectors and standard authentication.
• Agreed field mapping and a failure notification.
• Up to ten test scenarios, one revision and a handover call.
• Editable workflow configuration and clear operating instructions.

How it works

We check the tools and scope, build a test version and review it with you before agreed launch. Target: five to seven working days after access and scope are confirmed.

What you take away

One tested automation in an agreed account, plus the instructions your team needs to monitor it and make routine changes.

Price

£695 one-off for the connector-based starter. 50% at booking and 50% after the acceptance demonstration, before final handover. Custom API integrations receive a separate fixed quote.

When you need a different scope

Custom connectors, unsupported APIs, complex data transformation, historical migration and AI evaluation are separate work. Choose AI Workflow Pilot when the key task requires AI judgement or drafting.

Ownership, costs and next step

Start with a short fit call. We confirm the scope, total price, access needed and delivery dates in writing before work begins. Prices are in GBP, excluding VAT where applicable. Software subscriptions, hosting and AI usage are separate and disclosed before you commit. A Hub subscription is only needed if it is the platform you choose. Ongoing support is optional.

You keep the agreed deliverables and editable documentation. Bespoke code transfers after payment, subject to third-party licences; existing platforms remain licensed. We explain any limitations on export or moving providers. Results depend on the process and how the tools are used; no particular savings are guaranteed.

Builds include 30 days of fixes for defects against the agreed scope from handover. New features, third-party outages and platform changes are separate from that cover.

Before we begin

Name the event that should start the workflow and the result you want in the second tool. For example, specify what counts as an approved request and which fields a new job record needs. A single clear trigger is easier to scope than a broad instruction to keep two systems in sync.

Bring the names of the two tools, information about the accounts and the field mapping you expect. Include an example of missing or unusual data. Supported connectors and standard authentication define this starter; the service title does not mean every custom API or authentication method is included in the fixed price.

An illustrative walkthrough

In an illustrative request-to-job flow, the first tool records an approval, the workflow reads the agreed fields, and the second tool receives a new job record. A person then uses that record in the normal process. The field map explains what travels between the tools and what stays in its original system.

Acceptance should include the agreed exception cases as well as a normal request. Decide who receives the failure notification and what they should inspect before acting. A useful operating guide connects that notification to the workflow's purpose, rather than leaving the team with an unexplained technical error or a diagram nobody owns.

Using the result

Keep the editable configuration and operating instructions with the account owner. Use the handover to understand where the workflow runs, where the field mapping is maintained and who reviews a failure notification. Changes to a source field or a tool's permissions can affect the route even when the business process has stayed the same.

The starter is a defined connector-based automation. More tools, a custom connector, complex transformations or a historical migration need a separate scope. If the central task involves AI judgement or drafting, discuss AI Workflow Pilot so evaluation and human review are addressed as part of the work.